Skip Headers
JD Edwards EnterpriseOne Tools Performance Monitor Guide
Release 8.98 Update 4

Part Number E14715-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

4 Administering JD Edwards EnterpriseOne Performance Monitor

This chapter contains the following topics:

4.1 Understanding JD Edwards EnterpriseOne Performance Monitor Administration

This section discusses JD Edwards EnterpriseOne Performance Monitor administration and lists the forms used for JD Edwards EnterpriseOne Performance Monitor administration.

4.1.1 JD Edwards EnterpriseOne Performance Monitor Administration

JD Edwards EnterpriseOne Performance Monitor administration includes:

  • Specifying global settings.

  • Viewing performance definitions such as those related to systems, agents, metrics, and so on.

  • Setting system defaults.

  • Scheduling batch programs that maintain performance data.

4.1.2 Forms Used for JD Edwards EnterpriseOne Performance Monitor Administration

Form Name FormID Navigation Usage
Global Administration - Global Administration Revisions W95900A JD Edwards EnterpriseOne Menus, JD Edwards EnterpriseOne Lifecycle Tools, System Administration Tools, JD Edwards EnterpriseOne Performance Monitor, Administration, Global Administration View and modify global administration settings, such as the PPMI URL value.
System Defaults - System Default Revisions W95900B JD Edwards EnterpriseOne Menus, JD Edwards EnterpriseOne Lifecycle Tools, System Administration Tools, JD Edwards EnterpriseOne Performance Monitor, Administration, System Defaults Set global system defaults for all monitored systems.
System Definitions - Work With System Definitions W9500C JD Edwards EnterpriseOne Menus, JD Edwards EnterpriseOne Lifecycle Tools, System Administration Tools, JD Edwards EnterpriseOne Performance Monitor, Administration, System Definitions View and select system definition that is associated with each of the systems that are being monitored.
System Definitions - System Definition Revisions W95900D From the System Definitions - Work With System Definitions form, click Find. View and modify the system definition that is associated with each of the systems that are being monitored. For example, you can set archive, PMU timeout, and agent buffer size.
Agent Definitions - Work With Agent Definitions W9500E JD Edwards EnterpriseOne Menus, JD Edwards EnterpriseOne Lifecycle Tools, System Administration Tools, JD Edwards EnterpriseOne Performance Monitor, Administration, Agent Definitions View and select the definitions of the agents that are running on the monitored system's application server, and web server.
Agent Definitions - Agent Definition Revisions W95900F From the Agent Definitions - Agent Definition Revisions form, click Find. Make active or inactive the agent that you selected.
Agent Filters - Work With Agent Filters W9500J JD Edwards EnterpriseOne Menus, JD Edwards EnterpriseOne Lifecycle Tools, System Administration Tools, JD Edwards EnterpriseOne Performance Monitor, Administration, Agent Filters Search for the filter levels for the agents that are running on the monitored system.
Agent Filters - Agent Filter Revisions W95900G From the Agent Filters - Work With Agent Filters form, click Find. Set the filter levels for the agents.
Submit Job - Work With Batch Versions - Available Versions W98305WA JD Edwards EnterpriseOne Menus, Submit Job. Enter R95900 in the Batch Application field and click Find. Select the Reaper and click Select.
Submit Job - Work With Batch Versions - Available Versions W98305WA From the Submit Job - Work With Batch Versions - Available Versions, search for and select a batch application, and click Select. Select Data Selection, Data Sequencing, or both, and click Submit.

4.2 Setting Global System Options

Access the Global Administration - Global Administration Revisions form.

URL

Displays the URL.

User

User ID used to access the PPMI servlet.

Password

Password used to access the PPMI servlet.

Maximum Rows

Limits the amount of data that can be inserted into the JD Edwards EnterpriseOne Performance Monitor tables.

Last Updated User ID

Specifies the last user to update the record.

Last Updated Date/Time

Specifies the Utime when the record was last updated.

4.3 Setting System Definition Defaults

Access the System Defaults - System Default Revisions form.

The System Defaults form enables you to set default values for all of the monitored systems. When a new systems register with the monitoring system for the first time, the system adopts the default values that you have set.

Using the System Defaults form enables you to set global values for each monitored system rather than modifying the values for each system separately.

Archive Nothing, Delete Data, Archive Data

Choose an archive mode. The archive mode specifies how the archive program should process the performance data stored in the monitoring database.

Allow Performance Trace

Enables authorized users connected to this monitored system to start a specific performance trace.

