Configuring separate database types

Under certain circumstances, such as when different or remote databases are used in an integrated environment, you must complete extra database configuration steps.

1. Required: If Network Manager and ITNCM-Reports are installed together, and if the Network Manager database is Db2 and on a different server:
   1. To connect to a Db2 database on a server remote from your Tivoli® Common Reporting Installation, ensure that a Db2 client is installed and the remote database cataloged. When the database server is remote to the WebSphere® Application Server node where configuration is taking place, enter the following command at the node to add a TCP/IP node entry to the node directory:

      db2 catalog tcpip node <NODENAME> remote <REMOTE> server <PORT>

      where

      NODENAME

      Specifies a local alias for the node to be cataloged.

      REMOTE

      Specifies the fully qualified domain name of the remote DB server.

      PORT

      This value is the port on which the database is accessible, typically port 50000.

      db2 catalog database <database_name> at node <NODENAME>

      where

      database_name

      Specifies the Db2 database name.

      NODENAME

      This value is the local alias that is specified in the previous step.

   2. Add 'source $HOME/sqllib/db2profile' to your <install_user>/.bash_profile.
      Where $HOME refers to the home directory of the user, which was configured during the installation of the Db2 client to manage the client (usually db2inst1), and <install_user> is the user who installed Netcool Configuration Manager, usually 'icosuser'.

      Note: The .bash_profile is only used for bash shell, and it is different for sh, csh, or ksh.
   3. Restart your reporting server after this update. However, before you restart the Reporting Server, check that the amended login profile is sourced.
      Tip: For installations that use a Db2 database, Cognos® requires 32-bit Db2 client libraries, which are installed by the 64-bit Db2 client. However, there maybe further dependencies on other 32-bit packages being present on the system; if such errors are reported, you can check with 'ldd $library_name'.
2. Required: If Network Manager and ITNCM-Reports are installed together, and if the Network Manager database is Oracle:
   1. To connect to an Oracle database from your Tivoli Common Reporting Installation, ensure that ITNCM-Reports are installed, and then update the itncmEnv.sh file default location:

      /opt/IBM/tivoli/netcool/ncm/reports/itncmEnv.sh

      Export the following variables (where <install directory> is the Netcool Configuration Manager installation directory):

      ORACLE_HOME

      ORACLE_HOME=<install directory>/reports/oracle 
      export ORACLE_HOME

      TNS_ADMIN

      TNS_ADMIN=<install directory>/reports/oracle/network/admin 
      export TNS_ADMIN

      LD_LIBRARY_PATH

      LD_LIBRARY_PATH=<install directory>/reports/oracle:$LD_LIBRARY_PATH 
      export LD_LIBRARY_PATH

   2. Create a tnsnames.ora file located in <install directory>/reports/oracle/network/admin/
   3. Add the NCIM database to the tnsnames.ora file.
      For example: NCIM = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(Host = <Database Server>)(Port = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = NCIM) ))
   4. Add source <install directory>/reports/itncmEnv.sh to your <install_user>/.bash_profile.
      Note: The .bash_profile is only used for bash shell, and it is different for sh, csh, or ksh.
   5. Restart your reporting server after this update. However, before you restart the Reporting Server, check that the amended login profile is sourced.