IBM Tivoli Composite Application Manager for Application Diagnostics, V7.1.0.1

Managing Server - Custom installation steps


  1. If you are running the installation from a remote computer, enter xhost + hostname on the remote computer.

    The hostname is the fully qualified host name of the computer on which the Managing Server is being installed.

  2. Log in as the root user on the computer on which the Managing Server is being installed.

    It is possible to install the Managing Server as a non-root user

  3. If you are running the installation from a remote computer

      export DISPLAY=local_machine:0.0

    Where local_machine is the fully qualified host name of the computer where you are sitting.

    If you are running the installation from the computer where the Managing Server is being installed...

      export DISPLAY=localhost:0.0

  4. Export the LANG variable...

      export LANG=en_US.UTF-8

  5. If you have an existing installation of WAS, start the instance of IBM WAS to be used by the Managing Server.

  6. Complete one of the following options to start the installation:

    1. Use the LaunchPad interface

    2. To directly invoke the installation without using LaunchPad or to auto-generate a response file for a silent installation, launch the executable file for your operating system from the directory that contains your installation image:

        setup_MS_platform.bin

  7. The first window that is displayed is...

      Select log path

    Enter a location to store log files and click OK:

  8. The Welcome panel is displayed.

    If the installation program detects your computer does not match the basic prerequisites for starting the installation, a failure window opens instead of the Welcome panel. Refer to the information in the window to correct the situation and restart the installation. For more details on prerequisites, see Prerequisites and pre-installation tasks for the Managing Server on UNIX and Linux

  9. Note the following installation points:

    • The InstallShield portion of the installation program will write to one of the following system temporary directories by default:

      Operating system Directory
      Solaris or HP-UX /var/tmp
      Linux and all other UNIX platforms /tmp

      If you do not want the InstallShield portion of the installer to write to this directory, run the executable file directly with the following option: -is:tempdir tmp_dir. For example:

        setup_MS_platform.bin -is:temp_dir /opt/ibm/tmp

      The temp_dir is the directory you want the InstallShield portion of the installation program to write to. The user for the installation must have read, write, and execute privileges to this directory.

    • The installation program writes to the following log directory by default: /var/ibm/tivoli/common/CYN/logs

      If you do not want the installer to write to this directory, run the executable file directly with the following option: -V LOG_DIR=log_dir. For example:

        setup_MS_platform.bin -V log_dir=/opt/ibm/log

      The log_dir is the directory you want the installer to write to. The user for the installation must have read and write privileges to this directory.

    • If you are trying to launch the installation program on HP-UX directly from a CD, and the installation program does not start, perform the following steps:

      • Clean up the temporary directory for the InstallShield portion of the installation program. For example, for HP-UX the default temporary directory for the InstallShield portion of the installation program is /var/tmp, so run the following commands:

          rm -fr /var/tmp/ismp* rm -fr /var/tmp/istemp*

      • Specify the Java home when running the executable file to launch the installation program. For example, if the CD-ROM drive is /mnt/cdrom, run the following command:

          setup_MS_platform.bin -is:javahome /mnt/cdrom/java/jre

    • If you are installing the Managing Server on HP-UX 11.11 from a Windows computer using a Windows terminal emulation program, run the executable file from the directory that contains your installation image in this way:

        setup_MS_platform.bin -is:javahome Java_home

      Java_home specifies the home directory for the Java Virtual Machine. For example, if you can find the Java file in /opt/java1.3/bin/java, Java_home is /opt/java1.3

  10. Select I accept both the IBM and the non-IBM terms and click Next.

    The CD Install Selection panel is displayed.

  11. Choose one of the following options:

    • If you are installing from an image located on your hard disk, select No and click Next.

    • If you are installing directly from a CD, select Yes so that the Managing Server installation image can be copied to a temporary directory on your hard disk clearing the CD-ROM drive for the rest of the required installation disks. The Managing Server installation image requires at least 1 GB of space. In addition, either accept the default temporary directory or browse to a different directory. Click Next.

    The Analyze System for Prerequisites panel is displayed.

    The system checks if you are running the installation as the root user. If not, you cannot perform the installation

  12. Wait for the installation program to finish its analysis and then click Next.

    The Choose Installation Type panel is displayed.

  13. Select Custom and click Next.

    The Choose Features panel is displayed.

  14. Select the features and click Next.

    The following descriptions explain which features select:

    • Managing Server: this option is selected by default, the Managing Server is installed in all circumstances.
    • Visualization Engine: select this if you are installing the Managing Server on this server. Do not select if you are running the installer program for creating database tables for an existing database environment on this server and the Managing Server is being installed on a separate server. If this is selected, Managing Server will automatically be enabled. You cannot install the Visualization Engine without installing necessary Managing Server files.
    • Database Tables: select this if you are installing IBM DB2 or creating database tables for an existing database environment on this server. Do not select this if you are using an existing remote database. If this is selected, Managing Server will automatically be selected. You cannot create database tables without installing necessary Managing Server files. If you are not running the installation as the root user, the "Database Tables" option is disabled and you cannot select it.

    Clear Database Tables if you are upgrading the Managing Server. If you have Database Tables selected, the data in the existing database tables will be deleted.

    Click Next. The Choose Destination panel is displayed.

  15. Click Next to accept the default installation directory path in the Directory Name field, or you can change this path by entering a different directory.

    1. You cannot install the Managing Server in a directory path that contains non-English characters, for example:

      • Traditional Chinese
      • Simplified Chinese
      • Japanese
      • Korean
      • Spanish special characters
      • German special characters
      • Portuguese Brazilian special characters
      • French special characters
      • Italian special characters
      • Cyrillic characters

    2. The directory that you specify must be empty.

    3. If you specify a directory that does not exist, the installation program creates the directory.

    Click Next. The Enter TEPS Information panel is displayed.

  16. Complete the following steps to configure the TEPS information:

    1. To install database tables on the TEPS DB2 database, select Install Database Tables on TEPS DB2 Database.

    2. To install the Visualization Engine on the TEPS embedded WAS, select Install Visualization Engine on TEPS eWAS

    3. The Input ITM HOME field is displayed, enter the path for ITM_home

    Click Next. The Enter Database Information panel is displayed.

  17. Perform the following steps to install IBM DB2:

    1. Select Install DB2.

      If the installer detects an existing IBM DB2 environment on this server, you will not have the option to install IBM DB2. To perform an embedded installation of IBM DB2 instead of use an existing database, you need to uninstall it from this server or choose another server to install the Managing Server on. You will then need to exit the installation.

    2. Browse to select the db2setup file, which is commonly in the same directory as the db2 subdirectory.

      The installer will install IBM DB2 in one of the following directories:

      Linux and UNIX (non-AIX) /opt/ibm/db2/V9.5
      AIX, HP-UX or Solaris /opt/IBM/db2/V9.5

    3. To customize IBM DB2 options instead of accept the defaults, select Show Advanced Options and perform one or more of the following procedures:

      1. On UNIX and Linux, you have the option of using a preexisting user. The installation creates the user account with the name you specify unless it already exists.

      2. If this server is part of a Network Information Service (NIS) environment, you will not be able to create new DB2 user accounts from the installer. Create these accounts before starting the Managing Server installation. See Network Information Service environment: creating the DB2 account users.


      Specifying advanced options when installing IBM DB2

      IBM DB2 option to customize Procedure
      DB2 Administration Server User To specify a DB2 Administration Server user:

      1. Click the Edit DAS button. A window for specifying the DB2 Administration Server user opens.

      2. Select Yes to create a new user, or select No if you want to use an existing user.

      3. Specify the DB2 Administration Server user name.

      4. Specify the password for the DB2 Administration Server user.

      5. If you are creating a new user, specify the group name for the DB2 Administration Server user.

        The group must already exist on the system. It will not be created during the installation.

      6. If you are creating a new user, specify the home directory for the DB2 Administration Server user.

      7. Click OK.

      This account has full IBM DB2 privileges. The user ID for the DB2 administration server user is used to run the DB2 administration server on your system.

      DB2 Instance User To specify a DB2 Instance user:

      1. Click the Edit DBI button. A window for specifying the DB2 Instance user opens.

      2. Select Yes to create a new user, or select No if you want to use an existing user.

      3. Specify the name of the IBM DB2 instance.

      4. Specify the name of the DB2 Instance user.

      5. Specify the password for the DB2 Instance user.

      6. If you are creating a new user, specify the group name for the DB2 Instance user.

        The group must already exist on the system. It will not be created during the installation.

      7. If you are creating a new user, specify the home directory for the DB2 Instance user.

      8. Click OK.

      The instance owner home directory is where the IBM DB2 instance will be created.

      DB2 Fence User To specify a DB2 Fence user:

      1. Click the Edit DBF button. A window for specifying the DB2 Fence user opens.

      2. Select Yes to create a new user, or select No if you want to use an existing user.

      3. Specify the DB2 Fence user name.

      4. Specify the password for the DB2 Fence user.

      5. If you are creating a new user, specify the group name for the DB2 Fence user.

        The group must already exist on the system. It will not be created during the installation.

      6. If you are creating a new user, specify the home directory for the DB2 Fence user.

      7. Click OK.

      This account has privileges to administer IBM DB2. The DB2 Fence user is used to run user-defined functions (UDFs) and stored procedures outside of the address space used by the IBM DB2 environment.

      DB2 Port Number To specify the IBM DB2 port number, enter the port number in the text box.
      DB2 Installation Location To specify the directory where IBM DB2 will be installed, enter the path in the text box. The following are the default locations:

      • Linux and UNIX (non-AIX): /opt/IBM/db2/V8.1
      • IBM AIX: /usr/opt/db2_08_01

      These are the guidelines for entering the information:

      • When entering a user ID:

        • User IDs are limited to 30 characters.

        • User IDs are not case-sensitive.

        • You cannot use USERS, ADMINS, GUESTS, PUBLIC, LOCAL.

        • You cannot begin the user name with SQL, SYS, or IBM.

        • You can use a combination of upper- and lowercase characters. However, sometimes they are converted to uppercase in IBM DB2.

        • You can use the numbers 0 through 9.

        • You can use the following special characters: @, #, or $.

        Examples (These are the defaults):

        • DB2 Administration Server: dasusr1

        • DB2 Fenced: db2fenc1

        • DB2 Instance: db2inst1

      • When entering a password:

        • The general guidelines are the same as for the user name.

        • You can use one to eight characters, without spaces.

        • Do not begin the password with a number or an ampersand (&).

        • Passwords are case sensitive.

      • When entering a group name:

        This string can have one to eight characters, without spaces, and can be a combination of upper- and lowercase characters.

        Examples:

        • DB2 Administration Server: dasadm1

        • DB2 Fenced: db2fadm1

        • DB2 Instance: db2iadm1

      • When entering a home directory:

        This string can have one to 64 characters, without spaces.

      A DB2 connection problem can occur due to the difference between 32 bit and 64 bit applications (Web Application Server or Managing Server) and between 32 bit and 64 bit DB2 instances.

      If the installer is using 32 bit JVM, in some cases it cannot connect to DB2 to verify the connection.

      • If the JVM for the Web Application Server and Managing Server is 32 bit, the local DB2 instance must also be 32 bit.

      • If the JVM for the Web Application Server and Managing Server is 64 bit, the local DB2 instance must also be 64 bit.

      Refer to the following case headings to identify the scenarios relevant to you work environment.


      Scenarios

      Header Header
      Case 1: The Managing Server database is created on a 32 bit DB2 instance and JVM for the Managing Server and WAS is created on a 32 bit instance The Managing Server installer can check the DB2 connection during installation. To do this set the DB2 environment variables before launching the installer. When the installation is complete set the DB2 environment variables again before launching the Managing Server installer and the WAS. Use the following command lines to set the DB2 environment variables:

      For Bourne or Korn shell use this command:

        INSTHOME/sqllib/db2profile

      For C shell use this command:

        source INSTHOME/sqllib/db2cshrc

      INSTHOME is the path of db2 instance home.

      Case 2: The Managing Server database is created on a 64 bit DB2 instance and JVM for Managing Server and WAS is created on a 64 bit instance

      The Managing Server installer cannot check the DB connection during installation.

      If you are using a Solaris platform you will need to make the following changes to allow the managing server run in 64 bit mode.

      1. Edit setenv.sh in MS_home/bin.

      2. Change JAVA_CMD=java to JAVA_CMD="java -d64" .

      Then you will need to set the DB2 environment variables before you launch the Managing Server and WAS.

      Use the following command lines to set the DB2 environment variables:

      For Bourne or Korn shell use this command:

        INSTHOME/sqllib/db2profile

      For C shell use this command:

      source INSTHOME/sqllib/db2cshrc

      Case 3: Managing Server database is created on a 32 bit DB2 instance and JVM for the Managing Server and WAS is created on a 64 bit instance. The Managing Server installer cannot check the DB connection during installation. Complete the following steps to resolve this issue:

      1. Create a 64 bit DB2 instance on the systems where the Managing Server and the WAS are installed.

      2. Catalog the Managing Server database on the 64 bit DB2 instance. (Refer to the DB2 manual for more information).

      3. Configure the Managing Server and the WAS to connect to the cataloged database on the 64 bit instance.
      4. On a Solaris platform complete the following steps so the Managing Server can run in 64 bit mode:

        1. Edit setenv.sh in MS_home/bin

        2. Change JAVA_CMD=java to JAVA_CMD="java -d64".

      5. Then to launch the Managing Server and the WAS, set the DB2 environment variables for the 64 bit instance.

      6. Use the following command lines to set DB2 environment variables:

        1. For Bourne or Korn shell use this command:

            INST64HOME/sqllib/db2profile

        2. For C shell use this command:

            source INST64HOME/sqllib/db2cshrc

        INST64HOME is the path of 64 bit db2 instance home.

      Example (case 3): The Managing Server database name is: MSDB (which is created on the 32 bit DB2 instance "db2int32").

      The Managing Server Host is: MSHOST

      1. Create a 64 bit DB2 instance "db2int64" on MSHOST.

      2. Catalog the Managing Server database on the 64 bit DB2 instance, the alias name is MSDB_on_int64.

      3. Modify the Managing Server database connection settings:

        1. Edit setenv.sh in MS_home/bin

        2. JAVA_CMD=java --> JAVA_CMD="java -d64"

        3. JDBC_DRIVER_URL=jdbc:db2:MSDB --> JDBC_DRIVER_URL=jdbc:db2:MSDB_on_int64

        4. JDBC_USER and JDBC_PASSWORD

      4. Modify the WebSphere data source setting:

        1. Open the WebSphere Administration Console, navigate to Resources -> JDBC -> Data sources -> ITCAMDataSource.

        2. Change the database name to MSDB_on_int64.

        3. Modify user name and password of JAAS - J2C Authentication data.

      Case 4: Managing Server database is created on a 64 bit DB2 instance and JVM of Managing Server and WAS is created on a 32 bit instance.

      The managing sever installer cannot check the DB connection during installation.

      1. Create a 32 bit DB2 instance on the system where the Managing Server and the WAS are installed.

      2. Catalog the Managing Server database on the 32 bit DB2 instance.

      3. Configure the Managing Server and the WAS to connect the cataloged database on the 32 bit instance.

      4. Before launching the Managing Server and the WAS, set the DB2 environment variables of the 32 bit instance.

      Use the following command lines to set the DB2 environment variables:

      For Bourne or Korn shell use this command:

        INST64HOME/sqllib/db2profile

      For C shell use this command:

        source INST64HOME/sqllib/db2cshrc

      INST32HOME is the path of 32 bit DB2 instance home.

  18. If you are using an existing DB2 database:

    1. Select Use an Existing Database to start the configuration of the existing database.

    2. In the Database Selection fields, select the Existing IBM DB2.

    3. Local IBM DB2 only: In the Database Instance User ID field, enter the name of the user of the IBM DB2 instance

      the Database Instance Password field enter the password for the database instance user.

      The database instance user id and password were determined when the IBM DB2 environment was configured prior to starting the Managing Server installation. If you do not know them, consult your database administrator.

      If your passwords have expired or you need to change them, you need to modify your password in MS_home/bin/setenv.sh and in the IBM WebSphere data source.

    4. In the Database Schema User ID field, enter the name of the user of the DB2 schema, for example, amuser. This user will own and can create the database tables for ITCAM for Application Diagnostics.

      In the Database Schema Password field type the password for the schema user.

      The database schema user id and password were determined when the IBM DB2 environment was configured before starting the Managing Server installation. If you do not know them, consult your database administrator.

      If your passwords have expired or you need to change them, you need to modify your password in MS_home/bin/setenv.sh and in the IBM WebSphere data source.

    5. From the JDBC type field, select one of the following:

      • Type 2 - JDBC type 2

      • Type 4 - JDBC type 4

    6. Verify the full path to the required Java DataBase Connectivity (JDBC) files or browse to and select the db2cc.jar file. For example, these files might be located in the following path: /usr/db2inst1/sqllib/java/db2cc.jar.

      If IBM DB2 is installed on a remote computer, one technique you can use is to copy the subdirectory containing the JDBC files to the local server, then browse to and select that directory.

    7. To specify advanced options, such as the location of a remote database, select Show Advanced Options and complete one or more of the following fields:


      Advanced options for an existing IBM DB2

      Field Description
      Database Host Type the fully qualified host name or IP address of the computer on which the existing IBM DB2 environment is installed. This advanced option is available only if you have selected JDBC type 4.
      Port Number Type the port number used by the IBM DB2 instance.

      You can discover the correct port number to enter by performing the steps in Determine the port number for an IBM DB2 instance that exists, or you can consult your database administrator for the correct port to enter. This advanced option is available only if you have selected JDBC type 4.

      Database Name Specify the database name. You can use any database name or the default name (octigate).

    8. Click Next.

    The installation program will override the current values for the following parameters in the IBM DB2 server and change them:

      update dbm cfg using authentication server;
      update dbm cfg using intra_parallel yes;
      update dbm cfg using query_heap_sz 2000;
      update dbm cfg using SHEAPTHRES 120000;
      update dbm cfg using FCM_NUM_RQB 768;
      update dbm cfg using MAXAGENTS 300;

    The DB2 administrator must take note of this and make adjustments in order to ensure proper data collector configuration. Refer to the MS_home/etc/dbsettings.sql file for details.

  19. To configure an existing Oracle environment:

    1. Select Use an Existing Database to start the configuration of the existing database.

    2. In the Database Selection field, select Existing Oracle.

    3. Enter the Oracle system identifier number (SID) in the SID field.

      The SID is used to identify the Oracle environment. To find this value, see the value for the ORACLE_SID environment variable for the operating system.

    4. Local Oracle only: In the DBA User ID field, enter the name of the Oracle database administrator

      In the DBA Password field, enter the password for the Oracle database administrator.

      The database administrator and password were determined when the Oracle environment was configured prior to starting the Managing Server installation. If you do not know them, consult your database administrator. If your passwords have expired or you need to change them, you need to modify your password in MS_home/bin/setenv.sh and in the IBM WebSphere data source.

      The DBA User ID and DBA Password fields are only visible if you selected Database Tables in the Choose Features panel.

    5. In the Database Schema User ID field, enter the name of the user of the Oracle schema, for example, amuser). This user will own and can create the database tables for ITCAM for Application Diagnostics.

      In the Database Schema Password field, enter the password for the user. Reenter the Oracle database schema password in the Verify Password field to make sure that you entered it correctly.

      The database schema user id and password were determined when the Oracle environment was configured prior to starting the Managing Server installation. If you do not know them, consult your database administrator. If your passwords have expired or you need to change the passwords, you need to modify your password in MS_home/bin/setenv.sh and in the IBM WebSphere data source.

    6. Local Oracle only: verify the full path to the Oracle home directory.

      See the Oracle profile for details.

    7. Local Oracle only: type the name of an existing Oracle SQLPlus user in the Oracle SQLPlus User field. For example, oracle.

      This was determined when the Oracle environment was configured prior to starting the Managing Server installation. If you do not know this value, consult your database administrator.

      The Oracle SQLPlus User and Oracle SQLPlus User Password fields are only visible if you selected Database Tables in the Choose Features panel.

    8. Select the JDBC type to use. From the list you can choose the following JDBC types:

      • Type 2 - JDBC type 2
      • Type 4 - JDBC type 4

      If you are using an Oracle type 2 JDBC driver, run the following commands to set the Oracle environment variables before launching the Managing Server installer and again before launching the Managing Server and the WAS. Set the Oracle environment variables:

        ORACLE_HOME=<ORACLE HOME>
        export ORACLE_HOME
        LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib
        export LD_LIBRARY_PATH

    9. Verify the full path to the required JDBC files or browse to and select the classes12.jar file.

      This is a directory which contains JDBC libraries. This is an example:

        opt/oracle/product/10g/jdbc/lib/ojdbc14.jar

      If Oracle is installed on a remote computer, one technique you can use is to copy the subdirectory containing the JDBC files to the local server, then browse to and select that directory.

    10. To specify advanced options (such as specifying the location of a remote database), select Show Advanced Options and complete one or more of the following fields:


      Advanced options for an Oracle database

      Field Description
      Database Host Type the fully qualified host name or IP address of the computer on which the existing Oracle environment is installed. Do not include a protocol in the host name. For example, use

        myserver.ibm.tivoli.com

      ...not...

        https://myserver.ibm.tivoli.com

      Port Number Provide a port number in the Port Number field. Do not accept the default port assignment (1521) if you have assigned other applications to use that port number.

      Consult your database administrator for the right port to enter.

      Database Name Specify the database name. You can use any database name or the default name (octigate).

    11. Click Next.

  20. After performing the steps to set up your database environment, the Enter WAS Information panel is displayed. Perform the following procedure to install IBM WAS:

    1. Select Install IBM WAS.

    2. Enter the following information to specify your IBM WAS configuration:


      Options for installing IBM WAS

      Field What to do
      User Name Type the name of the user that will run WAS.

      Default the root user. If you do not use the root user, this user will be created with root privileges.

      Password Type a user password.
      WAS 7.0 Installation Image Location Browse to and select the WAS/install file under the /path/to/install.
      Specify WAS installation directory: To change the default, select Show Advanced Options and enter or browse to a different directory.

      You cannot install WAS in a directory path that includes the following types of characters:

      • Traditional Chinese
      • Simplified Chinese
      • Japanese
      • Korean
      • Spanish special characters
      • German special characters
      • Portuguese Brazilian special characters
      • French special characters
      • Italian special characters

      User Interface User To change the default, select Show Advanced Options and enter the name that you want for the user for logging into and using the Application Monitor as the default user.

      Default the root user. If it is different from the root user, make sure that user has root privileges.

    3. Click Next.

  21. To configure an existing IBM WAS:

    1. Ensure that IBM WAS is installed on the Managing Server computer.

    2. Select Use an existing IBM WAS.

      The software searches for an installation of IBM WAS. It then displays a list of discovered IBM WAS instances.

    3. Complete the following steps:

      • Select the WAS instance on which to install the Managing Server.

      • If the WAS instance on which to install the Managing Server was not detected, you can specify another instance of WAS by completing the following steps:

        1. Select the Manually specify an application server node.

        2. Browse to and select the AppServer_home directory.

        3. Select the instance in the refreshed list of discovered IBM WAS instances.

      You cannot choose a IBM WAS instance in a directory path (including profile, cell, node, and server names) that includes the following types of characters:

      • Traditional Chinese
      • Simplified Chinese
      • Japanese
      • Korean
      • Spanish special characters
      • German special characters
      • Portuguese Brazilian special characters
      • French special characters
      • Italian special characters

    4. Click Next.

      If you selected Install Visualization Engine on TEPS eWAS in the Enter TEPS Information panel, the Existing WAS Information panel is displayed.

      The following table describes the fields in this panel:

      Field What to do
      Host Name Type the fully qualified host name or IP address of the WAS where the Managing Server will run.

      If using Network Deployment, provide the host name of the deployment manager instead.

      SOAP Connector Port Enter the SOAP port setting (Default 8880). This connector port is used by the WAS to send commands using the SOAP.

      The SOAP port is identified in the AppServer_home/profiles/profile_name/config/cells/cell_name/nodes/node_name/serverindex.xml file of the instance of WAS that the Managing Server will use.

      If using Network Deployment, provide the SOAP port of the deployment manager instead.

      User Name If Global Security is enabled on the WAS, type the user name of WAS Administrator. This is the user that logs in to the WebSphere Administration console. If Global Security is not enabled on the WAS, type the user name of your local Operating System. The Managing Server will use this user to enable Global Security on the WAS. For this to happen the WAS must be launched by the root user.WAS.

      This user must have the same types of permissions as described in the following section:Permissions for an existing WAS.

    5. If you selected Install Visualization Engine on TEPS eWAS in the Enter TEPS Information panel, theExisting WAS Information panel is displayed.

      The following table describes the fields in this panel:


      Table 10. IBM WAS configuration for an existing installation where the VE is not installed on the TEPS eWAS

      Field What to do
      Host Name Type the fully qualified host name or IP address of the WAS where the Managing Server will run.

      If using Network Deployment, provide the host name of the deployment manager instead.

      SOAP Connector Port Enter the SOAP port setting (Default 8880). This connector port is used by the WAS to send commands using the SOAP.

      The SOAP port is identified in the AppServer_home/profiles/profile_name/config/cells/cell_name/nodes/node_name/serverindex.xml file of the instance of WAS that the Managing Server will use.

      If using Network Deployment, provide the SOAP port of the deployment manager instead.

      User Name If Global Security is enabled on the WAS, type the user name of WAS Administrator. This is the user that logs in to the WebSphere Administration console. If Global Security is not enabled on the WAS, type the user name of your local Operating System. The Managing Server will use this user to enable Global Security on the WAS. For this to happen the WAS must be launched by the root user.WAS.

      This user must have the same types of permissions as described in the following section:Permissions for an existing WAS.

      Password Type a user password.
      User Interface User To change the default, select Show Advanced Options and enter the name that you want for the user for logging into and using the ITCAM for Application Diagnostics Managing Server.

      Default the root user. If it is different from the root user, make sure that user has root privileges.

      If you are using a non root user to install the Managing Server, the "User Interface User" field will be disabled, and the "User Interface User" will be the same as the user name of WAS Administrator. You can change the name after installation.

    If you are using a non root user to install the Managing Server, enable WebSphere Global security or you will receive a message similar to the following:

    'CYNCR9703E The global security of the WAS profile selected is disabled. For a non root user the WAS profile must enable global security.'

  22. Click Next. The Select WAS panel is displayed. Navigate to select the server, and click Next.

  23. After performing the steps to set up your WAS, the Enter Managing Server Information panel is displayed.

    Complete the following steps:

    1. Enter the fully qualified host name or IP address of the server where you want to install the Managing Server.

      If memory resources on one Managing Server are insufficient to support your environment, for example, if you want to have it connect to a large number of data collectors (such as 500 or more), create a second Managing Server that is different from the first Managing Server. See Split Managing Server installation in Unix for instructions on how to install the Managing Server on two separate servers.

    2. To change the default port numbers used by the Managing Server components, select Show Advanced Options and edit the values. Accept each provided value unless the port number has been used already.

    3. Click Next.

      The Generate Response File panel is displayed.

    4. To install the Managing Server on this computer, select Install the Managing Server on this computer.

      You might not want to install the Managing Server on this computer if you are performing the installation procedure for the sole purpose of creating a response file for a subsequent silent installation.

      If you want to create a response file for a subsequent silent installation, select Save the settings in a response file and enter the file path ending with a file name. For example:

        temp/response.opt

      A response file is only generated if the GUI installation completes successfully.

    5. Click Next.

      The Review Installation Information panel is displayed.

    6. Read the summary information and click Install to accept it and begin the installation. The Install and Configure Files panel is displayed. The progress bar might display as stuck at a certain position for a long time during the installation. This is expected, especially for embedded IBM DB2 and WAS installations. Allow the installation to continue. Depending on the performance of your server and operating system, installation might take longer than an hour.

    7. When the installation finishes, the Review Installation Summary is displayed

      If the summary panel displays one of the following messages, install database tables manually:

      • There are problems in the communication between the Managing Server and the database.

      • Installation of the database tables failed or is incomplete.

      In this case, see Manually creating database tables.

    8. Read the information in the panel and click Next.

      The Finish panel is displayed.

    9. To perform post-installation tasks at this time (recommended), select Launch the Managing Server and Launch the User Interface.

    10. Click Finish.


Parent topic:

Custom installation for the Managing Server on UNIX and Linux

+

Search Tips   |   Advanced Search