JD Edwards EnterpriseOne Server Manager (Windows)

Use this SAM application monitor template to monitor the health of JD Edwards EnterpriseOne Server Manager by checking for critical events in the agent log file and monitoring critical processes and TCP ports.

Prerequisites

Assign this template to Windows servers that host the JD Edwards EnterpriseOne Server Manager.

WinRM must be installed and properly configured on the target server.

Credentials

Administrator on target server.

Component monitors

Server Manager Agent Log File

Returns new server manager events from the last polling period. The server manager agent log contains events related to: registering/installing E1 managed instances; registering and managing IBM WebSphere and Oracle Application Server; managing the configuration file(s) for E1 managed instances; starting/stopping E1 servers and the J2EE servers; performing tools release upgrades/downgrades for E1 servers; discovering and sending log files to the management console for viewing.

The returned values are as follows:

• SEVERE – The number of SEVERE messages. SEVERE messages occur when a critical error has occurred from the perspective of the agent. Critical errors are non-recoverable errors and require immediate attention. An example would be a critical problem with initializing the agent that would prevent it from starting or functioning properly. In the message fields, this monitor also returns the SEVERE message.
• WARNING – The number of WARNING messages. WARNING messages denote an abnormal or unexpected result occurred that is recoverable, from the perspective of the agent. An example would include a failure while changing the tools release of an E1 server. It is a significant problem; however, the agent will recover so this is considered a warning. In the message fields, this monitor also returns the SEVERE messages.
• INFO – The number of INFO messages. INFO message denotes informative messages providing contextual information as to what the agent is doing. An E1 server that is started using SM would have a log message indicating this at the INFO level.
• CONFIG – The number of CONFIG messages. CONFIG messages are not commonly used in SM. A message at the configuration level is simply a means for logging information particular to that installation, such as the platform of the server.
• FINE – The number of FINE messages. FINE messages are a lower level message still intended as human readable that provides insight into what the agent is doing. This can be thought of as a standard "debug" message.
• FINER – The number of FINER messages. FINER message is an even lower level trace of the debug message. Messages are classified at this level rather than FINE if they occur frequently and are less likely to be of interest.

This monitor uses the following arguments:
path_to_agent_log_file,agent_name
where
path_to_agent_log_file – Full path to server manager log file;
agent_name – Agent name. This argument takes part only in generating temporary files. Change this if you monitor several agents on the same target host.

Example:
c:\jre_home\logs\e1agent_0.log,agent1

Management Console HTTP Port

Tests the ability of a Management HTTP Console to accept incoming sessions. By default, it monitors TCP port 8999.

Management Server JMX Port

Tests the ability of a Management Server JMX to accept incoming sessions. By default, it monitors TCP port 14501. This port can be changed in the Server Manager HTTP Console in the Management Agents section.

Management Agent Port

Tests the ability of a Remote Management Agent to accept incoming sessions. By default, it monitors TCP port 14502. This port can be changed in the Server Manager HTTP Console in the Management Agents section.

Management Agent Process

Returns the CPU and memory usage of the Management Agent process (steagent.exe).