Configuring the cross-launch application

The probe is supplied with a launch-in-context feature that enables you to launch the Nokia NSP Fault Management Web app from Netcool/OMNIbus Web GUI Active Event List right-click tool using two separate methods. You can configure the GUI manually. You can also configure the Web GUI using WAAPI which requires createCrossLaunchTool.xml and modifyAlertsMenu.xml.

You must run addCrossLaunchOSFields.sql by running one of these commands according to the platform to add the ObjectFullName and NokiaNspObjectId fields in alerts.status.

The createCrossLaunchTool.xml, modifyAlertsMenu.xml and addCrossLaunchOSFields.sql files are located here:

$OMNIHOME/probes/NOKIA_NSP_CrossLaunch/

On Unix:

$OMNIHOME/bin/nco_sql –server <objectserver_name> –user –password < <path_to_file>/addCrossLaunchOSFields.sql

On Windows:

%NCHOME%\bin\redist\isql.exe -S -U -P -i <path_to_file>\addCrossLaunchOSFields.sql

After executing addCrossLaunchOSFields.sql, uncomment the following lines in the message_bus_nokia_nfmp.rules rules file:

#if (exists($objectFullName))
	#{
		#@ObjectFullName = $objectFullName
    #}
    #if (exists($nspObjectId))
    #{
    #  @NokiaNspObjectId = $nspObjectId
    #}
Note: createCrossLaunchTool.xml and modifyAlertsMenu.xml are not required if you are configuring Web GUI manually.

Configure the Web GUI manually

To configure the Web GUI manually, complete the following steps.


  1. Login into the IBM Tivoli Netcool/OMNIbus WebGUI Dashboard Application Service Hub.

    https://<DASH IP or hostname>:16311/ibm/console

    Refer to the IBM Tivoli Netcool/OMNIbus Web GUI Administration and User's Guide to create a new tool of script type named NFMP-CrossLaunch with the following inputs.


    For example:

    1. Open the Event Management Tool (from the Dashboard's side bars)
    2. Select Tool Configuration and create a new tool named "NFMP-CrossLaunch"
    3. Choose Type as script and input the script as below:

      For the alarm impacted list, using objectFullName:

      var objName="{@ObjectFullName}"; 
      var sdnhost = "127.0.0.1:443"; 
      var address = "https://" + sdnhost + "/FaultManagement?view=alarmListImpacts&objectFullName=" + encodeURIComponent(objName); 
      window.open (address,"NFM-P Cross Launch"); 

      For the alarm list, using objectId/fdn:

       var alarmId='{@NokiaNspObjectId}'; 
      var sdnhost = '127.0.0.1:443'; 
      var address = 'https://' + sdnhost + '/FaultManagement?view=alarmList&alarmId=' + encodeURIComponent(alarmId); 
      window.open (address,"NSP Alarm List");
    4. * replace the IP <127.0.0.1> with your Nokia NFM-P server hostname or IP address accordingly.
      Note: When SSL is enabled on NFM-P, ensure the following settings are correct:
      1. Ensure the protocol is changed from http to https.
      2. Ensure the IP address contains a port number configured for the NFM-P Client; for example, 127.0.0.1:4321

  2. Refer to IBM Tivoli Netcool/OMNIbus Web GUI Administration and User's Guide to perform the menu configuration and modify alert menu to include NFMP-CrossLaunch that should be created in step 2 from available items.

    For example:

    1. Open Event Management Tool > Menu Configurations
    2. Click on "alerts" from the available menu and click on the "Modify" button.
    3. Add the NFMP-CrossLaunch tool that was previously created in step 2 from the available items to the current items.
    4. Click Save.
    5. Open Active Event List.
    6. Click Refresh.
    7. Right click on one of the alarms received from NFM-P. You should see NSP-AlarmListImpacted and NSP-AlarmList as an options.

Configure the Web GUI using WAAPI

To configure the Web GUI using the WAAPI, complete the following steps.


  1. Refer to the IBM Tivoli Netcool/OMNIbus Web GUI Administration API (WAAPI) User's Guide to create a new tool by using createCrossLaunchTool.xml. NSP-AlarmListImpacted and NSP-AlarmList must not exist before this step.

    For example:

    1. Go to WebGUI WAAPI bin dir.
    2. Modify the createCrossLaunchTool.xml to change the sdnhost in the line below to your Nokia NFM-P server hostname or IP address and save the XML file:
      <tool:script foreach="true"  command="var objName='{@ObjectFullName}'; var sdnhost = '127.0.0.1:443'; var address = 'https://' + sdnhost + 
      '/FaultManagement?view=alarmListImpacts&amp;objectFullName=' + encodeURIComponent(objName); window.open (address,&quot;NSP Alarm Impacted List&quot;);" />
    3. After reviewing and modifying createCrossLaunch.xml run this command:
      $WAAPI_BIN_DIR/bin/runwaapi -file 
      $OMNIHOME/probes/<platforms>/NOKIA_NFMP_CrossLaunch/createCrossLaunchTool.xml
      -user <WAS_USER_ID> -password <WAS_USER_PASSWORD>
  2. Refer to the IBM Tivoli Netcool/OMNIbus Web GUI Administration API (WAAPI) User's Guide to modify the alert menu by using modifyAlertsMenu.xml.
    Note: Running the modifyAlertsMenu.xml will overwrite your existing alerts menu items. Make sure in modifyAlertsMenu.xml the content under modify.menu does not overwrite any of your existing items in the Alerts menu.

    Make any changes if required, or you can run the manual step in above section to add in the newly created NFMP-CrossLaunch tool to the Active Event List alerts right-click tool menu.

  3. After reviewing and modifying the modifyAlertsMenu.xml run this command:
    $WAAPI_BIN_DIR/bin/runwaapi -file 
    $OMNIHOME/probes/<platforms>/NOKIA_NFMP_CrossLaunch/modifyAlertsMenu.xml
    -user <WAS_USER_ID> -password <WAS_USER_PASSWORD>
  4. Open Active Event List and click Refresh.
  5. Right click on one of the alarms received from NFM-P. You should see NSP-AlarmListImpacted and NSP-AlarmList as an option.