Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Watch4Net | SRM: How to Change the session timeout value (330772)

Last Updated: 5/29/2020Categories: TroubleshootingTotal Views: 8331Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Change the web portal session timeout value in watch4net and SRM

There are a several ways of controlling the web session timeout value which is also impacted by the usage of single sign on between the different web apps (frontend, centralized-managment, etc...)

Cause

each web application has it's own session-timeout value defined in it's respective web.xml configuration file

Web-Servers/Tomcat/Default/conf/web.xml:        <session-timeout>30</session-timeout>
Web-Servers/Tomcat/Default/webapps/mib-browser/WEB-INF/web.xml:         <session-timeout>240</session-timeout>
Web-Servers/Tomcat/Default/webapps/device-discovery/WEB-INF/web.xml:            <session-timeout>240</session-timeout>
Web-Servers/Tomcat/Default/webapps/centralized-management/WEB-INF/web.xml:              <session-timeout>240</session-timeout>
Web-Servers/Tomcat/Default/webapps/compliance-frontend/WEB-INF/web.xml:         <session-timeout>240</session-timeout>
Web-Servers/Tomcat/Default/webapps/alerting-frontend/WEB-INF/web.xml:           <session-timeout>240</session-timeout>
Web-Servers/Tomcat/Default/webapps/APG/WEB-INF/web.xml:         <session-timeout>240</session-timeout>

The timeout value in Web-Servers/Tomcat/Default/conf/web.xml is only enforced if a given web application doesn't have a session-timeout (by default all webapps have one)

i.e.: If you change the value in Web-Servers/Tomcat/Default/webapps/mib-browser/WEB-INF/web.xml to 1 minute and leave Web-Servers/Tomcat/Default/webapps/centralized-management/WEB-INF/web.xml to 240 and you log into the web portal the 1 minute timeout will be enforced however if you also access centralized-management then the timeout value will be 240 minutes. This is caused by single sign on between the webapps.

If you where to comment out  <Valve className="org.apache.catalina.authenticator.SingleSignOn"/> in APG/Web-Servers/Tomcat/Default/conf/server.xml (you would then need to sign in separately to each webapp (frontend, centralized-management)) However you could then enforce different timeout values for all the webapps.

If you where to comment out the session-timeout value in Web-Servers/Tomcat/Default/webapps/mib-browser/WEB-INF/web.xml and Web-Servers/Tomcat/Default/webapps/centralized-management/WEB-INF/web.xml then the value in Web-Servers/Tomcat/Default/conf/web.xml would be enforced for both the frontend and centralized-management.

Resolution

First, connect to the host(s) where the Frontend is installed using an SSH client (like Putty) and log in as root.

Next, navigate to the /opt/APG/Web-Servers/Tomcat/Default/webapps/APG/WEB-INF/ directory and make a backup of the current  web.xml  file via the following command:

APG/Web-Servers/Tomcat/Default/webapps/APG/WEB-INF # cp web.xml web.xml.orig

After making a backup, please then open the file in a text editor (such as vi) and edit the following, highlighted section to specify the timeout you wish to enforce, in minutes (the default is 4 hours, or 240 minutes) and save the file:

<!-- the session configuration -->
<session-config>
<!-- session duration, in minutes -->
<session-timeout></session-timeout>
</session-config>

Lastly, restart the Tomcat Web-Server service on all applicable hosts via the following steps:

In the APG UI,  click the  Administration  button at the top of the UI to enter Administration mode (if you haven t already and are in User Mode)

Click on  Centralized Management  in the tree panel on the left of the UI (the Centralized Management module will launch in a new window)

In the new Centralized Management window, navigate to Physical Overview > [SRM Suite instance name] > Modules > Web-Servers > Tomcat :: [Tomcat Instance name]

Note: There will be a Tomcat instance for each host running web applications   we ll need to select the Tomcat instances under which the frontend is running.

Click the  Restart  button to restart the Tomcat service for each instance (Important Note: This will temporarily disconnect all users who are currently logged into a web application on these hosts)

*Alternately, you can accomplish the same task by running the following command on those hosts:

hostname:/opt/APG/bin # manage-modules.sh service restart tomcat [Tomcat instance name]

Example:

hostname:/opt/APG/bin # manage-modules.sh service restart tomcat Default

After Tomcat has been restarted the new timeout settings will now be in effect.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - Watch4Net/M&R

Take Our Survey

Support Assistant