Configuring a Data Collector to use the Port Consolidator

If you have a firewall, you can avoid allocation of an excessive number of ports in the firewall for multiple Data Collectors by configuring and using the Port Consolidator.

Perform the following procedure to configure a Data Collector to use the Port Consolidator:

1. Edit the DC_home/runtime/app_server_version.node_name.server_name/custom/datacollector_custom.properties file. Add the following lines to the end of the file:

   proxy.host=IP_address

   This is usually the same IP address as the Data Collector computer, but it could be different in a multiple IP or virtual host scenario. In any case, specify the same IP address as the one specified in the am.socket.bindip property in DC_home/itcamdc/etc/proxy.properties.

   proxy.port=port

   This is usually 8800. In any case, specify the same port specified in the PROXY_PORT property in DC_home/itcamdc/bin/proxyserverctrl_*.
   Note:

   1. Do not use the loopback address for the IP address. Use a valid IP address for the local system.
   2. proxy.port must match the port number for PROXY_PORT that is specified in the startup script you run in Step 4.
2. Restart the instance of the application server that is being monitored by the Data Collector.
3. From a command prompt, move to the directory DC_home/itcamdc/bin.
4. Start the Port Consolidator using one of the following commands:

   Table 1. Command for starting the Port Consolidator

   Windows	proxyserverctrl_j2ee.bat start
   UNIX and Linux	./proxyserverctrl_j2ee.sh start

   Do not close the command prompt window.

   Note: The value for PROXY_PORT that is specified in the script must match the value that you specified for proxy.port in Step 1.
5. Open the Self-Diagnosis page of the Visualization Engine (Application Monitor) user interface, and check to see that the following components are listed:
   • COMMANDAGENTPROXY
   • KERNELPROXY
   • PROBECONTROLLERPROXY
6. Verify that the Data Collector is using the Port Consolidator:
   1. Look for the message labeled CYND4051I in one of the following files:

      Table 2. Location of the CYND4051I message

      Windows	DC_home\logs\CYN\logs\node_name.server_name\java_msg_log_file. For example: C:\IBM\ITM\TMAITM6\wasdc\7.1.0.2\logs\CYN\logs\tivx44Node02.server1\msg-dc-ParentLast.log
      UNIX and Linux	DC_home/logs/CYN/logs/node_name.server_name/java_msg_log_file. For example: /opt/IBM/AD7101_0505/li6263/yn/wasdc/7.1.0.2/logs/CYN/logs/tivx44Node02.server1/msg-dc-ParentLast.log

      That message includes the text Join Proxy Server and Kernel successfully.

   2. From a new command prompt, move to the directory DC_home/itcamdc/bin, and enter one of the following commands:

      Table 3. Entering the proxyserverctrl_j2ee command

      Windows	proxyserverctrl_j2ee.bat list
      UNIX and Linux	./proxyserverctrl_j2ee.sh list

      You will see the Data Collector listed as one Service type, PPECONTROLLER. Keep this command prompt window open for future use.

7. Verify the Data Collector connection to the Port Consolidator (again) by entering one of the following commands:

   Table 4. Entering the proxyserverctrl_j2ee command

   Windows	proxyserverctrl_j2ee.bat list
   UNIX and Linux	./proxyserverctrl_j2ee.sh list

   You will now see the Data Collector listed as two Service types, PPECONTROLLER and PPEPROBE.

   The Data Collector is configured to use the Port Consolidator.