The first step for authenticating by using a Tivoli Netcool/OMNIbus ObjectServer is to
create a federated user repository for Netcool Configuration 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
-
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.
- Select .
-
Under the User account repository, select Federated repositories from
the Available realm definitions field, and click Configure.
-
Under Repositories in the realm, select Add repositories (LDAP, custom,
etc).
-
Under General Properties, select
-
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 |
-
Click Apply and save your changes directly to the master
configuration.
-
Under General properties of Repository Reference, update the Unique distinguished name to
o=netcoolObjectServerRepository
-
Click OK and save your changes directly to the master configuration,
then click OK again.
-
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.
-
If prompted, enter the WebSphere Administrator user password in the
Password and Confirm Password fields, and click
OK.
-
In Global security under the User account repository, select Federated
Repositories from the Available realm definitions field, and click Set as
current.
-
Click Apply and save your changes directly to the master
configuration.
-
Log out of the Administrative Console.
- 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)