Application and database server: Installing multiple integration services

You can install multiple integration services simultaneously, by selecting multiple software packages for Jazz™ for Service Management in a single IBM® Installation Manager session.

Before you begin

About this task

Tip: The number of steps and their order can change depending on the number of software packages that you select in the Installation Manager > Install Packages window and subsequently the features that you select in the Installation Manager > Features window.

Procedure

  1. Depending on whether you have a browser on the target server, start either the launchpad or Installation Manager.
  2. Select each check box that is associated with the software package to install, and click Next. If IBM WebSphere® Application Server is not already installed, select IBM WebSphere Application Server and its extension.
    • IBM WebSphere Application Server Version 8.5.0.1
    • IBM WebSphere SDK Java™ Technology Edition (Optional) Version 7.0.2.0
    • Jazz for Service Management extension for IBM WebSphere 8.5.5.4
    • Registry Services Version 1.1.2.1
    • Administration Services Version 1.1.2.1
    • Security Services Version 1.1.2.1
    • Dashboard Application Services Hub Version 3.1.2.1
    • Administration Services UI Version 1.1.2.1
    • Reporting Services Version 3.1.2.1
    The Installation Manager > Licenses panel opens.
  3. Review the license agreement for the following software packages as required, and accept the terms; click Next.
    • Administration Services Version 3.1.2.1
    • Administration Services UI Version 3.1.2.1
    • IBM WebSphere Application Server Version 8.5.5.4
    • Jazz for Service Management extension for IBM WebSphere 8.5.
    • Registry Services Version 3.1.2.1
    • Security Services Version 3.1.2.1
    • Dashboard Application Services Hub Version 3.1.2.1
    • Reporting Services Version 3.1.2.1
    The Installation Manager > Location panel opens.
  4. Specify the installation locations for the following software package groups and accept the specified default installation locations as outlined in Table 1.
    • WebSphere Application Server
    • Core services in Jazz for Service Management
    Tip: For each software package group, select the group name and then specify the installation directory.
    Restriction: If you specify a non-default installation directory, ensure that the path and directory name do not contain non-ASCII, special, or double-byte characters. Use only these characters: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ _\:0123456789()~-./
    Table 1. Installation locations for the software packages
    Software package Platform Location
    Package group: WebSphere Application Server
    WebSphere Application Server (WAS_HOME) Windows C:\Program Files\IBM\WebSphere\AppServer
      Linux, AIX® /opt/IBM/WebSphere/AppServer
    Package group: Core services in Jazz for Service Management

    Jazz for Service Management (JazzSM_HOME)

    Windows C:\Program Files\IBM\JazzSM
    Linux, AIX /opt/IBM/JazzSM

    Dashboard Application Services Hub

    Windows C:\Program Files\IBM\JazzSM
    Note: Dashboard Application Services Hub is installed to C:\Program Files\IBM\JazzSM\ui referred to as DASH_HOME.
    Linux, AIX /opt/IBM/JazzSM
    Note: Dashboard Application Services Hub is installed to /opt/IBM/JazzSM/ui, referred to as DASH_HOME.

    Registry Services in Jazz for Service Management

    Windows C:\Program Files\IBM\JazzSM
    Note: Registry Services is installed to C:\Program Files\IBM\JazzSM\registry, referred to as REGISTRY_HOME.
    Linux, AIX /opt/IBM/JazzSM
    Note: Registry Services is installed to /opt/IBM/JazzSM/registry, referred to as REGISTRY_HOME.

    Administration Services in Jazz for Service Management

    Windows C:\Program Files\IBM\JazzSM
    Note: Administration Services is installed to C:\Program Files\IBM\JazzSM\admin, referred to as ADMIN_HOME.
    Linux, AIX /opt/IBM/JazzSM
    Note: Administration Services is installed to /opt/IBM/JazzSM/admin, referred to as ADMIN_HOME.

    Security Services in Jazz for Service Management

    Windows C:\Program Files\IBM\JazzSM
    Note: Security Services is installed to C:\Program Files\IBM\JazzSM\security, referred to as SECURITY_HOME.
    Linux, AIX /opt/IBM/JazzSM
    Note: Security Services is installed to /opt/IBM/JazzSM/security, referred to as SECURITY_HOME.

    Administration Services in Jazz for Service Management UI

    Windows C:\Program Files\IBM\JazzSM
    Note: Administration Services UI is installed to C:\Program Files\IBM\JazzSM\admin_ui, referred to as ADMINUI_HOME.
    Linux, AIX /opt/IBM/JazzSM
    Note: Administration Services UI is installed to /opt/IBM/JazzSM/admin_ui, referred to as ADMINUI_HOME.
    The Installation Manager > Features – languages panel opens.
  5. Accept the default translated languages that are selected in the Translations Supported by All Packages panel; click Next. The Installation Manager > Features panel opens.
  6. Select the following features to install and click Next.
    Option Description
    IBM WebSphere SDK Java Technology Edition (Optional) Version 7.0.2.0 IBM WebSphere SDK Java Technology Edition (Optional) Version 7.0.2.0
    WebSphere Application Server Version 8.5.0.1

    WebSphere Application Server Full Profile

    • EJBDeploy tool for pre-EJB 3.0 modules
    • Stand-alone thin clients, resource adapters and embeddable containers > Stand-alone thin clients and resource adapters
    • Stand-alone thin clients, resource adapters and embeddable containers > Embeddable EJB container
    • Sample applications

    IBM WebSphere SDK for Java Technology Edition 6

    • IBM 32-bit WebSphere SDK for Java
    • IBM 64-bit WebSphere SDK for Java
    Note: Ensure that you select IBM 64-bit WebSphere SDK for Java, otherwise the installation fails.
    WebSphere Application Server Version 8.5.0.1 ships IBM WebSphere SDK for Java Technology Edition 6. However, custom installation provides an option to install IBM WebSphere SDK for Java Technology Edition 7.
    Jazz for Service Management extension for IBM WebSphere 8.5.0
    • Jazz for Service Management extension for IBM WebSphere > Install WebSphere extension
    Registry Services
    • Schema
      • Installation
      • Configuration
    • Application
      • Installation
      • Configuration
    • Samples
      Note: This feature is optional.
    • Documentation
      Note: This feature is optional.
    Administration Services
    • Installation
    • Configuration
      • Configure on WebSphere Application Server Full Profile
      • Configure on WebSphere Application Server Liberty Profile
      Note: If you installed WebSphere Application Server Full Profile, and you want to configure Administration Services on WebSphere Application Server Liberty Profile, you will encounter an error. These configuration options for WebSphere Application Server are mutually exclusive and you must have the relevant WebSphere Application Server full or Liberty profile application serving environment that is already installed.
    Security Services

    Authentication Service

    • Installation
    • Configuration

    Authentication Service Client

    • Software Development Kit
    • Sample Applications
    Note: This feature is optional.
    Dashboard Application Services Hub
    • Installation
    • Configuration
    Administration Services UI
    • Installation
    • Configuration
    Reporting Services
    • Schema
      • Installation
      • Configuration
    • Application
      • Installation
      • Configuration
    The Installation Manager > Features configuration panel opens for the selected software package.
  7. Either create or use the JazzSMProfile, which is the WebSphere application server profile for Jazz for Service Management on the target application server.
    1. In the Common Configurations > WebSphere Configuration panel, click Browse to select the full path to the WebSphere Application Server installation directory.
    2. From the Profile deployment type drop-down list, select one of the following options:
      • Create WebSphere profile, if you want to create the WebSphere application server profile.

        Select this option, if this integration service is the first one to be installed on the target application server and you want to create the profile.

      • Use existing WebSphere profile, if you want to use the existing JazzSMProfile.

        Select this option, if you already installed another integration service and created the JazzSMProfile during that installation.

    3. If you accept the default settings for the WebSphere application server profile, specify the User name and Password; otherwise specify different values.
      Fields Description
      WebSphere installation location The full path to the WebSphere Application Server profile directory.
      Profile name The default WebSphere Application Server profile name, that is, JazzSMProfile.
      Attention: If you want to install all integration services on a single server, or you are installing Dashboard Application Services Hub on a separate application server, you must specify JazzSMProfile as the profile name.
      Node name The default server node for the WebSphere application server profile, that is, JazzSMNode01.
      Server name The default name of the application server, that is, server1.
      User name The administrator user ID for the application server profile.
      Password The password that is associated with the administrator user ID.
      Password confirmation The confirmed password that is associated with the administrator user ID.
      Note: This field is displayed only when you select Create WebSphere profile from the Profile deployment type list.
    4. Click Validate. After Installation Manager validates the details, it enables the Next button. Click Next.
    5. In the Common Configurations > Ports Configuration panel, accept the default values for the ports. Alternatively, change the value in the HTTP transport port field, and Installation Manager automatically changes the values in the remaining fields that are based on this value.
    Note: A Windows service is not created when the application server profile is created.