Agent Heartbeat Interval (sec)

Indicates the interval at which agents that do not have any performance data to report or that are in standby mode connect to the monitor servlet to be notified of any configuration changes. If agents post data to the monitoring system before this interval expires, they will be notified of any configuration changes and the timer will be reset. The lower the number, the greater the responsiveness of the agents to configuration changes, but the greater the network traffic. This value cannot be set to zero.

PMU Timeout (days)

Indicates the interval in which an open PMU is considered timed out. PMU timeouts are measured in days. The PMU timeout value cannot be set to zero. After the specified interval, the system assumes that a PMU that has not completed encountered an error and should no longer be considered open. The reaper program moves timed out PMUs from the current PMU tables to the history PMU tables and sets the status to Reaper Timed Out.

Agent PMU Sample Rate (1/X)

Enables you to reduce the amount of PMU data generated by monitoring just 1 of every N server trips. Sampling does not affect PMUs initiated in a performance trace.

Agent Buffering Interval (sec)

Specifies the rate (in seconds) at which an agent sends performance data to the monitoring system. This value cannot be set to zero. A smaller interval decreases the delay between the time when the monitored system generates performance data and the time it is displayed on the monitoring system. Larger intervals enable more efficient transmission of performance data across the network because the system can consolidate the data into packets. The larger the interval, the greater the Agent Max Buffer size should be set.

Agent Max Buffer Size (bytes)

Determines the maximum size of the buffer containing performance data. This enables you to cap the amount of data being stored by the agent on the monitored system and the amount of data sent across your network. If this limit is reached, the agent automatically discards new performance data until the current data has been posted to the monitor servlet. The agent posts an alarm to the monitoring if the buffer size threshold is exceeded. The minimum must be 10240 bytes (10 KB).

Agent Filter Level

Select a filter level stored in the system default table applied to monitoring system when no specific definition is applied. Each PMU definition has a filter level set to one of the following: standard, verbose, or debug. Marking a PMU as standard, verbose, or debug will tell JD Edwards EnterpriseOne Performance Monitor system whether or not the PMU metrics should be captured based on what level JD Edwards EnterpriseOne Performance Monitor is capturing data at. JD Edwards EnterpriseOne Performance Monitor filter level can be one of the following: standby (no metric data captured), standard (only standard PMUs captured), verbose (standard and verbose PMUs captured), or debug (all PMUs captured).

4.4 Modifying System Definitions

Access the System Definitions - System Definition Revisions form.

A system refers to a particular monitored system. System definitions are created automatically when the first agent of a monitored system registers with the monitoring system. The database name and GUID (a JD Edwards EnterpriseOne value used to uniquely identify a JD Edwards system) are provided by the agent during its registration process.

This section describes the properties and configuration options for each monitored system.

System ID

Identifies each monitored system. JD Edwards automatically generates this value incrementally. System definitions are created automatically when the first agent of a monitored system registers with the monitoring system.

Database Name

Identifies the name assigned to the database during installation, such as HPDEVORAP or HP9000. - - - FORM SPECIFIC HELP - - - The name of the database running on the monitored system. The monitoring system automatically inserts this value when it recognizes and creates a monitored system.

Description

Identifies the description for JD Edwards EnterpriseOne Performance Monitor usage. - - - FORM SPECIFIC HELP - - - A description of the monitoring system to assist recognition. The default value is the database name.

UID

Identifies the unique identifier for JD Edwards EnterpriseOne Performance Monitor defined systems. The monitoring system automatically inserts this value when it recognizes and creates a monitored system.

Archive Mode

Displays the archive mode you set specifies how the archive program should process the performance data stored in the monitoring database.

Allow User Trace

Enables authorized users connected to this monitored system to start a specific performance trace.

Agent Heartbeat Interval (sec)

Indicates the interval at which agents that do not have any performance data to report or that are in standby mode connect to the monitor servlet to be notified of any configuration changes. If agents post data to the monitoring system before this interval expires, they will be notified of any configuration changes and the timer will be reset. The lower the number, the greater the responsiveness of the agents to configuration changes, but the greater the network traffic. This value cannot be set to zero.

PMU Timeout (days)

Indicates the interval in which an open PMU is considered timed out. PMU timeouts are measured in days. The PMU timeout value cannot be set to zero. After the specified interval, the system assumes that a PMU that has not completed encountered an error and should no longer be considered open. The reaper program moves timed out PMUs from the current PMU tables to the history PMU tables and sets the status to Reaper Timed Out.

