Both the Dashboard and the Operations Center server to which the Dashboard has established a connection times out based on inactivity. For more information about configuring session timeout, see the following sections:
Two types of session timeout affect the Dashboard user:
Server Connection Timeout: Dashboard portlets will attempt to reconnect to an Operations Center server that has timed out or stopped as long as the Dashboard application has not timed the user out of the Dashboard session. By default, a connection timeout occurs after 30 minutes of inactivity with the Operations Center server.
User Session Timeout: By default, if a user does not perform any activity in the Dashboard for 30 minutes, the user is warned that the session will expire. The user can remain logged in to the Dashboard for an additional 30 minutes by responding to the notification.
To change Dashboard session timeouts:
To configure the server connection timeout, add or update the mo.remoteserver.context.keepAliveTime property value in the Formula.custom.properties file. Set the property to the number of minutes of inactivity to trigger the connection timeout with the Operations Center server.
For information about creating or using the Formula.custom.properties file, see Making Custom Changes
in the Operations Center Server Configuration Guide.
To set the user session timeout, update the following line in the Operations_Center_Dashboard_installation_path/server/webapps/ROOT/WEB-INF/web.xml file for the number of minutes before timeout:
<session-config>
<session-timeout>number_of_minutes</session-timeout>
</session-config>By default, session timeout is enabled for the Dashboard. To extend sessions and keep them open as long as the user’s browser is open and a portal page is loaded, update the portal-ext.custom.properties file. When extending sessions, a smaller session.timeout value, such as 5 minutes, must be set.
To halt session timeout:
By default, the server connection timeout is set to 30 minutes. Verify the mo.remoteserver.context.keepAliveTime property setting in the Formula.custom.properties file to adjust the connection timeout with the Operations Center server.
For information about creating or using the Formula.custom.properties file, see Making Custom Changes
in the Operations Center Server Configuration Guide.
Stop the Dashboard server.
For more information, see Section 2.3.2, Stopping the Dashboard.
Add the following line to Operations_Center_Dashboard_installation_path/server/webapps/ROOT/WEB-INF/classes/portal-ext.custom.properties:
session.timeout.auto.extend=true
For more information about the portal-ext.custom.properties file, see Section 3.9, Understanding Portal Properties Files.
Update Operations_Center_Dashboard_installation_path/server/webapps/ROOT/WEB-INF/web.xml to set a smaller session timeout:
<session-config> <session-timeout>number_of_minutes</session-timeout> </session-config>
Five minutes is the recommended value.
Start the Dashboard server.
For more information, see Section 2.3.1, Starting the Dashboard.
When using the Remember Me feature for auto-login, you can configure the cookie lifespan to expire after a specific length of time or after each browser session.
By default, the Remember Me feature is enabled in the portal-ext.custom.properties file using the company.security.auto.login setting.
To configure Remember Me and cookie lifespan:
Open Operations_Center_Dashboard_installation_path/server/webapps/ROOT/WEB-INF/classes/portal-ext.custom.properties.
To configure cookie lifespan, add the following line and set the value to the length of time (in seconds) to expire:
company.security.auto.login.max.age=31536000
31536000 sets a lifespan of one year. Specify -1 to expire after each browser session.
To disable the Remember Me auto-login feature, add the following line:
company.security.auto.login=false