The TcpPortTest monitors the number of the TCP connections to different source/port and destination/port combinations on a server. This page depicts the default parameters that need to be configured for the TcpPortTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed. 

• In the TARGETAPPPORTS text box, define the the source/port and/or destination/port combinations to be monitored. This parameter is specified in the format:

  PatternName:LocalIp:LocalPort@RemoteIP:RemotePort

  PatternName is a unique name by which the pattern being defined is to be identified. This is the name that would appear alongside the test name in the monitor interface.

  When configuring this parameter, decide whether you are monitoring connections to the application or connections from the application to other applications. If the connections to an application running on the local system are to be monitored, the LocalIp and LocalPort become relevant. For example, if the number of connections to a web server on the local system have to be monitored, the LocalIp can be "*" (indicating that all the local IP addresses are to be considered), and the LocalPort can be "80", to monitor the web server running on port 80. On the other hand, if the web server is running on a specific IP address, specify this IP address in the LocalIp field.

  The RemoteIP is the IP address of the remote end of the TCP connection. In the example above, TCP connections can be established from any remote address to the web server. Hence, the RemoteIP should be "*" in this example. Likewise, the RemotePort is the TCP port being used to connect to the application being monitored. In the example above, clients can use any TCP port to connect to the application, and hence, the RemotePort setting should be "*".

  To conclude, to monitor all the connections to a web server running on port 80 and configured to use an IP address 192.168.10.8, the TARGETAPPPORTS specification should be WebUsage:192.168.10.8:80@*:*.

  Suppose the administrator also wants to monitor the TCP connections going out of the web server to a J2EE application server that is listening on IP address 192.168.10.20 on port 6010, then the corresponding TARGETAPPPORTS configuration should be J2EE:*:*@192.168.10.20:6010. This indicates that the clients can be using any IP address/port to connect to the application server.

  The complete TARGETAPPPORTS specification for this example, will hence be:

  WebUsage:192.168.10.8:80@*:*,J2EE:*:*@192.168.10.20:6010

  As another example, you can also instruct the eG Enterprise sytem to monitor all TCP connections from IP addresses in the range 192.168.10.30-192.168.10.39, to IP addresses in the range 192.168.10.40-192.168.10.49. The pattern specification for this would be:

  Connection34:192.168.10.3*:*@192.168.10.4*:*

• Once the above values are provided, click on the UPDATE button to register the changes made.