Linux operating systems

Installing the API on Linux on Power Systems (Big Endian)

You can install the IBM Storage Protect API from the product installation media.

Before you begin

  • You must be logged in as root user to install the product.
  • If you have IBM Storage Protect 6.2 (or an earlier version) installed, remove it (rpm -e) and any other dependent software programs before you install a newer version.
  • If you have IBM Storage Protect 6.3 (or newer) installed, you can use the rpm upgrade option (rpm -U) or the rpm freshen option (rpm -F) to upgrade the existing software to a newer version. The rpm -U command can be used to install new packages or upgrade existing packages; rpm -F can update only packages that are already installed.
  • Stop any running client processes before you uninstall or upgrade the IBM Storage Protect API or backup-archive client.
  • If you are running a version 7.1.2 or earlier client, you must uninstall any language packages before you proceed with the upgrade.

About this task

The following installation options are available in uncompressed packages on the installation media.

Table 1. Package names, contents, and default directory
Package Name Contents Default directory
gskcrypt64-8.x.x.x.linux.ppc.rpm
gskssl64-8.x.x.x.linux.ppc.rpm
64-bit Global Security Kit (GSKit) packages /usr/local/ibm/gsk8
TIVsm-API64.ppc64.rpm Application programming interface (API), which contains the IBM® Storage Protect API shared libraries and samples. /opt/tivoli/tsm/client/api/bin64

TIVsm-APIcit.ppc64.rpm

Optional. These files provide the Common Inventory Technology components that you can use to obtain information about the number of client and server devices that are connected to the system, and the utilization of processor value units (PVUs) by server devices. For more information about PVUs, see Estimating processor value units in the IBM Storage Protect server documentation.

APIcit is installed in /opt/tivoli/tsm/client/api/bin64/cit

This installation procedure can be used to install new distributions or updates from downloaded installation media. The downloaded files that you use to install the client might be compressed. Depending on the package file format, either copy or extract the files to disk and use these instructions to install the components.

You can download the appropriate package file from one of the following websites:
Before installation, you must first check the GSKit signature of the rpm package as follows:
  1. Download the GSKit public PGP key GSKit.pubn.pgp from the download sites that also contain the client packages, where n represents a number. For now, the value of n is 4.
  2. Import the GSKit public key by issuing the following command:
    rpm --import GSKit.pub4.pgp
  3. Verify the GSKit rpm file by issuing the following command:
    rpm --checksig <GSKit rpm file> --verbose
    where <GSKit rpm file> is the name of a GSKit rpm package that is listed in Table 1 - Package names, contents, and default directory.
