Creating and configuring a federated user repository for Netcool Configuration Manager

The first step for authenticating by using a Tivoli® Netcool®/OMNIbus ObjectServer is to create a federated user repository for Netcool Configuration Manager.

Before you begin

Important: Before attempting this procedure, complete the following task: Configuring integration with Network Manager

About this task

A federated user repository is built on Virtual Member Manager (VMM), which provides the ability to map entries from multiple individual user repositories into a single virtual repository. The federated user repository consists of a single named realm, which is a set of independent user repositories. Each user repository may be an entire external user repository.

This task describes how to create and configure a federated user repository for Netcool Configuration Manager.

Procedure

  1. Launch the WebSphere Administrative Console from http://<ncmserver-hostname-ip>:<16316>/ibm/console and login using the Netcool Configuration Manager superuser name and password specified during installation.
    Note: The port number may be different for a non-standard installation.
  2. Select Security > Global security.
  3. Under the User account repository, select Federated repositories from the Available realm definitions field, and click Configure.
  4. Under Repositories in the realm, select Add repositories (LDAP, custom, etc).
  5. Under General Properties, select New Repository > Custom Repository
  6. Update the ObjectServer VMM properties as described here (or per your custom repository):
    Repository identifier
    NetcoolObjectServer
    Repository adapter class name
    com.ibm.tivoli.tip.vmm4ncos.ObjectServerAdapter
    Custom Properties
    Add the following four properties:
    Note: Find the exact details from the repository viewable on the Network Manager Gui Administrative Console.
    Table 1. Custom Properties
    Name (case-sensitive Value
    username ObjectServer administrator user name
    password ObjectServer encrypted administrator user password
    port1 Object Server port number
    host1 Object Server hostname/IP address
  7. Click Apply and save your changes directly to the master configuration.
  8. Under General properties of Repository Reference, update the Unique distinguished name to o=netcoolObjectServerRepository
  9. Click OK and save your changes directly to the master configuration, then click OK again.
  10. The local repository may not contain IDs that are also in Netcool Configuration Manager. To mitigate, perform one of the following steps:
    • Remove the local file repository from the federation of repositories.
    • Remove all the conflicting users from the local file repository.
  11. If prompted, enter the WebSphere Administrator user password in the Password and Confirm Password fields, and click OK.
  12. In Global security under the User account repository, select Federated Repositories from the Available realm definitions field, and click Set as current.
  13. Click Apply and save your changes directly to the master configuration.
  14. Log out of the Administrative Console.
  15. Stop the Netcool Configuration Manager server using the ./itncm.sh stop command. Then start the Netcool Configuration Manager server using the ./itncm.sh start command.

What to do next

Netcool Configuration Manager will now authenticate with the ObjectServer VMM.

The Netcool Configuration Manager Superuser has been reverted to the user created during the Dash profile Installation (which is smadmin by default)