Server Status
From Site > Utilities, you can click Server Status to view an overview of server processes for your Windchill solution. The Server Status utility generates the values on the page to provide an overview of the status of important server processes for your Windchill solution, including the number of current active users on your system.
If you are in a clustered environment, you can see the status of the processes on all machines in the cluster.
Page Organization
The data presented is organized first according to the type of process under which it is gathered (server manager, method server, Windchill Directory Server, and file server) and then logically grouped within each process. All server managers for your system are listed in the Server Managers field. If there are multiple server managers, clicking the server manager name in the Server Managers field displays the information table for that server manager.
Additional links that display at the top of the page include the following:
The System Configuration Collector link (available only to users in the site Administrators group or to users listed in the wt.util.jmx.AccessUtil.siteAdministrators property).
The Monitoring Tools link (available only to users in the site Administrators group or to users listed in the wt.util.jmx.AccessUtil.siteAdministrators property).
When displaying data that has caused the page to scroll, you can click any Back to top link to return to the top of the Server Status page.
Red text displayed on the page indicates areas of concern. If the red text represents calculated values, the values presented have exceeded the configured thresholds.
For threshold information, see Understanding Server Status Threshold Values.
The timestamps at the bottom of the Server Status page indicate the time frame in which the presented data was collected.
Status Information Details
The server manager table on the page provides the following:
Information on the server manager itself.
Available memory information from the host system.
Information on the method servers managed by the server manager.
The data gathered from Windchill method servers resides in the rows under the Method Server Data title and actual values are provided under each method server process ID. This data is grouped so that you can easily find information about things like memory usage, operating system statistics, servlet requests, and method contexts. The servlet requests are further grouped according to which web application is processing the request:
Servlet Requests: General servlet requests represent those requests going to the Windchill web application.
Servlet Requests: Help Center servlet requests represent those requests going to the Windchill Help Center web application.
Servlet Requests: Solr servlet requests represent those requests going to the Windchill Index Search web application.
Each method server only has values for the web applications deployed in that method server.
Many of the status indicators on the Server Status page provide two data points that are identified by the Recent and Baseline column headings:
The value stored under the Recent column heading provides data about the most recent interval that was captured. The value presented in the Recent column reflects system information gathered from a short time ago until the present moment.
The value stored under the Baseline column provides comparison data that is based on the statistics available since the last baseline reset was done from a JMX client or, if no reset was done, since the last start up of the process. Use the baseline statistics to provide a long-term view of what is normally occurring in the system since startup. You can choose to reset the statistics to capture a specific historical view for some reason. For example, you can reset the baseline statistics if you have applied some change that does not require a restart or reset the baseline statistics immediately prior to conducting a benchmark.
Not all statistics provide a reset option; when available, the resetBaselineStatistics operation on the corresponding MBean allows you to reset a specific statistic. For MBean details, see the following section.
Clicking a linked value in a Baseline column takes you to a historical graph of the data. (To return to the Server Status page, use your browser’s back button.)
Status indicators such as the memory usage indicators and the Uptime statistic only provide one value that applies to just the current instant rather than data aggregated over a time interval. In these cases, there is no baseline provided.
MBean Details for Server Status Page Fields
Many of the values displayed on the Server Status page are calculated using JMX MBeans. The following table shows the Server Status page field label and then identifies the MBean path and attributes that are used to generate the field value:
Server Status Field
MBean Path
MBean Attributes
com.ptc > Dumper
When the value is Yes, it is displayed as red text.
Available System Memory
Load Average (available for non-Windows servers)
java.lang > OperatingSystem
SystemLoadAverage (available for non-Windows servers)
com.ptc > java.lang > Runtime
Time In Garbage Collection
com.ptc > Monitors > GarbageCollection
Perm Gen
com.ptc > Monitors > Memory
CPU Used by Process
com.ptc > Monitors > ProcessCpuTime
Method Contexts
Method Context Time
com.ptc > Monitors > MethodContexts
Servlet Requests: <type>
where types of servlet requests are:
Help Center
com.ptc > WebAppContexts > webAppContext > Monitors > ServletRequests
where the web application contexts are:
Attributes for all values except Active Sessions
Servlet Requests: General
Active Sessions
com.ptc > WebAppContexts > windchillWebAppPath > Monitors > ServletSessions
Current Active Users
com.ptc > Monitors > ActiveUsers
Master Server Manager
com.ptc > ServerManager
Attributes are used to determine which server manager is the main server manager and to display the remote access JMX URL for each server manager (assumes the user is a system administrator and remote access has been configured).
File Servers
com.ptc > Monitors > VaultSites
Was this helpful?