Ironstream™ Software IBM i Discovery ServiceNow App - ironstream_for_servicenow_discovery_1 - 7.5

Creating the Discovery Source

1. Before installing or upgrading the Ironstream IBM i Discovery app, you must manually add a data source named Ironstream_i. This data source is required by the ServiceNow Identification and Reconciliation Engine (IRE).
   Note: The data source cannot be added automatically during the app installation because the choice field for the data source must exist in the ServiceNow global scope.
   To add the data source, go to the Scripts - Background area in ServiceNow. Run the following script in the global domain:

   
   var discoverySource = 'Ironstream_i';
   var gr = new GlideRecord('sys_choice');
   gr.addQuery('element', 'discovery_source');
   gr.addQuery('name', 'cmdb_ci');
   gr.addQuery('value', discoverySource);
   gr.query();
   if (!gr.hasNext()) {
       var grNew = new GlideRecord('sys_choice');
       grNew.initialize();
       grNew.setValue('element', 'discovery_source');
       grNew.setValue('name', 'cmdb_ci');
       grNew.setValue('value', discoverySource);
       grNew.setValue('label', discoverySource);
       if (!grNew.insert()) {
           gs.info('Adding discovery source failed for: "' + discoverySource + '".');
       }
   } 

2. Download the Ironstream IBM i Discovery app from the ServiceNow Store.
   Refer to the Ironstream Administration Guide for detailed instructions on configuring the Ironstream Proxy Server.

   Important: If you already have a version of the app installed, note that your existing probe configurations will not be retained. This is the current behavior of ServiceNow.

Creating the Reconciliation Rules

To enable Ironstream to update data in ServiceNow's CMDB classes, you must create Reconciliation Rules in the ServiceNow instance before running Discovery.

Reconciliation Rules must include 'Ironstream_i' as a Discovery Source. This requirement applies only to non-custom classes that are not part of the 'Legacy' offering.

If Reconciliation Rules are not created, Ironstream Discovery can insert records into ServiceNow's CMDB classes. However, it will not be able to update those records later. For instance, if a subsequent Discovery run identifies updated attribute values, Ironstream Discovery will be unable to apply those changes.

For advice on how to create Reconciliation Rules, refer to ServiceNow's official documentation.

Upgrade Steps

Overview

If you upgrade from an earlier version of Ironstream for ServiceNow (for example, v7.2) and simply install v7.5 over your existing environment you will see multiple Configuration Tool services and installed software.

These notes explain how to avoid this issue, which was caused by corporate rebranding applied from v7.5 onwards.

1. Before installing v7.5:
   • Uninstall any previous version (e.g., v7.2).
   • Backup the conf folder to preserve user configurations and any custom changes.
     Note: User configurations in the conf folder are preserved during uninstallation, but a backup is recommended as a precaution.
2. If v7.5 is already installed over v7.2:
   • Uninstall v7.5 first, followed by v7.2.
   • Backup the <b>conf</b> folder before proceeding.
   • Reinstall v7.5 after completing the uninstallation steps.
3. Post-Installation check:
   • After installing v7.5, previously defined MCS services should still appear in the Windows Services list and function as expected when started.

Instructions for v7.4 users