Child pages
  • BEx Web Applications: Session Management and Analysis
Skip to end of metadata
Go to start of metadata


To enable the SAP portal to run back-end transaction applications, the following tasks must be handled for each session:

  • Log off:
    When a user logs off  from portal by choosing the Log Off button, a logoff action should be triggered on the SAP portal side (portal and connected back-end systems).
    Although SAP NetWeaver Portal comes with an out-of-the-box mechanism that terminates a session when the user closes the browser or navigates out of the SAP iFrame, the mechanism does not handle logoff.

  • Closing the browser:
    When the user closes the browser without logging off, a logoff on the SAP portal side should be triggered as well.

  • Navigating away:
    Navigating out of the SAP iFrame in your company portal should trigger a logoff on the SAP portal side.

  • Session timeout:
    The session timeout period should be synchronized between the SAP NetWeaver portal and your company portal.

    To set the SAP Portal timeout value, perform the following steps:

    1. Shut down the system.
    2. Open the Config Tool from the following location:
                      C:\usr\sap\<SID>\J<instance no.>\j2ee\configtool\configtool.bat
    3. Choose View ->Expert Mode
    4. Navigate to Services ->servlet_jsp
    5. In the Key column, scroll down to the following parameter: Global_app_config/session_config/sessionTimeout
    6. In the Custom Value field, enter the timeout value and choose Set Custom Value .
    7. Save and then restart the system


Session Timeout Analysis:

Logon to the following URL to start the session overview:

         <protocol>://<server>:<port>/irj/servlet/prt/portal/prtroot/ bi.web.portal.integration.sessionoverview

Note: The user needs to have administrator authorization.

The session overview shows:

Current date: <current date>
Controllers: <# of controllers>
Applications without page: <# of applications without page>
Applications with page: <# of applications with page>
Portal connection pools: <# of portal connection pools>
SM04 shows the RFC connections opened from J2EE engine to ABAP backend.

Execute the session overview twice:

1) Before executing the BEx Web Applications Java

2) After terminating the BEx Web Applications Java
Note: A BEx Web Application session is terminated, e.g. when: - navigating to another page - using the logoff button - closing the browser window
The numbers for <# of controllers>, <# of applications without page>, <# of applications with page>, and <# of portal connection pools> must be the same before and after executing the BEx Web Applications Java. Otherwise there is a problem in the session management that requires further analysis.

Execute the SM04 after terminating the BEx Web Applications Java. Note: In transaction SM04 you will see a connection of type RFC for each BEx Web Application Java. Important: Terminating a BEx Web Application will not release the RFC connection in SM04. This behavior is due to the RFC connection pool of the Enterprise Portal. The RFC connection will be returned to the connection pool and will be reused when doing a re-logon. Therefore the proper release of sessions of BEx Web Applications Java cannot be analysed with SM04. SM04 will only show that the memory consumed on the ABAP stack will be freed after a successful termination.

Note: The RFC connection will be removed from the connection pool if it is unused for a longer time than defined in the connection lifetime:
Visual Administrator Services ->
Connector Container Runtime ->
Connectors ->
Connector 1.0 -> ->
SAPFactory Managed Connection Factory ->
Connection Definition Connection Lifetime: 3600
Connection lifetime defines the timeout in seconds.

Note: If you are using a load test script or a test script for BEx Web Applications Java, please have a look at note 1008847.




  • No labels