Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Timeout with SAP BusinessObjects concurrent license


This topic provides troubleshooting information for how to address problems you might encounter when you have one SAP BusinessObjects concurrent license for SAP BusinessObjects XI Enterprise.

Each client access consumes a license while it is in an active session within the CMS.

With a single concurrent user client access license, only one client can be active at any one time. To ensure that the license usage count returns to zero, you should properly log out of each client application session. If you exit out of the browser without logging out of the client, you might receive messages stating that you have exceeded license count. In some cases, your session might not be properly released, and the session stays open until the timeout has been reached, which is 20 minutes by default.

Try one or both of the following workarounds:

To modify the timeout setting if Apache Tomcat is installed

  1. Stop the Tomcat service.
  2. Open the Web.xml file located at <ApacheInstallationDirectory>\Tomcat\webapps\businessobjects\enterprise115\desktoplaunch\WEB-INF.
  3. Locate the following entry: 

    <!-
    <listener>

    <listener-class>com.businessobjects.sdk.ceutils.SessionCleanupListener</listener-class>
    </listener>
    -->
  4. Remove the comment tags so the entry appears as follows: 

    <listener>
    <listener-class>com.businessobjects.sdk.ceutils.SessionCleanupListener</listener-class>
  5. Locate the following entry: 

    <session-config>
    <session-timeout>20</session-timeout>    <!-- 20 minutes for session objects -->
    </session-config>
  6. Update the session timeout value to the appropriate value. BMC recommends that you update the value to 15 minutes, but the value you use can vary according to the requirements of your environment.
  7. Restart the Tomcat service.

To modify the timeout value if Microsoft IIS is installed

  1. Stop the Microsoft Internet Information Services (IIS) service.
  2. Open the machine.config file located at C:\Windows\Microsoft.NET\Framework\v1.1.4322\CONFIG.
  3. Change the number of seconds in the following line: 

    <httpRuntime executionTimeout="200"

     BMC recommends that you update the value to 900 seconds, but the value you use might vary according to the requirements of your environment.

  4. Restart the Microsoft IIS service.

Note

Changing this setting affects the ASP.NET timeout, because ASP.NET depends on this setting. You can also use this procedure if you encounter timeouts in the BI launch pad sessions when you are previewing large reports.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*