After the name-value pairs have been discovered, they must be inserted into the DNCIM
discovery database. Configure the DbEntityDetails.cfg configuration
file so that the name-value pairs are inserted into the DNCIM discovery
database.
About this task
The ncp_disco process uses the dbModel.entityDetails discovery database table
to populate the entityDetails table in the DNCIM discovery database with the
information from the workingEntities.finalEntity table. To configure an insert into
the dbModel.entityDetails table, complete the following steps:
Procedure
-
Edit the DbEntityDetails.cfg configuration file.
Note: Editing the ModelNcimDb.cfg configuration file makes
it more difficult to migrate your customizations. Edit the
DbEntityDetails.cfg configuration file
instead.
-
Add an insert into the dbModel.entityDetails database table to extend the
default EntityType filter.
You can have only one entityDetails mapping per EntityType filter. For
example, append a mapping similar to the following code:
insert into dbModel.entityDetails
(
EntityType,
EntityDetails
)
values
(
1, -- chassis
{
NetworkEdge = "eval(text, '&m_ExtraInfo->m_NetworkEdge')",
CustomerName = "eval(text, '&m_ExtraInfo->m_CustomerName')",
CustomerType = "eval(text, '&m_ExtraInfo->m_CustomerType')"
}
);
-
Save and close the DbEntityDetails.cfg configuration
file.
Results
The next time that a full discovery is run, the name-value pairs are inserted into the
entityDetails table in the DNCIM discovery database. The data in the entityDetails table in DNCIM is
automatically copied to the entityDetails table in NCIM and the ncimCache.entityData table.
What to do next
Ensure that custom name-value pairs are preserved between discoveries.