Agent Buffering Interval (sec)

Specifies the rate (in seconds) at which an agent sends performance data to the monitoring system.

This value cannot be set to zero.

A smaller interval decreases the delay between the time when the monitored system generates performance data and the time it is displayed on the monitoring system. Larger intervals enable more efficient transmission of performance data across the network because the system can consolidate the data into packets. The larger the interval, the greater the Agent Max Buffer size should be set.

Agent PMU Sample Rate (1/X)

Enables you to reduce the amount of PMU data generated by monitoring just 1 of every N server trips. Sampling does not affect PMUs initiated in a performance trace.

Agent Max Buffer Size (bytes)

Determines the maximum size of the buffer containing performance data. This enables you to cap the amount of data being stored by the agent on the monitored system and the amount of data sent across your network. If this limit is reached, the agent automatically discards new performance data until the current data has been posted to the monitor servlet. The agent posts an alarm to the monitoring if the buffer size threshold is exceeded. The minimum must be 10240 bytes (10 KB).

Last Updated User ID

Specifies the last user to update the record.

Last Updated Date/Time

Specifies the Utime when the record was last updated.

4.5 Viewing Agent Definitions

Access the Agent Definitions - Agent Definition Revisions form.

Agent definitions enable you to view the details about the agents in monitored systems.

System ID

Identifies each monitored system. JD Edwards EnterpriseOne automatically generates this value incrementally. System definitions are created automatically when the first agent of a monitored system registers with the monitoring system.

Database Name

Identifies the name of the database running on the monitored system. The monitoring system automatically inserts this value when it recognizes and creates a monitored system.

Agent ID

Identifies an agent within a domain. This is automatically generated by the monitor the first time an agent registers.

Domain Monitor

Displays as Yes or No. If yes, then this agent is responsible for sending resource events for its host and domain to the monitor at the specified sampling rate for the monitored system.

Domain Name

Identifies the name of the domain in which an agent operates.

Domain Type

Indicates whether the domain is an application server, a web server, or a Process Scheduler server domain.

Domain Host/Port

Identifies the name or IP address of the server on which the domain resides including the port number to which the domain listens for requests.

Domain Directory

Specifies the directory in which the domain is installed on the server.

Server Instance

Specifies the collator server instance number.

Agent Inactive

Select this box to make the agent inactive. If selected, the agent's events and PMUs do not appear in JD Edwards EnterpriseOne Performance Monitor forms showing current information. You can still view information about events and PMUs sent by inactive agents using the forms that display historical information.

4.6 Setting Agent Filter Options

Agent Filters - Agent Filter Revisions form.

Agent filters determine the amount of performance data that is generated and sent to the monitoring system. Depending on the situation, different levels of performance data may be needed to assist in your performance-related decisions. The levels range from no information to extremely detailed information.

Each type of PMU and event is associated with a filter level, which is the lowest level at which the system generates performance data for that PMU or event.

System ID

Identifies each monitored system. The JD Edwards EnterpriseOne system automatically generates this value incrementally. System definitions are created automatically when the first agent of a monitored system registers with the monitoring system.

Database Name

Identifies the name assigned to the database during installation, such as HPDEVORAP or HP9000. - - - FORM SPECIFIC HELP - - - The name of the database running on the monitored system. The monitoring system automatically inserts this value when it recognizes and creates a monitored system.

Description

Identifies the description for JD Edwards EnterpriseOne Performance Monitor usage. - - - FORM SPECIFIC HELP - - - A description of the monitoring system to assist recognition. The default value is the database name

Last Update User ID

Specifies the last user to update the record.

Last Update Date/Time

Specifies the Utime when the record was last updated.

4.7 Scheduling the Reaper Program

The reaper process (R95900/XJDE0001) maintains the tables JD Edwards EnterpriseOne Performance Monitor uses to store performance data for current, real-time processing. It should be scheduled to run (via scheduler) periodically based on the filter level you are capturing data at and the load your enterprise is under. Performance of JD Edwards EnterpriseOne Performance Monitor will degrade if the tables JD Edwards EnterpriseOne Performance Monitor uses to store performance data for current, real-time processing are not maintained by the reaper process.

When JD Edwards EnterpriseOne Performance Monitor gets notified that a PMU has finished (it receives a STOP for an open PMU), it:

When the reaper program (R95900/XJDE0001) runs, it:

Caution:

If you do not schedule the reaper program to run often enough, the F95960 table will grow very large over time, and it may contain many old, open PMUs.