Configuring a dNCIM database on Linux on IBM z Systems

On Linux on IBM z Systems, you need to make some configuration changes to the dNCIM database. By default, the dNCIM database is implemented using the SolidDB database. This database is automatically installed and there is no need to perform any setup tasks. However, SolidDB is not supported on Linux on IBM z Systems. If you are working on Linux on IBM z Systems and you want to use dNCIM, you must install an alternative database and configure it to work with the Discovery engine, ncp_disco.

1. Create an entry for the database in the DbLogins.domain.cfg file, where domain is the name of your domain.
   For example:

   insert into config.dbserver
   (
       m_DbId,
       m_Server,
       m_DbName,
       m_Schema,
       m_Hostname,
       m_Username,
       m_Password,
       m_PortNum,
       m_EncryptedPwd
       m_EmbeddedProcess
       m_ScriptTimeoutSecs
   )
   values
   (
       "DNCIM",
       "Db2",
       "ITNM",
       "dncim",
       "localhost",
       "user",
       "password",
       50000,
       1
       "ncp_disco"
       100
   );

   In this insert, the m_ScriptTimeoutSecs argument sets a timeout in seconds for any SQL scripts that run against this database. A timeout might be necessary if the dNCIM database is slow; for example, when the database is not embedded into ncp_disco or with a slow database server.

   Note: In this example, the database is local to the Discovery engine, ncp_disco, and so the m_Hostname attribute is set to localhost. Keeping the database local to the discovery process ensures faster discoveries.
2. Populate the schema for the database by using the $NCHOME/precision/scripts/sql/create_db_schemas.pl Perl script.
   For example:

   ./create_db_schemas.pl -server oracle|db2|| -dbname dbname -schema schema -host hostName -username username -password password -port port -action ncim

   Where:

   • The -server attribute is the type of database.
   • The dbname attribute varies with the type of database.
     • On Oracle, use the SID value.
     • On Db2®, use the value m_DbId from the DbLogins.domain.cfg insert.
   • The schema matches the m_Schema argument from the DbLogins.domain.cfg insert. For example, set schema to dncim to match the example insert in step 1.
     Note: You can give the database schema any name. The value that you use for m_Schema in the DbLogins.domain.cfg insert must match the value you use for the -schema argument in the create_db_schemas.pl script.
   • The -action attribute takes the value ncim because the dNCIM and NCIM databases are identical in format.