If you selected the Registry Services Schema or Application Configuration feature in the Installation Manager > Features panel.

  1. Specify the database connection details to the DB2® instance.
    1. Specify the details for the Registry Services database, which is created in the selected DB2 instance.
      Fields Description
      Select DB2 instance The database instance on the database server, for example, db2inst1 or DB2 when you installed DB2 with the default values and a single database instance.
      Note: On Windows systems only, Installation Manager reads the DB2INSTANCE environment variable.
      Note: On AIX systems, if you select a DB2 instance that is not a default instance or any instance that is not cataloged, you must catalog the selected instance before you perform the Jazz for Service Management installation; otherwise, you might encounter errors. The selected instance must be cataloged with the node name that is the same as the instance name.

      db2 catalog local node <node_name_same_as_instance_name> instance <instance_name>

      Example: db2 catalog local node db2inst2 instance db2inst2

      Registry database The default option to create the Registry Services database, that is, Create database; otherwise, select Use existing database to use an existing Registry Services database.
      Note: If you select Create database, ensure that a database with the same name does not exist in the selected instance. If you try to create a new database with an existing name, Registry Services installation might fail.
      Database name The default name of the Registry Services database, that is, FRSDB; otherwise, select the name of the existing Registry Services database.
      User name The administrator user ID for connecting to the database instance.
      Password The password that is associated with the administrator user ID.
      Database port number The port for connecting to the database instance.
    2. Click Test Connection. After Installation Manager validates the details, it enables the Next button.

