IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Perform a silent installation of IBM Tivoli Monitoring > Create and using a Windows response file

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

---

Windows: Installing and configuring the Tivoli Enterprise Monitoring Automation Server in silent mode

This configuration option allows for an unattended and automatic installation and configuration of the Tivoli Enterprise Monitoring Automation Server. A locally installed hub monitoring server is a prerequisite for the Tivoli Enterprise Monitoring Automation Server. That means the hub monitoring server is installed together with the Tivoli Enterprise Monitoring Automation Server, unless the hub monitoring server is already installed.

If you are installing the hub monitoring server as part of this procedure then you must also uncomment the [CMS_CONFIG] section in your silent_server.txt file. If the hub monitoring server is already installed then you do not need to include the [CMS_CONFIG] section in your silent response file.

To install and configure the Tivoli Enterprise Monitoring Automation Server in silent mode, using the silent response file:

1. On the product installation media, locate the silent_server.txt file in the WINDOWS directory and copy it into a temporary directory on the target system.

2. Edit the silent_server.txt file and perform the following actions so that only the Tivoli Enterprise Monitoring Automation Server is installed:

   1. uncomment: License Agreement=I agree to use the software only in accordance with the installed license.

   2. uncomment: Install Directory=C:\IBM\ITM

      Accept the default location or specify another directory location.

   3. uncomment: Install Folder=IBM Tivoli Monitoring

   4. uncomment: EncryptionKey=IBMTivoliMonitoringEncryptionKey

   5. uncomment: KMSWICMS=Tivoli Enterprise Monitoring Server

   6. uncomment: KASWICAS=Tivoli Enterprise Monitoring Automation Server

3. Edit the following section of the silent_server.txt file to configure the Tivoli Enterprise Monitoring Automation Server:

   ;--------------------------------------------------
   ;    Tivoli Enterprise Monitoring Automation Server
   ;--------------------------------------------------
   ;
   [CAS_CONFIG]
   ;
   ; Enable Registry Services access?
   ; Default value is No. Uncomment your answer:
   ;
   ;KAS_REGISTRY_SERVICES_ENABLED=Yes
   ;KAS_REGISTRY_SERVICES_ENABLED=No
   ; 
   ; The host name of the Registry Services provider registry.
   ;KAS_REGISTRY_SERVICES_URL_HOSTNAME=
   ;
   ; The protocol used by Registry Services provider registry. 
   ; Available protocols must be specified as follows:
   ;
   ; =HTTP
   ; =HTTPS
   ;
   ;KAS_REGISTRY_SERVICES_URL_PROTOCOL=HTTP
   ;
   ; The port number used by Registry Services provider registry for HTTP connection.
   ;KAS_REGISTRY_SERVICES_URL_HTTP_PORT=16310
   ;
   ; The port number used by Registry Services provider registry for HTTPS connection.
   ;KAS_REGISTRY_SERVICES_URL_HTTPS_PORT=16311
   ;
   ; Set user authentication for Registry Services?
   ; Default value is No. Uncomment your answer:
   ;
   ;KAS_REGISTRY_SERVICES_AUTH=Yes
   ;KAS_REGISTRY_SERVICES_AUTH=No
   ;
   ; The name of a user that is authorized to access Registry Services.
   ; This must be a valid WebSphere user name.
   ;KAS_REGISTRY_SERVICES_USER=
   ;
   ; The password of the user that is authorized to access Registry Services.
   ;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.
   
   ; The protocol that the Tivoli Enterprise Monitoring 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 Tivoli Enterprise Monitoring Automation Server
   ; uses for incoming resource query HTTP requests.
   ;KAS_SERVER_HTTP_PORT=10001
   ;
   ; The port number that the Tivoli Enterprise Monitoring Automation Server
   ; uses for incoming resource query HTTPS requests.
   ;KAS_SERVER_HTTPS_PORT=10002

   The acting hub alias cannot exceed 128 characters. Valid characters are alphanumerics, -, _ , and period.

4. Invoke the following command to perform the silent installation:

   start /wait setup /z"/sf<silent_reponse_file>"/s/f2"<silent_install_log>"

   where:

   silent_response_file

   Is the absolute path to the edited silent_server.txt file.

   silent_install_log

   Is the absolute path to the silent installation output log file.

5. After the installation is complete you can reconfigure, start, or stop the Tivoli Enterprise Monitoring Automation Server.

Parent topic:

Create and using a Windows response file

---

+

Search Tips   |   Advanced Search