You can use OpenEdge Management to set up resource monitors for non-OpenEdge resources. To determine the availability of some non-OpenEdge network resources, you follow network discovery procedures that allow you to search for ports that are present on your network.
This chapter describes network discovery procedures and explains how to create specific port connections for the following network resources:
TCP port — You can set up resource monitors for ports that use Transmission Control Protocol (TCP) to monitor machine availability and enable a data connection between two machines.
UDP port — You can set up resource monitors for ports that use User Datagram Protocol (UDP) to determine the availability of these ports enabling a given machine to broadcast messages over a network.
PING (ICMP) — Packet Internet Groper (PING) is a utility used to determine whether a specific IP address is accessible. It works by sending a packet to the specified address and waiting for a reply. ICMP supports packets that can contain error, control, and informational messages. OpenEdge Management allows you to set up resource monitors on a PING to monitor the availability of specific machines and IP addresses.
HTTP Monitor — Hypertext Transfer Protocol (HTTP) is an OpenEdge Management-supported resource monitoring feature that allows you to monitor various aspects of a Universal Resource Locator (URL). Businesses that rely heavily on the Internet need to ensure that their company's Web site is reliable, accurate, and accessible. The HTTP Monitor supports an authentication feature. You cannot use the discovery process with the HTTP Monitor resource process.
Caution: Give serious consideration to the types of devices for which you are creating network resources. OpenEdge Management does not allow you to PING broadcast or multi-cast addresses. However, it is possible to PING other devices, such as hubs, switches, and routers. Polling devices such as these can lead to network problems.