IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Perform a silent installation of IBM Tivoli Monitoring > Perform a silent installation on a Linux or UNIX computer
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Linux/UNIX: Installing and configuring the Tivoli Enterprise Monitoring Automation Server in silent mode
A silent installation runs on its own and does not require you to provide input to dialog boxes or monitor the installation. This configuration option allows for an unattended and automatic installation and configuration of the Tivoli Enterprise Monitoring Automation Server.
To install and configure the Tivoli Enterprise Monitoring Automation Server in silent mode, using the silent response file:
- On the product installation media, locate the silent_install.txt file and copy it into a temporary directory on the target system.
- Edit the silent_install.txt file and perform the following actions so that only the Tivoli Enterprise Monitoring Automation Server is installed:
- comment out INSTALL_PRODUCT=all
- uncomment INSTALL_PRODUCT=as
- Invoke the following command to perform the silent installation:
install.sh -q -h <candlehome> -p <silent_response_file>
Results
The configuration file for the Tivoli Enterprise Monitoring Automation Server is located in candlehome/samples/as_silent_config.txt. This is an example of configuration file content for the silent installation of the Tivoli Enterprise Monitoring Automation Server:
# Enable Registry Services access KAS_REGISTRY_SERVICES_ENABLED=YES # The protocol of the Registry Services # Available protocols must be specified as follows: # # =HTTP # =HTTPS # Protocol is HTTP or HTTPS. # KAS_REGISTRY_SERVICES_URL_PROTOCOL=HTTP # The hostname of the Registry Services KAS_REGISTRY_SERVICES_URL_HOSTNAME= # The HTTP port of the Registry Services KAS_REGISTRY_SERVICES_URL_HTTP_PORT=16310 # The HTTPS port of the Registry Services KAS_REGISTRY_SERVICES_URL_HTTPS_PORT=16311 # Set user authentication for Registry Services KAS_REGISTRY_SERVICES_AUTH=YES # The name of a user that is authorized to access the Registry Services # server. This must be a valid WebSphere user name KAS_REGISTRY_SERVICES_USER= # The password of the user that is authorized to access the Registry Services server KAS_REGISTRY_SERVICES_PASSWORD= # When the OSLC Performance Monitoring service provider is configured for a Hub monitoring server # that is enabled for Hot Standby, a value must be configured for the acting hub alias. The acting # hub alias must match the acting hub alias configured for the OSLC Performance Monitoring service # provider associated with the other Hub monitoring server in the Hot Standby environment. # The acting hub alias is used to create a single service provider entry in Registry Services # for the Hot Standby environment and each Hot Standby environment must have a unique alias value. KAS_REGISTRY_SERVICES_ACTING_HUB_ALIAS= Note: The acting hub alias cannot exceed 128 characters. Valid characters are alphanumerics, -, _, and period. ################## AUTOMATION SERVER CONNECTION CONFIGURATION ################## # The protocol that the automation server uses # for incoming resource query requests. # Available protocols must be specified as follows: # # =HTTP # =HTTPS # KAS_SERVER_PROTOCOL=HTTP # The port number that the automation server uses # for incoming resource query HTTP requests KAS_SERVER_HTTP_PORT=10001 # The port number that the automation server uses # for incoming resource query HTTPS requests KAS_SERVER_HTTPS_PORT=10002
What to do next
After the installation is complete you can reconfigure, start, or stop the Tivoli Enterprise Monitoring Automation Server.If a monitoring server was also installed by default, you can reconfigure, start, or stop the monitoring server after the installation has completed.
Parent topic:
Perform a silent installation on a Linux or UNIX computer