Skill Level: Any Skill Level

This recipe explains how to implement the event integration between ScienceLogic SL1 running at IBM Cloud and Netcool running on premise inside customer's IT infrastructure using Json payload.


For this recipe the following prerequisites are expected:

  • an existing and working Netcool environment on premise (not limited to);
  • an existing ScienceLogic SL1 instance running at IBM Cloud (not limited to);
  • network flow (outbound to internet) between ScienceLogic SL1 in the cloud and the on premise network;
  • at least 1 new VM on premise available to install the SL1 Data Collector.


  1. Install the MessageBus Probe (in case it does not exists already)

    The messagebus probe is used to receive JSON event messages from ScienceLogic SL1 solution.

    The probe needs to be installed and connected to the existing Netcool environment so the received events can be used later on the current integrations available, like ticketing, paging, emailing, automations and others.

    For more information on how to install the Netcool MessageBus Probe component, please refer to the documentation available on the following link.


  2. Install the ScienceLogic SL1 Phone Home Data Collector

    The ScienceLogic SL1 Phone Home Data Collector is used to create an outbound flow out to IBM Cloud and connect to the ScienceLogic SL1 environment.

    Events will be sent using this Data Collector to the MessageBus Probe already attached to the existing Netcool environment.

    For more information on how to install the ScienceLogic SL1 Phone Home Data Collector component, please refer to the documentation available on the following link.



  3. Architecture Overview and Event Flow

    The message will be sent from the cloud to the on premise netcool using those 2 new components – The Data Collector and the MessageBus Probe.

    After the new components being added to the solution, the event message flow should be like presented on the following picture.

    Note: MessageBus probe port may be different and it is defined in the probe config file.


  4. Required settings on the ScienceLogic side

    The integration uses the RunBook feature available on the tool. Required actions are described below.

    4.1) Create a new credential for the MessageBus probe authentication;

    Note: Check the correct Netcool Messagebus info on your own environment at the probe config file.


    Note: In password field is used, the snippet will try to use authentication when sending the payload to the probe. If no authentication is required just leave it blank. Also if the probe requires secure connection (HTTPS) use https://<ip_address> at Hostname/IP field, otherwise use http://<ip_address>.

    4.2) Create a new RunBook/Automation for normal events;


    4.3) Create a new RunBook/Automation for clearning events;

    Note this automation is very the same as the previous one, just the Policy Type is different.

    What this automation will do is to send the Harmless event to Netcool every time an event gets cleared at SL1.


    4.4) Create a new RunBook/Action for preparing the event;


    Get the code for this snippet at https://github.ibm.com/MnE-ScienceLogic/Netcool-Integration/blob/master/GSMA_Event_Identification.py

    4.5) Create a new RunBook/Action for sending the event to Netcool;


    Get the code for this snippet at https://github.ibm.com/MnE-ScienceLogic/Netcool-Integration/blob/master/GSMA_Event_forward.py

  5. Required configuration files on the Netcool side

    The Probe has 2 important files, the props and the rules files.

    For the props, the most important informations are shown below. Other config lines are also required, but they are generic to all probe (like AuthUserName and AuthPassword), so not described in here.

    # Probe Specific Properties
    MessagePayload : ‘json’
    TransportFile : ‘$OMNIHOME/java/conf/httpWebhookTransport.properties’
    TransportType : ‘HTTP’
    RulesFile : ‘/opt/IBM/GSMA/probe/MsgBus/rules/gsma_eif.rules’

    For the rules, the GSMA EIF rules file was used for this integration. Please refer to the GSMA documentation for more information.

Join The Discussion