Installing Tivoli Service Automation Manager 7.2.4.2 for IBM Service Delivery Manager 7.2.4 on Power

News


Abstract

Tivoli Service Automation Manager 7.2.4.2 has been certified for IBM Service Delivery Manager 7.2.4. This technote describes how to install Tivoli Service Automation Manager 7.2.4.2 for IBM Service Delivery Manager 7.2.4 on Power. A procedure for IBM Service Delivery Manager 7.2.4 on VMware is provided in a separate technote.

Content

Prerequisites:

1. Log on to the TIVSAM_image virtual machine as a root.

2. Add executive permission to the ThinWsadmin.sh file:

    cd /opt/IBM/SMP/wasclient/
    chmod +x ThinWsadmin.sh

3. Run /opt/IBM/SMP/wasclient/ThinWsadmin.sh -username wasadmin -password <wasadmin_password> -lang jython -c "AdminTask.help()"

4. Run the following commands:
    rm /opt/IBM/tivoli/tpm/properties/version/7.2.1.0-TIV-TPM-Multi-IF00003.efix
    rm /opt/IBM/tivoli/tpm/properties/version/history/7.2.1.0-TIV-TPM-Multi-IF00003*

5. Run this command to update the deployment engine host name:
    /usr/ibm/common/acsi/bin/de_chghostname.sh

6. Go to the directory /opt/IBM/AgentManager and edit the following files:
  • ./toolkit/config/amClientConfig.properties
  • ./tempAMProps
  • ./bin/SetupEnv.sh
  • ./install/AMInstall.properties

Replace the hostname icb-tivsam.icbvm.cloud.com with the name assigned to TIVSAM_image machine during the time of activation.

7. Create the following subdirectories:
  • /usr/IBM/WebSphere/AppServer/logs/manageprofiles/ctgDmgr01
  • /usr/IBM/WebSphere/AppServer/logs/manageprofiles/ctgAppSrv01
  • /usr/IBM/WebSphere/AppServer/logs/manageprofiles/casprofile

8. Assign the ownership of the subdirectories to the tioadmin user as follows:
    chown tioadmin:tioadmin /usr/IBM/WebSphere/AppServer/logs/manageprofiles/ctgDmgr01
    chown tioadmin:tioadmin /usr/IBM/WebSphere/AppServer/logs/manageprofiles/ctgAppSrv01
    chown tioadmin:tioadmin /usr/IBM/WebSphere/AppServer/logs/manageprofiles/casprofile
9. Stop TIVSAM software stack and reboot the TIVSAM virtual machine.

10. Start TIVSAM software stack.

11. Migrate the VMC images registered in Tivoli Service Automation Manager 7.2.4.

Note: This step is required if you plan to migrate your VMC images that are registered in Tivoli Service Automation Manager 7.2.4 as described in Tivoli Service Automation Manager 7.2.4.2 Infocenter > chapter "Migration from Tivoli Service Automation Manager 7.2.4 to 7.2.4.2".

To use the VMC NIM images that were created with Tivoli Service Automation Manager 7.2.4 in Tivoli Service Automation Manager 7.2.4.2, unregister all registered VMC images just before the migration. Then, when the Tivoli Service Automation Manager 7.2.4.2 installation is done, these images must be discovered and registered again. See step 3 in the “Post-installation steps” section of this technote.

Tivoli Service Automation Manager 7.2.4.2 installation

To install Tivoli Service Automation Manager 7.2.4.2, read through the Tivoli Service Automation Manager readme file, which is attached to the Tivoli Service Automation Manager installation package.

Go to the section “4. Installation Instructions” of the Tivoli Service Automation Manager 7.2.4.2 readme. Proceed as described there, but be aware that the following comments apply for the IBM Service Delivery Manager environment:
  1. Prepare Tivoli Provisioning Manager 7.2.1.0 interim fix 5 for the installation
    a) Go to FixCentral site and download the files:
      7.2.1.0-TIV-Components-AIXPPC64-IF00005 (both packages: 7.2.1.0-TIV-Components-AIXPPC64-IF00005.tar and 7.2.1.0-TIV-TPM-Multi-IF00005.zip).

    Important: Do not install the Tivoli Provisioning Manager interim fix manually by yourself. It must be installed from the Tivoli Service Automation Manager 7.2.4.2 launchpad!
    b) Unpack both packages.

    7.2.1.0-TIV-Components-AIXPPC64-IF00005.tar extracts to CAS, CDS and DMS folders. Extracted content of 7.2.1.0-TIV-TPM-Multi-IF00005.zip includes tpm_core folder.
    c) Move CAS, CDS and DMS folders to tpm_core folder.

2. Stop Tivoli Provisioning Manager deployment engine
    Be sure that the Tivoli Provisioning Manager deployment engine is stopped before the installation. The command to stop Tivoli Provisioning Manager deployment engine is $TIO_HOME/tools/tio.sh stop -t.

3. Check defer options in launchpad
    When you run Tivoli Service Automation Manager 7.2.4.2 launchpad, you will reach a section for Product Installation. When you install Advanced Workflow Components (RBA 7.3.0.4) in that section, check both Defer options on the Process Solution Installer Package Options tab.
