Try OpenEdge Now
skip to main content
Servers, DataServers, Messengers, and Adapters
Analyzing OpenEdge Application Performance : Responding to an application crisis : Initial investigation
 

Initial investigation

In an application crisis situation of this type, the administrator can leverage OpenEdge Management-supplied information to alert him to immediate problems and provide data related to the crisis.
The following table lists the possibilities the system administrator considers. Note the blank, first column in the table. As each possibility is reviewed, the administrator can use this table as a checklist, identifying the items requiring further consideration.
Table 50. Crisis review checklis
Access and review . . .
To . . .
Alert and other data indicators that have been set up to monitor and display data on the collections page
Quickly examine issues that might be the reason for this dramatic change in performance. As previously noted in OpenEdge Management at XYZ Corporation, the administrator has several indicators set up, including viewlets related to the AppServer brokers.
Data details in log files such as the database log files, AppServer log files, customized log files and so forth
Examine log file data from the time period during which the crisis initially occurred. Determine if there is any noteworthy, relevant information in error logs related to the crisis situation.
Network- and server-related data details, using TCP resource monitors previously set up
Determine the status and response time, if any, for mail, FTP, and Web Servers that might be running on the network.
Network-related data details, using Packet Internet Grouper (PING) (ICMP) resource monitors previously set up
Determine if network resources are available.
Server-related data details
Determine if AppServer server details and/or AppServer broker details are of help in problem determination.
While quickly scanning the checklist, the system administrator remembered what the users said about the performance issue: Nothing was working. This could indicate there is a network problem to resolve, but where is the source? Since most of the transactions related to the procedures that were not currently functioning run on a remote AppServer, the administrator decides to follow this investigative path.