OpenEdge Management supports setting up individual TCP and/or UDP monitors. The TCP monitor attempts to connect to a TCP port and reports status and response time. The TCP monitor can be useful in determining the status and response times for servers that listen on a TCP port. This includes servers such as mail, FTP, and Web servers.
Note: OpenEdge Management supports a default operator e-mail TCP monitor identified as a Simple Mail Transfer Protocol (SMTP) SMTP_Mail. You can set host, port, and default e-mail recipient values in the Default alert recipient section of the OpenEdge Management Configuration page. However, you can edit values as you would any user-defined TCP resource monitor.
The UDP monitor attempts to communicate with a UDP port and reports status and response time.
Note: Monitoring a NameServer using UDP resource monitors is not recommended. If you set up a UDP monitor to monitor a NameServer UDP listener port, the NameServer will detect the UDP messages. However, the NameServer will inspect the UDP messages and reject them because they do not follow the convention expected by the NameServer. Consequently, the NameServer will log error messages to indicate that invalid message requests are being received.
To define a TCP resource monitor:
1. Select Resources > New > TCP in the OpenEdge Management console menu.
The Edit TCP Monitor page appears.
2. Enter values in the Name and Description fields.
3. In the Host field, enter either the name of the host or the IP address where the port is located.
4. In the Port field, enter the number of the port.
5. Ensure that the Enabled field is checked to begin monitoring.
6. Click Save.
The Create Monitoring Plan page appears.
7. Update as necessary the default values, which provide for monitoring plan and rule definition fields. See Reviewing network resource default values for details about the Alert if response time greater than and OR no response within fields.
8. Click Save.
The TCP resource summary page appears displaying the monitoring plans.
