IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Install IBM Tivoli Monitoring > Install Tivoli Enterprise Monitoring Automation Server

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

---

Linux or UNIX: Installing a Tivoli Enterprise Monitoring Automation Server

Use the following steps to install the automation server on a Linux or UNIX computer.

A Tivoli Enterprise Monitoring Automation Server requires a locally installed hub monitoring server (see Install the hub Tivoli Enterprise Monitoring Server).

1. In the directory where you extracted the installation files, run:

   ./install.sh  

2. When prompted for the IBM Tivoli Monitoring home directory, press Enter to accept the default...
   /opt/IBM/ITM

   To use a different installation directory, type the full path to that directory and press Enter.

   Do not specify the path of the directory containing ./install.sh as the IBM Tivoli Monitoring home directory. On certain platforms, this can cause the plug-in JAR files to overwrite themselves and become zero length files. The installation will fail as a result.

   In addition, do not use the number sign (#) or exclamation mark (!) characters anywhere in your installation directory path.

3. If the directory you specified does not exist, you are asked whether to create it. Type 1 to create this directory.

   The following prompt is displayed:

   Select one of the following:
   1) Install products to the local host.
   2) Install products to depot for remote deployment (requires TEMS).
   3) Install TEMS support for remote seeding
   4) Exit install.
   Please enter a valid number:

   Type 1 to start the installation and press Enter.

   The end user license agreement is displayed. Press Enter to read through the agreement.

4. Type 1 to accept the agreement and press Enter.

   If you are upgrading IBM Tivoli Monitoring from global GSKit enabled to local GSKit enabled, the following text is displayed:

   Local GSKit has been installed for IBM Tivoli Monitoring. The global GSKit installation 
   will no longer be used by IBM Tivoli Monitoring. It will not be uninstalled automatically, 
   because it might be used by other applications. You may uninstall it manually, if IBM 
   Tivoli Monitoring is the only application utilizing it.

5. Type a 32-character encryption key and press Enter.

   To the default key, press Enter without typing any characters.

   1. Do not use any of the following characters in your key:

      &	ampersand
      |	pipe
      '	single quote
      =	equal sign
      $	dollar sign

      In addition, do not specify double-byte (DBCS) characters.

   2. Document the value you use for the key. Use this key during the installation of any components that communicate with this monitoring server.

   If you are upgrading IBM Tivoli Monitoring instead of a pristine installation, you are prompted by the installer to upgrade the common prerequisite components for agents and servers.

   The product packages available for this operating system and component support categories are listed.

6. Type the number that corresponds to your operating environment.

   For a new installation, type 1 IBM Tivoli Monitoring components for this operating system. This option installs all components for your operating system.

7. Type 1 to confirm the selection of product packages in step 7.

8. Type the number that corresponds to the Tivoli Enterprise Monitoring Automation Server. Press Enter.

   The automation server requires a locally installed hub monitoring server. If no monitoring server is installed, type the number that corresponds to the Tivoli Enterprise Monitoring Server.

9. Type 1 to confirm the installation.

   If you are installing the Tivoli Enterprise Monitoring Server at this time, the monitoring server application support is also installed. You are prompted to answer the following questions as the installation completes:

   - Please enter TEMS name [ TEMS is default ]:
   
   - Do you want to install additional products or product support packages? 
   [ 1=Yes, 2=No; default is "2"]
   
   - Do you want to seed product support on the Tivoli Enterprise Monitoring Server?
   [ 1=Yes, 2=No; default is "1"]
   
   - Type your selection here [ Number "3" or "NEW" is default]:

10. If the IBM Tivoli Monitoring environment is not already secured you will be asked at this point if you want to secure it. [1=Yes, 2=No; default is "1"]. If the IBM Tivoli Monitoring environment is already secured this question is skipped. The product installation process creates the majority of directories and files with world write permissions. IBM Tivoli Monitoring provides the secureMain utility to help you keep the monitoring environment secure. You can secure your installation now, or manually execute the secureMain utility later. See Securing the IBM Tivoli Monitoring installation on Linux or UNIX

What to do next

The next step is to configure your automation server.

After you have configured your automation server, you can perform the following steps:

• To configure the Performance Monitoring service provider to use the Security Services component of Jazz for Service Management to authenticate OSLC client applications, you also must set the KAS_SECURITY_SERVICES_ENABLED environment variable to Yes in the Tivoli Enterprise Monitoring Automation Server's environment file and restart the monitoring automation server.

• After you install application support for agents that have an OSLC template, restart the automation server. You must restart the automation server if the application support is manually installed or is installed using the self-describing agent feature.

After performing these steps, IBM Tivoli Monitoring is ready to integrate with other products using OSLC linked data interfaces.

Parent topic:

Install Tivoli Enterprise Monitoring Automation Server

---

+

Search Tips   |   Advanced Search