Web tier monitoring

Web tier monitoring provides notification when the following metrics reach the specified level, indicating a critical event. Use the Teamcenter Management Console to manage the Server Manager and the web tier. The following metrics are defined in the webtierMonitorConfig.xml file: Metric Description Abandoned Servers Servers are assigned, but attempts to connect fail. No Server Available The web tier is unable to assign a server to a user because none are available. Server Comm Failure A Teamcenter server closed the connection while the web tier was waiting for a response. Failed Login Attempts A user provided invalid credentials. Number Pending Requests The number of client requests for which the web tier is awaiting a response. Long-running Requests Current The web tier waited longer than the specified time for a server response Long-running Request Completed The number of requests taking longer than the specified amount of time to complete. Grave Events Fatal or unexpected errors occurring in the web tier. Configure web tier monitoring using the webtierMonitorConfig.xml file, located in the deployed .war file in the lib\mldcfg.jar file. You can revise the webtierMonitorConfig.xml file and save it back into the .war file before deployment by the web application. Or if you prefer, you can place the revised file directly into the root directory of the web application server’s run-time environment, and thus override the version of the file in the .war file. For example, on WebSphere place it into the profile directory, or on JBoss place it into the bin directory. Tip You should review all monitoring settings and ensure that the thresholds are set correctly for your site. If you do not know the optimum monitoring setting for any given critical event, then set the value to COLLECT. Collect the data and review it to determine normal activity levels. Then set notification values slightly higher than normal activity levels. The contents of the email notifications are generated from the webtierMonitorConfigInfo.xml file. (This is a companion file to the webtierMonitorConfig.xml file.) See this file for a complete list of possible causes and recommended actions for web tier monitoring. The webtierMonitorConfigInfo.xml file is stored in the WAR file by default in the lib\mldcfg.jar file. A copy can be placed on the application server’s current directory to override the default version. You can configure web tier metrics and logging behavior to better administer web tier processes. Use the pref_export.xml file to enable web tier metrics. This file is stored in the WAR file by default in the lib\mldcfg.jar file. A copy can be placed on the application server’s current directory to override the default version. Use the ExtendedEnabled element to enable extended nested metrics upon reset. Use the ResponseTimeSampler element to enable sampling and logging of response times.