BusinessObjects Administration – Session Management

Hi Readers,

In this blog we are going to see one of the common Issues in Business Objects deployment i.e. Stale sessions which catch up the concurrent user licenses. Let’s have a look on the issue briefly.

Problem statement:

Concurrent users are being shown as logged in multiple times and their sessions are not being cleared even when they are not using the Business Objects Applications. As a result concurrent user licenses are getting used up very quickly causing other concurrent users facing login Issues due to unavailability of concurrent user licenses (i.e.) All the concurrent licenses are utilized.

Impact – What are the effects/symptoms of the issue?

Concurrent Users of the system will be facing logon Issues due to unavailability of the concurrent licenses.

Benefits

• Effective utilization of existing Business Objects Licensing
• Useful for re-sizing of Business Objects deployment.

Solution Approach for resolution

1. Always ensure that Session Cleanup Listener and Logon token parameters are configured properly in respective business objects applications.

Open web.xml under <BO Installdir>\Business Objects\Tomcat55\webapps\InfoViewApp\WEB-INF

And make sure that the below configuration has been made (in BO 3.x).

• Session Cleanup Listener is active/ uncommented.

-          This will ensure the automatic session cleanup is enabled

• Logon token is set to disabled.

-          Changing the true to false does not allow the token to re-login from stale session.

The above is for Infoview application. If you want to implement the same for other 3-tier applications like CMC, Xcelcius and AdminTools, you have to modify the web.xml for each application directory within Business Objects Installation directory.

2. Implement a SDK utility which periodically monitors and cleans up the stale sessions which consumes the concurrent user license.

Hope the blog could be useful for User and Session management for Business Objects Administrators.

Thanks for reading.  

Read More About  Business Objects Administration

Business Objects Administration – Managing Timeout settings

Hello Booglers,

From this Blog onwards we are going to see more in detail about Business Objects Administration and Best practices.

Let us start with timeout settings. As we started moving from 2-tier to 3-tier architecture (DeskI to WebI), the role of timeout becomes significant as it is associated with reports running time.This post will be handy for those who struggle with the timeout issue and various methods to apply itin a Business Objects Enterprise deployment.

Timeout can be configured at the below levels.

1. Designer level

In Designer Application Go to: File > Parameters > Controls

Configure the Limit execution time to setting which limits how long the SQL query is allowed to execute. This hasgreatimpact on reports that contain multiple queries.

Universe Parameters

2. Web Application Server level (Tomcat)

• In the Business Objects Installation server go to Program Files\Business Objects\BusinessObjects Enterprise 12.0\warfiles\WebApps \InfoViewApp\WEB-INF
• Open web.xml in a text editor.
• Change the session-timeout value to the one desired. The default value is 20 minutes.

<session-config>

<session-timeout>60</session-timeout>

<!– 20 minutes for session objects –>

</session-config>

Similarly, modify web.xml on the following folders:

• AdminTools– for Query Builder
• CmcApp– for CMC
• CrystalReports– for Crystal reports
• InfoViewAppActions – for Infoview

3. Central Management Console

Go to: Home > Servers > Web Intelligence Processing Server > Properties

You can configure various timeout setting heresuch as cache timeout, idle document timeout, Idle Connection timeout.Configure these values to the desired.

Similarly, modify settings for Desktop Intelligence Processing Server and Crystal Reports Processing Server.

And finally configure the Auto-save time delay option for Web Intelligence under Business Objects Applications.

4. Central Configuration Manager

Go to: CCM > Web Intelligence Report Server > Properties > Command

Add “-RequestTimeoutxxx” to its command line (where xxx is the duration in milliseconds)

Configure this value to the desired one(for 60 minutes the value would be 3600000).

Similarly, modify settings for Web Intelligence Report Server.

Hope this will be useful for timeout setting in your BOE deployment.

Watch out this space as more to come on BOE Administration. Keep reading!

Read More about  Business Objects Administration