IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
Configure a Managing Server on a host with multiple network interfaces and NATs
The Managing Server always binds to one network interface (IP address) only, even on a host with multiple network interfaces
If the Managing Server always exposes a specific IP to all data collectors:
- On the Managing Server side, in setenv.sh (in MS_home/bin), set KERNEL_HOST01 to the IP address of the Managing Server.
Set the following parameters:
- am_socket_bindip=<IPaddress_MS>
- am_socket_exportip=<IPaddress_MS>
- On the Managing Server side, in wdctl.sh, klctl.sh and psctl.sh (in MS_home/bin), add java.rmi.server.hostname to the java command line in the start section of the script and set it to IP address of the Managing Server.
- You need to edit the MS_home/etc/ve.properties file's kernel.codebase value to point to the right IP address. This also impacts DHCP where you need to hardcode the dynamic DNS host name rather than an IP address in the MS_home/etc/ve.properties file.
- In MS_home/etc/ms.properties, you need to modify kernel.hosts to indicate the IP address of the Managing Server: kernel.hosts=<IPaddress_MS>CBSPort:RFSPort:RMIPort
By default, this would bekernel.hosts=<IPaddress_MS>9122:9120:9118
- In addition, if the Managing Server was installed on multiple servers, make the changes from Steps 1 through 3 on all the servers where the Managing Server is installed.
- On the data collector side, in the DC_home/runtime/appserver_version.node_name.server_name/appserver_version.node_name.server_name.datacollector.properties or DC_home/runtime/app_server_version.node_name.server_name/datacollector.properties file, make sure that the kernel.codebase and kernel.rfs.address properties have the right IP address for the Managing Server.
- On the data collector side, in the DC_home/itcamdc/etc/datacollector.policy file, make sure that the socket permissions (java.net.SocketPermission) are granted to the right IP address for the Managing Server.
The Managing Server may also expose different IP addresses to different data collectors because of Network Address Translation (NAT), even though it only binds to one IP address on the host. In this case:
- On the Managing Server side, in setenv.sh (in MS_home/bin), set KERNEL_HOST01 to the fully qualified domain name of the Managing Server (for example qaapp-lnx-s01.usca.ibm.com).
- On the Managing Server side, in wdctl.sh, klctl.sh and psctl.sh (in MS_home/bin), add java.rmi.server.hostname to the java command line in the start section of the script and set it to the fully qualified domain name of the Managing Server.
- In addition, if the Managing Server was installed on multiple servers, make the changes from Steps 1 and 2 on all the servers where the Managing Server is installed.
- On the data collector side, in the DC_home/runtime/appserver_version.node_name.server_name/ appserver_version.node_name.server_name.datacollector.properties or DC_home/runtime/app_server_version.node_name.server_name/datacollector.properties file, make sure that the kernel.codebase and kernel.rfs.address properties have the right IP address (or fully qualified host name) for the Managing Server.
- On the data collector side, in the DC_home/itcamdc/etc/datacollector.policy file, make sure that the socket permissions (java.net.SocketPermission) are granted to the right IP address (or fully qualified host name) of the Managing Server.
- Make sure that on the data collector side, the fully qualified host name of the Managing Server can be resolved to the correct IP address (You can use ping to verify this).
Parent topic:
Customization for the Managing Server on UNIX and Linux