Precisely collaborated with ServiceNow to enhance the out-of-the-box CMDB CI Model support for Ironstream Configuration Items (CIs). This new data is integrated into the CMDB by the IRE (ServiceNow's Identification and Reconciliation Engine). This release supports LPARs, CPCs and Sysplexes.
The custom columns that were added to the out-of-the-box LPAR (cmdb_ci_mainframe_lpar) and CPC (cmdb_ci_mainframe) tables are now directly available as out-of-the-box columns on those tables. Ironstream Discovery will populate the out-of-the-box columns using the IRE. Sysplex is now also available as an out-of-the-box table (cmdb_ci_mainframe_sysplex) which Ironstream Discovery will populate using the IRE.
In upcoming incremental releases, we plan to expand our support for additional Configuration Items (CIs).
We have introduced a populateLegacyTables switch as an
application-scoped system property to allow turning off population of the legacy
(custom) tables. The switch is set to true by default. Currently the
only CIs supported within the out-of-the-box CMDB CI Class Model tables are LPARs, CPCs
and Sysplexes.
We recommend that the switch remains set to true unless
- Domain Separation is in use and a requirement of your ServiceNow environment.
- there is no requirement to discover CIs other than LPARs, CPCs and Sysplexes.
- there is no dependency on data in the legacy tables.
With the populateLegacyTables switch set to true,
Ironstream Discovery will continue to populate the custom tables and custom columns that
are populated as in previous releases and continues to use GlideRecord as the population
method for that data. Data will also be populated into the out-of-the-box tables and
columns for the CPC, LPAR and Sysplex tables. This data will be populated using the
IRE.
If the populateLegacyTables switch is set to false,
data will only be populated into the out-of-the-box tables and columns for the
CPC, LPAR and Sysplex tables. This data will be populated using the IRE. Data in the
legacy (custom) tables and columns will remain untouched but will not be updated by any
Discovery runs.
In the matching ServiceNow app for this release, all the views of legacy data are available under the 'Legacy' heading.
Using a Domain-Separated ServiceNow instance
The Configuration Tool provides two new fields: "LPAR Owner Username" and "CPC Owner Username" to configure which ServiceNow user can 'discover' the LPAR and the CPC on which the LPAR resides.
The fields do not need to be populated. When running a non-domain separated ServiceNow instance, the fields should remain unpopulated. When the fields are not populated, then both the LPAR and CPC will be discovered regardless of which user is running Discovery.
The "LPAR Owner Username" and the "CPC Owner Username" can have the same value or different values, but if one is populated, then the other must also be populated.
When the ServiceNow username of the MID server user that is running Discovery matches the value in the "LPAR Owner Username" field, then the LPAR and Sysplex CIs will be discovered. When the ServiceNow username of the MID server user that is running Discovery matches the value in the "CPC Owner Username" field, then the CPC CI on which the LPAR resides will be discovered.