You must then check the signature of the client package as follows:
  1. Download the generated gpk key PRD0001289key.pub.asc from the download sites that also contain the client packages.
  2. Import the generated gpk key by issuing the following command:
    rpm --import PRD0001289key.pub.asc
  3. Verify the PGP public key by issuing the following command:
    cat PRD0001289key.pub.asc
    -----BEGIN PGP PUBLIC KEY BLOCK-----
    
    mQINBGa0+zYBEACv8/upsLxBLwv8SkiUBj1EtKV7slhZg2B7ubVBAeh1XNJh06t6
    rkLZsFSBLIDhKjk0GeLfj31tZZxeyydGorUORqocfB6XooNgFk9ZB/xMKjdI8wzZ
    AHJOMqskLIjGmQw1JjWei4nXmKtrb3IktP2MqGRM6L/thoaJbIDtMPto73eNL4hp
    wL8VzFV0Qtgvj/cbTxQn/zmZW6yPLrH0/9xpKNXkJAvHnfxRHEtZ9H0lOCd/XUEk
    KPEPpk8ROCvtpi1ZyqKGN12BWmy/byOllIZFggwFhdZF8QPE+1fWsmpPTlvdH9ip
    HBoRCh2KAe5lnBgpOytQVGv48CqiYY9Yzq9WYM4aV9I1JMGoY/lXWKmRbluMN6Ad
    501usqw9qACnH3K63AIFlomPYzMLt4OnPZiJ+p9Hm5UpeTPpjbQcKyVenAPtH8Er
    dlov8nNOjFGbxucIemdxo6JmZ7lnHL/wjTVsb2s3/EDoyj8NvtfElD4wARf60MK6
    +LqZifv5xZunDSMbGEeKwnH7ob6/xa09SDozt3DFymAisNwEGt1mL8NHInhN+zXM
    HFDvIryMLzqrzYm7GYedS7PnoORrUp0ZuQdy6Y89PwhhpVFVW1+1IwPeP8bjQobJ
    jdsbY2IHr+DFTp6RnilmJ8nrUH+4ORN7jPaTvB6iFgN+jHrudTRhjDWeMQARAQAB
    tC5JQk0gU3BlY3RydW0gUHJvdGVjdCBDbGllbnQgPHBzaXJ0QHVzLmlibS5jb20+
    iQI6BBMBCAAkBQJmtPs2AhsPBQsJCAcCBhUKCQgLAgQWAgMBAh4BBQkAAAAAAAoJ
    EM5xG7blgVejJxcQAKz/xjvlRZ8KBq6vjHiQZDpd35Z9m5Em7AcubicAyHu1mPbB
    y+ES7dhXo6YI9wGZhhYw9f578bkszZE7Yn46xMLzB8k1r1tfgQ7iCKAVqMi/jGl7
    wBa/4P6h6YrIGPOlIft8HjEqAGf6RNCSkHJ7rOaDbEAeBM35rlXENXup/zgEm7c5
    fYVA7WVr3C29GDhqiEuXdphEHElZfWz8vbvW++m0SedjOpUzLL7HZ0TXncUuxedr
    iiFcJzVpMDmTlyaj2YKJRbgHrSNA2KN8VO3aU4IYeJ28tEyvz8P610V4Gqq/aU1U
    fIPnGqf+3+j+/DxIBeLGlFako6QI2cuyY08sqV3iu35/TThgkiLo0wpP0NaoP/Ea
    7qp8Se+Yu6KiuJ+0zeF4J5x8NzxqbKmZArr0ogiwyZJHBgclwjUrZflV/EnzPmW4
    xJrzS3FTCLmsoxKaoiDyFP9GsQxHlz+mDeih4wO1uU8I5rb2eegZP9I4MQaHoAaC
    qhVb0Df5hVV+skr4PYfWOFXHL5v2c5JGVENy1sHYL0oMoz2dxVPJhRVQs0GzyBlx
    WpdItyx415QUqJWDHifqBzb0qOiZq5iGl0ERu0D59S3oDmstnKeCX4msAxuuOvGX
    kg04zJIz6ifkfzcGoSnWq9Pbos5QsNnDNYG7+y0QsbnX4hO8vXBwCWgW4Z3q
    =7qT0
    -----END PGP PUBLIC KEY BLOCK-----
  4. Verify the client package by issuing the following command:
    rpm -K <client_package>.rpm
    where <client_package> is the name of an rpm package that is listed in Table 1 - Package names, contents, and default directory.

Procedure

  1. Mount the volume that you are installing from.
  2. Change to the directory where the installation packages are stored.
  3. Install the 64-bit GSKit packages. In this example, the 8.x.x.x characters represent the GSKit version:
    rpm -U gskcrypt64-8.x.x.x.linux.ppc.rpm gskssl64-8.x.x.x.linux.ppc.rpm
  4. Install the IBM Storage Protect API, and optionally install the Common Inventory Technology package that is needed to support processor value unit (PVU) calculations.
    1. Required: Install the API:
      rpm -i TIVsm-API64.ppc64.rpm
    2. Optional: Install the Common Inventory Technology package that is used by the API. This package is dependent on the API so it must be installed after the API package is installed.
      rpm -i TIVsm-APIcit.ppc64.rpm
    Tip: If you are upgrading the API and the Common Inventory Technology package was previously installed, you must upgrade both the API and Common Inventory Technology packages. For example, you can run the following command:
    rpm -U TIVsm-API64.ppc64.rpm TIVsm-APIcit.ppc64.rpm