+

Search Tips   |   Advanced Search


Configure IBM Tivoli License Compliance Manager on Linux

IBM Tivoli License Compliance Manager (ITLM) monitors license compliance. It recognizes and monitors what product offerings and their versions, releases, and fix packs are installed and used on the system. Before configuring ITLM, WebSphere Portal must be installed and configured, including security. Configure IBM Tivoli License Compliance Manager:

  1. Download the IBM Tivoli License Compliance Manager agent and install it on each system that requires it. See Passport Advantage for instructions on downloading the IBM Tivoli License Compliance Manager agent, prerequisites and licensing process.

  2. To provide credentials to ITLM:

    1. Go to the IBM Tivoli License Manager install directory: /var/itlm/wasagent.

    2. Run...

        ./WASAgentClient.sh

      .

    3. Type servers on the WASAgentClient console to list all the server IDs and locations.

    4. Type credentials id userid password to provide credentials for the servers, where id is the server ID and userid and password is for the WAS administrator.

      Whenever the IBM Tivoli License Compliance Manager agent is stopped, rerun the WASAgentClient task and then reissue the credentials.

  3. Follow the IBM Tivoli License Compliance Manager instructions provided with customer agreement to complete the IBM Tivoli License Compliance Manager licensing configuration for WebSphere Portal and IBM Lotus Web Content Management.

  4. Optional: Ensure that the following inventory signature files exist in the provided directory path:

    The required signature file is available on its product installation CD.


    Table 1. Product signature files

    Product offering / Component name IBM Tivoli License Manager signature file Signature file's directory path
    WebSphere Portal (all editions) ITLMWP0601.sys2 PortalServer_root/installer/wp.config/itlm
    IBM Lotus Web Content Management ITLMWCM0601.sys2

    This signature file is placed in the EAR directory during installation. PortalServer_root/installer/wp.config/itlm

  5. Optional: Verify that the itlm.product file exists in the PortalServer_root/version directory.

  6. Optional: Verify that the WebSphere Portal installation updated the .ITLMRegistry file, in the user_home directory, to contain the WebSphere Portal installation directory path.


Parent topic:

Configure IBM Tivoli License Compliance Manager