To configure a target of type Micro Focus Network Node Manager i (NNMi), you need to do these steps:
- Configure a Web Services Client User in Micro Focus NNMi
- Identify your Micro Focus NNMi port
- Configure the corresponding NNMi target in the ClipConfig.xml on the Clip server
Please assure that the system you intend to integrate meets the version requirements outlined in the table below.
|Network Node Manager i (NNMi)|
10.1x, 10.2x, 10.3x, 10.4x on all available platforms
Until NOM suite 2020.10 – classic release, and above
Until NOM suite 2020.10 – container release, and above
Web Services Client User
Configuring a Web Services Client User in Micro Focus NNMi allows Clip to subscribe to NNMi to receive filtered incidents and also to update NNMi incidents. To create a Web Services Client User
- Launch theMicro Focus NNMi Web Console and log in as an Administrator
- Under the Configuration Workspace, select "Security" and then "User Accounts"
- On the User Accounts tab, click "New"
- On the User Account page, specify the Name and Password for the Web Services Client User (leave the option "Directory Service Account" unchecked). By default, the user name and password configured within the Clip example targets in ClipConfig.xml are "clip" / "clip".
If you want to use a different name or password, you must update the attributes for the username and password in ClipConfig.xml for your NNMi target.
- Click "Save and Close". The new user account is now listed in the "User Accounts" page.
- Under the Configuration Workspace, select "Security" and then "User Account Mappings"
- Click "New", and then associate the Web Services Client account "clip" with the NNMi Web Service Clients group ("client").
- Click "Save and Close". The new user account mapping is now listed in the "User Account Mappings" page.
Micro Focus NNMi port
You can determine whether the default port setting of 80 is correct for your Micro Focus NNMi installation by checking the port information in the NNMi port configuration file (entry for "nmsas.server.port.web.http"), located in the following file:
Clip Target Configuration
To configure a target of Target Type NNMi, you need to adjust the basic settings to point to your NNMi server.
The update settings ( under <updateNNMi/> ) define how Clip should modify an NNMi event in case the corresponding Incident of the destination target changes. These settings do not need to be changed for the example targets of the default installation.
On the Clip Server, edit the configuration file conf/ClipConfig.xml:
The following basic attributes have to be set in the NNMi target definition:
- "name" attribute of the target tag ("MF_NNMi" in the example configuration).
- The "updateOnSubmit" attribute specifies whether Clip should perform the event modifications defined under the <updateNNMi/> tag when a new incident has been created (updateOnSubmit="true"). This is e.g. useful to show the incident ID in the notes attribute of the NNMi event right after the incident has been created. Please note that this attribute needs to be set to "true" additionally on the <attribute> level for an update on an attribute to happen on event submission.
- The "updateCalcDelta" attribute specifies whether Clip, once it receives an event modification for a forwarded event, should determine and forward just those event attributes that were modified. For a target of NNMi, leave this setting to "true", as NNMi always submits all event attributes, whether they were modified or not.
- Attribute "user": please enter the NNMi Web Services Client username configured in NNMi as described in the previous section. In the example configuration above, the username is "clip".
- Attribute "passwd": please enter the Web Services Client user's password. In the example configuration above, the password is "clip".
- The password can be entered in clear text or as an encrypted value. To encrypt the password, use the password encryption in the "Configuration" tab of the Clip Web interface:
Attribute "NNMiURL": This URL needs to be changed to point to your NNMi server. The URL contains the NNMi port number determined in 5.2.2 . As an example, if Clip is installed on the NNMi server and NNMi listens to port 8004, the correct setting would be 'NNMiURL="http://localhost:8004"'.
- Attribute "ClipURL": This URL needs to be changed to point to your server running Clip. This URL is used by NNMi to submit events and event changes to Clip. The URL contains the Clip port number (default: 9090). As an example, if Clip is installed on the NNMi server, the correct setting would be 'ClipURL="http://localhost:9090"'.
- Element "drilldownURL": the drilldown URL specifies how an NNMi event can be opened in a web browser. It is used in the Clip Web GUI in the "Incident List" tab to provide a quick link to the NNMi event:
- Element "incidentDescription": the incident description element defines the description text for an NNMi event. It is displayed in the Clip Web interface in the "Description" column:
- Element "nnmiFilter": at the time Clip subscribes to NNMi to receive events, it passes this filter to NNMi to limit the events it receives to those events matching certain criterias. With the example filter provided in ClipConfig.xml for target "MF_NNMi", Clip receives NNMi events where
- The nature of the event is ROOTCAUSE
- And, the Event Type is one of AddressNotResponding, COnnectionDown, InterfaceDown, NonSNMPNodeUnresponsive or NodeDown
To modify the filter, please refer to
The update settings define how Clip should modify an NNMi event in case the synchronized peer incident changes. These settings are defined under the <updateNNMi> tag for an NNMi target. They can include Variables ( [variablename] ), that refer to attributes of the BMC Remedy or ServiceNow incident.
These settings do not need to be changed if the example targets of the default installation are used to provide an out-of-the-box integration.
To set the NNMi event's notes, configure the attribute "notes" in the Clip Configuration file. The example configuration for target "MF_NNMi" sets the notes to the BMC Remedy Ticket Number, Status and Assignment and allows to open the BMC Remedy incident via a link:
Result example for the NNMi Incident list view:
Result example for the NNMi Incident Summary view:
Result example for the NNMi Incident Details view:
To set the NNMi event's priority, configure the attribute "priority" in the Clip Configuration file. The example configuration for target "MF_NNMi" maps the priority of the BMC Remedy Ticket ( [Priority] ) to theMicro Focus NNMi event priority, i.e. if the BMC Remedy Ticket's Priority is changed to "Urgent", the NNMi event's priority is updated to "Top":
Event Lifecycle State
To set the NNMi event's lifecycle state, configure the attribute "lifecycleState" in the Clip Configuration file. The example configuration for target "MF_NNMi" maps the status of the BMC Remedy Ticket ( [Status] ) to theMicro Focus NNMi event lifecycle state, i.e. if the BMC Remedy Ticket's Status is changed to "Closed", the NNMi event's lifecycle state is updated to "Closed":
To set the NNMi event's "Assigned To" attribute, configure the attribute "assignedTo" in the Clip Configuration file. The example configuration for target "MF_NNMi" assignes a forwarded event to the NNMi Web Service Client user "clip" once the peer incident is created. The assignment of the NNMi event is not repeated on event updates:
Configuring NNMi button for generating the ticket in BMC Remedy
To generate a ticket/incident in BMC Remedy from AppLink CLIP, there are some tasks that need to be done in HPE NNMi.
Step 1: For creating the button in NNMi, from the left menu, go to Configuration -> User Interface -> Menu Items and click on * (asterisk)
Step 2: Add the name “Transfer to BMC Remedy via CLIP”, as “Menu Item Label”. In the “Unique Key” filed put a value. In the “Ordering” filed please type 2 and select the Enabled field.
Step 3: In the “Menu Item Contexts” window click on asterisk *.
Step 4: In the next screen, choose as Object Type “Incident”. In the “Menu Item Action” field please choose “New Launch Action”.
Step 5: In the next screen, the Launch Action screen will pop up. Add a name, in this case “Transfer to BMC Remedy via CLIP”. In the Full URL field please use the below link and adapt it with your corresponding Clip instance and all required fields (as per NNMi documentation).
Step 6: Please use “Save and Close” buttonfor all opened windows.
You must save all the windows, if not the changes will not be applied.
Step 7: Once you saved the screens, the new Menu option will be shown in the following screen. The option has a 2 as the ordering input.
Testing the NNM-Remedy integration by AppLINK CLIP
Step 1: Open NNM with a user with high privileges, and go to Incident Browsing -> Open Key Incidents -
> Select an incident to report in BMC Remedy and Right Click it, selecting “Transfer to BMC Remedy via CLIP”.
Step 2: A pop-up Windows will be opened and the following details will be passed from NNMi to BMC Remedy via AppLink CLIP.
Checking the event / incident pair in Clip
Open your Clip instance, click on Entities tab and check the information about that Event/Incident pair.