IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

---

Performing a three phase Managing Server installation with three logins on Linux and UNIX systems - UNIX

You can perform a three phase Managing Server installation, using three different logins. The logins are:

• Managing Server installation - this login is the Managing Server installation user.

• Managing Server Application Monitoring user interface (Visualization Engine) installation - this login is the WebSphere user.

• Database instance - this login is the database administrator user.

With this process, you have the option of installing the Visualization Engine on a separate server, to make more resources available for it. You can also install the Visualization Engine and the other Managing Server components on the same server.

If you install the Visualization Engine on a separate server, the WAS only needs to be installed on the Visualization Engine server and not on the server where the Managing Server files were installed (called the main server in this chapter). However, you will need to copy the java diractory from the Visualization Engine server to the main server.

The following section describes the three phases involved:

• First Phase - in this phase, you login as the Managing Server installation user and install the Managing Server files.

• Second Phase - in this phase, you login as the WebSphere user and deploy the ITCAM for Application Diagnostics Managing Server component and register the configuration in IBM WAS.

• Third Phase - in this phase, you login as the database instance user (DB2 or Oracle) and give the user write and execute access permission to db2-remote-scripts.tar or the oracle-remote-scripts.tar.

The following procedure describes the steps involved in a three phase installation:

1. Complete the following steps to prepare for the three phase installation:

   1. Ensure WAS version 6.0.2 or higher is installed with Global Security Enabled.

   2. Before installing Managing Server, you will copy the installation image to the server where you will be performing the installation. Create the following directory to hold the installation image: Managing_Server_/path/to/install

   3. Copy the ITCAM_INSTALL.properties file from Managing_Server_/path/to/install/silent to Managing_Server_/path/to/install. If you are using a CD to install the Managing Server, you do not need to specify the file name when you are copying ITCAM_INSTALL.properties.

   4. Edit the ITCAM_INSTALL.properties file according to your WAS and database environment. See Configure an existing database environment to work with the Managing Server on Windows.

2. Complete the following steps to install the Managing Server components:

   1. Login as the Managing Server installation user. Ensure this user has the permission to run JAVA.

   2. Run the following command to install the Managing Server files:

      <JAVA_HOME_DIRECTORY>/bin/java -cp lib/javainstaller.jar:lib/tk_jflt.jar:
        lib/itcamfwas.jar:setup_MS.jar 
        com.ibm.tivoli.javainstaller.MSFileManagement <DBSchemaPassword>

      For example:

      >/opt/IBM/Java142/bin/java -cp lib/javainstaller.jar:lib/tk_jflt.jar:
            lib/itcamfwas.jar:setup_MS.jar 
              com.ibm.tivoli.javainstaller.MSFileManagement itcam610

3. The Managing Server installation user and the WebSphere user must have the following permissions:

   • The Managing Server installation user must have read and execute permission to the WebSphere installation directory.

   • The WebSphere user must have read, write and execute permission to the Managing Server installation image directory.

   • The WebSphere user must have read and write permission to the Managing Server Log directory.

   To assign these permissions:

   1. To assign the Managing Server installation user read and execute permission to the WebSphere installation directory, use the following command:

       chmod -R 755 <WebSphere DIR>

   2. To assign the WebSphere user read, write and execute permission to the Managing Server installation image directory (excluding the bin directory), use the following command:

      If both users are in the same group, use the following commands:

        chmod 770 <MS DIR> 
        chmod -R 770 <Sub directories MS DIR>  

      If both users are in different groups, use the following commands:

       chmod 777 <MS DIR>
       chmod -R 777 <Sub directories MS DIR>

      When assigning permissions to the Managing Server installation image sub directories, remember to exclude the bin directory.

   3. To assign the WebSphere user read and write permission to the Managing Server Log directory, use the following command:

      If both users are in the same group

       chmod -R 760 <MS log DIR>

      If both users are in different groups:

      chmod -R 766 <MS log DIR>

