The ‘Default’ installation option for TBSM v42 installs a simple, default File Based Repository for user authentication. We say this is sufficient for demonstrations, POCs, etc. but not for production use.
There are no issues with taking a default installation and relying on only the File Based Repository with TBSM, it will work just fine. Scenarios involving typical event management activities within a Netcool/WebTop AEL will not work just using only the File Based Repository. You must use the OMNIBus Repository to establish an OMNIbus authenticated user with the appropriate group membership (or role assignment) to be able to use any of the AEL event management tools such as Acknowledge, Prioritize, Add to Journal, etc.
Adding the Netcool/OMNIbus Repository to the Federated Repositories for TBSM v42 can be accomplished by following this procedure. There is a similar procedure for stand alone Netcool/WebTop v2.2 and I assume ITNM v3.8 installations (not via TBSM v42).
Configuring the servers for an OMNIbus user repository
Further to this procedure, test out creating a user in TIP and verifying that it’s created in the OMNIbus repository. You can use the OMNIbus Administration client to validate this has occurred. Validate that you see both the File Based and OMNIBus Repository under “Secure Administration, Applications and Infrastructure –> Federated Repositories”.
To enable a user to have access to the traditional AEL tools for event management activities, the user needs to be a member of the ‘Normal’ group or have the appropriate OMNIbus roles assigned. At a minimum, a typical TBSM user would be a member of ‘TBSM USERS’, ‘Normal’ and ‘Public’ groups. The ‘TBSM USERS’ group is the group you’ve created with the appropriate roles assigned based on how you will be using TBSM.
Comments on this entry are closed.