If you selected the Registry Services Application Configuration feature in the Installation Manager > Features panel.

  1. Specify the authentication mechanism for Registry Services to use at run time.
    Fields Description
    Authentication The authentication mechanism to select:
    • Basic
    • Certificate
    Important: Select Basic when you install Administration Services, Administration Services UI, and Registry Services in the same WebSphere Application Server profile. Administration Services does not support client certificate authentication.
    Authorization The administrator authorization is provided based on the following options:
    • All authenticated users are administrators
    • Everyone is an administrator
    • Following users or groups are administrators
      • Users–all specified users are administrators, where multiple users are separated by the | pipe symbol
      • Groups–all members of the specified groups are administrators, where multiple groups are separated by the | pipe symbol

If you selected the Administration Services Configuration feature in the Installation Manager > Features panel.

  1. Specify the installation location of Registry Services that Administration Services uses at run time to connect to the Registry Services application; click Next.
    Fields Description
    Location The installation location for Registry Services that is one of the following options:
    1. local–select when the Registry Services application server is installed on the same server as Administration Services.
    2. remote–select when the Registry Services application server is installed on a different server than Administration Services.
    Host name The host name or IP address of the server on which Registry Services is installed. Modify this value if you selected remote from the Location drop-down list.
    HTTPS transport secure port The secure listening port for the Registry Services run time.
    Note: This field is only displayed when you select remote from the Location list.
  2. In the IBM Cognos 10.2.0.4 installation image panel, specify the path to the extracted Cognos image on your local file system.

If you selected the Dashboard Application Services Hub Configuration feature in the Installation Manager > Features panel.

  1. Accept the default value or specify the context root for Dashboard Application Services Hub in the Context Root field in the Dashboard Application Services Hub Configuration > Context Root panel. The default value is /ibm/console.

If you selected the Administration Services UI Configuration feature in the Installation Manager > Features panel.

  1. Specify the installation location of Registry Services that Administration Services UI uses at run time to connect to the Registry Services application; click Next. They are same Registry Services details that you specified for Administration Services.

If you selected the Reporting Services Schema or Application Configuration feature in the Installation Manager > Features panel.

  1. Specify the database connection details to the DB2 instance.
    1. Specify the details for the Cognos® Content Store, which is created in the selected DB2 instance.
      Fields Description
      Select DB2 instance The database instance on the database server, for example, db2inst1 or DB2 when you installed DB2 with the default values and a single database instance.
      Note: On Windows systems only, Installation Manager reads the DB2INSTANCE environment variable.
      Note: On AIX systems, if you select a DB2 instance that is not a default instance or any instance that is not cataloged, you must catalog the selected instance before you perform the Jazz for Service Management installation; otherwise, you might encounter errors. The selected instance must be cataloged with the node name that is the same as the instance name.

      db2 catalog local node <node_name_same_as_instance_name> instance <instance_name>

      Example: db2 catalog local node db2inst2 instance db2inst2

      IBM Cognos Content Store The default option to create the Cognos Content Store, that is, Create database; otherwise, select Use existing database to use an existing Cognos Content Store.
      Note: If you select Create database, ensure that a database with the same name does not exist in the selected instance. If you try to create a database with an existing name, the Cognos Content Store installation might fail.
      Database name The default name of the Cognos Content Store, that is, tcrdb; otherwise, select the name of the existing Cognos Content Store.
      User name The administrator user ID for connecting to the database instance.
      Password The password that is associated with the administrator user ID.
      Database port number The port for connecting to the database instance.
    2. Click Test Connection. After Installation Manager validates the details, it enables the Next button.
  2. Specify the complete path where the extracted Cognos install image is located (upto TCRCognos directory) and click Validate. For example:C:\ExtractedDir\TCRCognos
  3. Review the software packages to be installed and their installation directories; click Install.

    Installation Manager calls the scripts to install the software packages and configure WebSphere Application Server and Jazz for Service Management.

  4. After Installation Manager successfully installs and configures the software packages, it displays the start programs panel. You can verify the Dashboard Application Services Hub installation or complete the installation and verify later. Select the relevant radio button and click Finish.
    • Open Dashboard Application Services Hub login window; click the Log into Dashboard Application Services Hub radio button.
    • Do not open Dashboard Application Services Hub login window; click the None radio button.