IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Deployment phase > Install the infrastructure components
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Configuration checklist
Use the following checklist for your configuration.
- Install all Tivoli Monitoring core components (portal server, monitoring server, Warehouse Proxy Agent, and Summarization and Pruning Agent) so there can be a section for each component.
- Verify the correct protocols are selected. If SPIPE is chosen, make sure the encryption key string used is the same across the Tivoli Monitoring enterprise environment.
- Verify the correct configurations are performed regarding data warehousing.
After installing the hub and remote monitoring server, ensure that you do not attempt to start a second kdsmain instance, which can corrupt your environment. Modify the monitoring server startup CandleServer script so that it looks as follows:
# #Local change to check for another running kdsmain # if [ "$action" = "start" ] then if ps -ef | grep -v grep | grep kdsmain then echo "There is a KDSMAIN running already" exit fi fi
Some users run multi-hub monitoring servers on a single server for the development and test environments using different ports. If that is the case, then the previous script cannot work because kdsmain is running for the other hub. If that is the case, use extreme care to ensure that you do not accidentally start a second kdsmain for a given hub.
Do not enable warehousing at this time. Wait until all the agents for phase one have been installed and started, and the situations have been distributed.
Disable all the default situations by unassigning the managed system group and any agents present in the Assigned check box.
Create the managed system groups before creating the situations.
Distribute all newly created situations with naming conventions to the customized managed system group and not to *NT_SYSTEM, *ALL_UNIX. You must customize your situation thresholds before forwarding your events to Tivoli Enterprise Console or Netcool/OMNIbus, which ensures that you do not cause any event storms.
You can enable event forwarding at this time. Install your first 50 agents.
Use the installation method of your choice, install several OS monitoring agents. These can be installed locally on the server or through the remote deployment mechanism. Detailed steps on remote deployment are included in the following sections.
Because the remote deployment of application agents depends on having an OS agent running on the server, always deploy the OS agents first.
Parent topic:
Install the infrastructure components