Main page format and content

Figure 2–5 shows an example of a WebSpeed main page. The format and content sections are identical to the AppServer main page, and very similar to the NameServer page.

Figure 2–5: WebSpeed main page example

Each OpenEdge main page follows the OpenEdge Management title page naming conventions. That is, the specific resource type, container name, and resource name appear in the upper-left corner of the main page. For example, in Figure 2–5, the title WebSpeed: chimay.wsbroker1 identifies the default wsbroker1 broker discovered on the container (host) chimay as a Transaction Server.

A container represents a named instance of an AdminServer that is either running OpenEdge Management or configured to be monitored by OpenEdge Management. There is a one-to-one relationship between the host name and container name, unless there are multiple AdminServers running OpenEdge Management on the same host.

Table 2–2 identifies and provides a general description of the four sections on the OpenEdge main page.

Table 2–2: Sections of the OpenEdge main page 
This section . . .
Identifies information you use to . . .
Status
Review the current operational statistics for a specific OpenEdge resource.
Command and control
Perform various tasks associated with an OpenEdge resource, including:
  • Modifying the start and stop controls for a specific resource, or adding and/or trimming a resource's pool of available agents (WebSpeed) or servers (AppServer).
  • Accessing and examining log file monitor and viewer details (for local resources and their associated agents or servers only).
  • Configuring monitoring plans and rules.
  • Generating recommended rule threshold settings using the Configuration Advisor. (WebSpeed brokers and AppServer brokers polled rules only.)
Operational views
Help analyze the performance of these OpenEdge resources:
  • AppServer brokers and their associated servers through the display of data and associated graphs.
  • WebSpeed brokers and their associated agents through the display of data and associated graphs.
  • Status details about a NameServer instance and its related Application Services.
Informational views
Review the static configuration values for a resource as they are defined in the ubroker.properties file.

Polling and statistical details on the OpenEdge main page

As shown in Figure 2–6, the upper-right corner of the page displays summarized resource polling information pertinent to the currently displayed resource monitor. This section can also report broker resource status details.

Figure 2–6: Broker statistics not available information

Figure 2–6 shows the additional line of information—Statistics collection not enabled—in the upper-right corner. This resource status detail displays when the Broker statistics not available field is not currently enabled (that is, it is set to False) on the Broker Control page. This message indicates that this resource is not currently collecting statistical data. Therefore, no trending, polling, or graphing can occur for this resource until the status of the Broker statistics available field is changed to True.

The WebSpeed and AppServer main pages also present the collection status information in the Broker statistics available field in the Status section.

Note: The OpenEdge Management internal information alert, BrokerCollectStatisticsDisabled, can also appear on the OpenEdge main page if the current setting of the Broker statistics available field is False.

For more information about the Broker statistics available field and specific OpenEdge resources, see:


Copyright © 2006 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095