4. Complete the following steps to deploy and publish the Managing Server Visualization Engine (Application Monitor user interface) to the WAS:

   1. Log off.

   2. To install the Visualization Engine on a separate server, copy the MS_home (Managing Server installation) directory from the main server, where the previous steps were performed, to exactly the same location on the new Visualization Engine server. Complete step 4.c on the Visualization Engine server; complete subsequent steps on the main server.

   3. Login as the WebSphere user, and run the following command:

        <JAVA_HOME_DIRECTORY>/bin/java -cp lib/javainstaller.jar:lib/tk_jflt.jar:
          lib/itcamfwas.jar:setup_MS.jar
           com.ibm.tivoli.javainstaller.MSWASManagement <WASGSPassword> 
            <DBSchemaPassword>
          

      For example:

       >/opt/IBM/Java142/bin/java -cp lib/itcamfwas.jar:lib/tk_jflt.jar:
              lib/javainstaller.jar 
                com.ibm.tivoli.javainstaller.MSWASManagement admin itcam610

      <WASGSPassword> represents the WAS Global Security password. If this password was already set in the soap.client.props file, you can ignore this property when you run the command to deploy MSVE.

   4. If you have installed the Visualization Engine on a separate server:

      1. Copy the java (JVM) directory from AppServer_home on the Visualization Engine server to any location on the main server. On the main server, set the JAVA_HOME environment variable to the full path to this directory.

      2. Copy the AppServer_home/lib directory from the Visualization Engine host to the main server. Use the same absolute path as used on the Visualization Engine host.
      3. On the main server, in the file MS_home/bin/setenv.sh, adjust the setting for JAVA_HOME to the location of the copied java directory. In the same file, set the WAS_HOME variable to the absolute path of AppServer_home on the Visualization Engine host. (This is used to determine the location of the copied lib directory).

5. To give the DB2 Instance user write and execute access permission to Managing_Server_/path/to/install/base/scripts/db2-remote-scripts.tar:

   1. Login as the DB2 Instance user.

   2. Create a temporary directory under the DB2 Instance user home directory, copy the db2-remote-scripts.tar file from Managing_Server_/path/to/install/base/scripts to this temporary directory and untar it.

   3. Go to temporay_directory/db2/bin and run the following command as the DB2 Instance user:

      db2install.sh <DB2inst_username> <db_user> 
        <absolute_path_of_db2scripts_dir> <adminVEUser> <databaseName> 
              <DB2version> <databaseName>

      1. When prompted for a password, enter the password for the <schema user>.

      2. <DB2inst_username> must have dba privileges.

      3. <db_user> owns and can create the database tables for the product.

      4. <absolute_path_of_db2scripts_dir> is the absolute directory containing bin/db2install.sh, for example: /home/db2inst1/tmp/db2.

      5. <adminVEUser> is the user to be used when logging in and operating the Managing Server Application Monitor (MSVE) after installation and configuration.

      6. <databaseName> is the Managing Server Database name which is specified in ITCAM_INSTALL.properties.

6. To give the Oracle Instance user write and execute access permission to Managing_Server_/path/to/install/base/scripts/ oracle-remote-scripts.tar:

   1. Login as the Oracle instance user.

   2. Create a temporary directory under the Oracle home directory, copy the oracle-remote-scripts.tar file from Managing_Server_/path/to/install/base/scripts to the temporary directory and untar it.

   3. For the Oracle user, go to <temporay directory>/oracle/bin and run the following command as the Oracle System user.

        Usage: oracleinstall.bat oracle_sid sqlplus_user sqlplus_password tablespace 
          jdbc_user jdbc_password adminVEUser 

      For example:

      C:\oracle-remote-scripts\oracle\bin>oracleinstall.bat 
        octigate system zhu88jie octigate system zhu88jie Administrator

7. Restart WAS as the WebSphere user.

8. Restart Managing Server as the WebSphere user.

• What to do next
  

Parent topic:

Silent installation for the Managing Server on UNIX and Linux

---

+

Search Tips   |   Advanced Search