A logging off scenario is vitally important forstateful BSP applications, since the BSP runtime is not able to carry out session management itself. The BSP runtime cannot determine when an application has ended.
Without a logging off scenario, numerous SAP Web AS sessions could remain open and therefore use up memory capacity and similar system resources, even if they are not actually required. The open and inactive sessions remain to exist until they are closed by default by theInternet Communication Manager. This then overloads the application servers.
The cure for this problem is a simple logging off scenario that is created as a protective frame for the session around the respective BSP application. If you implement the logoff scenario, the SAP Web AS session is ended when a user calls up a different URL in the browser, for example, or closes the browser. The session is ended using the automatic send commandsessioncmd=close to the SAP Web AS in a new frame, which is then automatically closed afterwards.
The pages for the logoff are components of the BSP applicationSYSTEM.
BSP applicationSYSTEM contains the following sample pages for logging off:
The BSP application is processed in the browser in its own browser frame. If you close the browser or call a different URL, this closes the session that is running in the background.
The BSP application in the browser consists of two different browser frames, where the system always switches between the two frames, which minimizes setting up the screen repeatedly. If you close the browser or call a different URL, this closes the session that is running in the background.