IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Tivoli Data Warehouse solutions: common procedures > Install multiple Warehouse Proxy Agents
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Set a permanent socket address for a proxy agent
In some network environments, use of the Global Location Broker default registration algorithm is not supportable and a specific monitoring server variable must be used.
This applies also when monitoring agents configure their connections as ephemeral (using KDC_FAMILIES=ip.pipe use:y ephemeral:y for instance).
KPX_WAREHOUSE_LOCATION is the variable that allows a fixed warehouse route to be delivered to connected agents. KPX_WAREHOUSE_LOCATION is an optional list of fully qualified, semicolon delimited network names and should be added in the monitoring server environment file located in different place depending on the platform:
- install_dir/CMS/KBBENV
- install_dir/config/kbbenv.ini
KPX_WAREHOUSE_LOCATION is used instead of the routing string currently derived by the monitoring server from the Location Broker monitoring. If the variable KPX_WAREHOUSE_LOCATION is set on the hub monitoring server, then the Warehouse Proxy Agent is registered in the Global Location Broker. If the variable is set on the remote monitoring server, then the Warehouse Proxy Agent is registered in the Local Location Broker. This variable has a maximum length of 200 bytes. The syntax is:
KPX_WAREHOUSE_LOCATION= family_protocol:network_address[port number];
For Tivoli Enterprise Monitoring Servers running on UNIX and Linux platforms only, you must reconfigure the Tivoli Enterprise Monitoring Server after adding KPX_WAREHOUSE_LOCATION to the kbbenv.ini file. This is required so that the new setting is propagated to the KBBENV file.
Parent topic:
Install multiple Warehouse Proxy Agents