4. In the 1st step ('Specify Installation Parameters') of Post-installation Steps tab in Tivoli Service Automation Manager 7.2.4.2 launchpad, make sure that all the fields are filled with the host names that you defined for your environment. If they are not, correct them manually. Be sure that there are no default hostnames, for example, icb-tivsam.icbvm.cloud.com.

Post-installation steps

1. Reactivate the ESCALATION function:
    The following steps in Maximo must be performed to reactivate the escalation to generate CSR file data:

    a) Click System Configuration > Platform Configuration > Cron Task Setup
    b) Find ESCALATION and open it.
    c) Reactivate the escalation.

2. Migrate the existing projects from Tivoli Service Automation Manager 7.2.4.
    There is no need to perform any steps for the migration of existing projects.

3. Migrate the VMC images registered in Tivoli Service Automation Manager 7.2.4
    This step is required if you want to migrate your VMC images that are registered in Tivoli Service Automation Manager 7.2.4 according to the steps described in the chapter "Migration from Tivoli Service Automation Manager 7.2.4 to 7.2.4.2" of the Tivoli Service Automation Manager 7.2.4.2 Infocenter.

    The procedure for migrating VMC images begins with unregistering VMC images before the migration. See step 11 in the prerequisite section of this technote for details.

    To use the VMC NIM images that were created with Tivoli Service Automation Manager 7.2.4 in Tivoli Service Automation Manager 7.2.4.2, just after the migration, perform the following steps:

    a) Run the discovery on all VMC pools.
    b) If validation errors are detected, fix them and re-run the discovery.
    c) Register the images again.
Troubleshooting
  • When installing RBA 7.3.0.4 components, you may receive this error for checking middleware credentials:
    CTGIN0158E: Cannot connect to "WebSphere Application Server" with userid "wasadmin"

    The reason for this behavior is the incorrect start of the LDAP server.

    The solution is to manually stop the LDAP and then run it again:
    # /opt/IBM/ldap/V6.3/sbin/ibmdiradm -k
    GLPADM034I Stopped Admin server instance: 'idsccmdb'.

    # /opt/IBM/ldap/V6.3/sbin/ibmdiradm -I idsccmdb
    GLPADM056I Admin server starting.
    GLPCOM025I The audit plugin is successfully loaded from libldapaudit.a.
    GLPCOM022I The database plugin is successfully loaded from libback-config.a.
    GLPADM060I The admin server backup and restore server configuration entry is not enabled.
    GLPCOM024I The extended Operation plugin is successfully loaded from libloga.a.
    GLPCOM003I Non-SSL port initialized to 3538.

    # /opt/IBM/ldap/V6.3/sbin/ibmslapd -k
    GLPSRV176I Terminated directory server instance 'idsccmdb' normally.

    # /opt/IBM/ldap/V6.3/sbin/ibmslapd -I idsccmdb
    GLPSRV041I Server starting.
    GLPCTL113I Largest core file size creation limit for the process (in bytes): '1073741312'(Soft limit) and '-1'(Hard limit).
    GLPCTL119I Maximum Data Segment(Kbytes) soft ulimit for the process is -1 and the prescribed minimum is 262144.
    (...)
    GLPSRV180I Pass-through authentication is disabled.
    GLPCOM003I Non-SSL port initialized to 389.

    Then you must start TIVSAM software stack with the command:

    su - tioadmin
    $TIO_HOME/tools/tio.sh start wasadmin <wasadmin_password>

    and remember to stop Tivoli Provisioning Manager deployment engine:

    su - tioadmin
    $TIO_HOME/tools/tio.sh stop -t
  • When installing Tivoli Provisioning Manager web components, you may receive this error for checking middleware credentials:
    CTGIN0158E: Cannot connect to "databaser" with userid "maximo"
    The reason for this is the unsuccessful start of the LDAP server.

    The solution is to perform the following steps:

    a) Stop TIVSAM software stack

    b) Reboot the TIVSAM image

    c) Run the commands:
      su - dasusr1
      db2admin start
      exit
    d) Run the commands:
      su – ctginst1
      db2start
      exit
    e) stop and start LDAP:

    /opt/IBM/ldap/V6.3/sbin/ibmdiradm -k
    /opt/IBM/ldap/V6.3/sbin/ibmdiradm -I idsccmdb
    /opt/IBM/ldap/V6.3/sbin/ibmslapd -k
    /opt/IBM/ldap/V6.3/sbin/ibmslapd -I idsccmdb
    /opt/IBM/ldap/V6.3/bin/ibmdirctl -D cn=root -w password start

    f) Start the rest of TIVSAM sw stack:
      su - tioadmin
      $TIO_HOME/tools/tio.sh start wasadmin <wasadmin_password>
    g) Stop the Tivoli Provisioning Manager deployment engine:
    $TIO_HOME/tools/tio.sh stop -t

    h) Run the launchpad and start the Tivoli Provisioning Manager web components installation again.
  • Due to some potential problems in SimpleSRM User Interface, clear cache in the browser after the installation and before using the Tivoli Service Automation Manager 7.2.4.2 SimpleSRM User Interface.

Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Service Delivery Manager
On Power

Software version:

7.2.4

Operating system(s):

AIX, Linux, Windows

Software edition:

All Editions

Reference #:

1650937

Modified date:

2013-09-25

Translate my page

Machine Translation

Content navigation