Installing the Network Manager core components

You must install the Network Manager core components before, or at the same time as, installing the GUI components.

chmod o+rx /opt/IBM/netcool/core
chmod o+rx /opt/IBM/netcool
chmod o+rx /opt/IBM/

About this task

Important: If you want to use WebSphere Application Server version 9, you must have new installation of WebSphere Application Server version 9 and Network Manager Fix Pack 11. This is because of the upgrade path is not available for WebSphere Application Server from version 8 to version 9.

Important: Installing Fix Pack 6 or later removes existing MIB files. These Network Manager Fix Packs do not contain the Management Information Base (MIB files). Network Manager Fix Pack 5 does contain the MIB files. The MIBs are required for network discovery.

If you are upgrading from Fix Pack 5 or earlier, complete the following steps to obtain the MIB files:

1. Locate a zip file named com.ibm.tivoli.netcool.ncp.mibs.all.any_*.zip within the IBM Installation Manager shared location that contains the MIB files from the previous Fix Pack installation. The exact path might be different in your installation. An example path is: /opt/IBM/IBMIM/native/
2. Unzip this file.
3. Load the MIBs into the database by running the ncp_mib command, as described in Loading updated MIB information.

If you are installing a Fix Pack later than Fix Pack 5 without upgrading, or you are unable to locate the MIB files using the above procedure, complete the following steps to obtain the MIB files:

1. Run the ncp_mib command, as described in: Loading updated MIB information.
2. If you have Network Manager 4.2 Fix Pack 5 installed, back up the contents of the $NCHOME/precision/mibs/ directory to a backup directory outside $NCHOME. For example, /mibs_backup/.
3. If you have an earlier version than 4.2 Fix Pack 5 installed, complete the following steps:
   1. Back up the contents of the $NCHOME/precision/mibs/ directory to a backup directory outside $NCHOME. For example, /old_mibs/. Keep this directory and its files in case you want to roll back to this version later.
   2. Download the Network Manager Fix Pack 5 (4.2.0.5) files from IBM Fix Central: https://www.ibm.com/support/fixcentral/
      Important: Download the files for Linux x86, regardless of which platform you are using.
   3. Expand the Network Manager package into a temporary directory.
   4. Expand the repositories/disk1/ad/native/file000876 archive file into a backup directory outside $NCHOME, for example, /mibs_backup/. This directory now contains the default MIB files.
   5. If you customized or added any MIB files, copy the customized or new MIB files from /old_mibs/ over the default files in /mibs_backup/.
4. Regardless of the version of Network Manager you installed, the /mibs_backup/ directory now contains the most current set of MIB files from Fix Pack 5, plus any additions and customizations.

After you obtain the MIB files, install the most recent version of Network Manager.

1. Install Network Manager Fix Pack 6 or later using the instructions in this procedure.
2. Copy the MIB files from your /mibs_backup/ directory to the following location within the installation: $NCHOME/precision/mibs/
3. Run the ncp_mib command, as described in: Loading updated MIB information.

To uninstall Fix Pack 6 or later and use a previous version, complete the following steps:

1. Copy the MIB files from the following directory to a temporary directory: $NCHOME/precision/mibs/
2. Delete all the files in the $NCHOME/precision/mibs directory.
3. Uninstall Network Manager Fix Pack 6 or later using the instructions in: Uninstalling fix packs.
4. If you are rolling back to 4.2 Fix Pack 5, copy the MIB files back from the temporary directory to the MIB directory: $NCHOME/precision/mibs/
5. If you are rolling back to a version prior to 4.2 Fix Pack 5, copy the MIB files back from the backup directory /old_mibs/ to the MIB directory: $NCHOME/precision/mibs/
6. Run the ncp_mib command, as described in: Loading updated MIB information

To install the Network Manager core components, complete the following tasks.

1. Start IBM Installation Manager:
   1. Change to the directory where IBM Installation Manager is installed.
   2. Run the following command:

      ./IBMIM

      IBM Installation Manager starts in wizard mode. To use command line, silent, console, or web browser mode, refer to the information on Managing installations with Installation Manager in the IBM Installation Manager documentation at: https://www.ibm.com/support/knowledgecenter/SSDV2W/im_family_welcome.html. Not all products and components support all installation modes.
2. Click Install.
3. On the next Install Packages screen where you can select packages to install, select the latest available version of the Network Manager Core Components.
   The prerequisites for installing the package are evaluated.
4. If any issues with prerequisites are displayed, resolve them using the information that is provided before you continue.
5. Click Next, agree to the terms in the license agreement, and click Next again.
6. Select the IBM Netcool Core Components package group and click Next.
   Restriction: If you are installing Network Manager on the same server as Tivoli Netcool/OMNIbus, you must install the core components in the same package group as Tivoli Netcool/OMNIbus.
7. Select the Core components to be installed.
8. Select Additional cryptographic routines if you want to use all the cryptographic options that Network Manager provides. Clear this option if FIPS 140-2 compliance is important to you, because some of the components are not compliant with this standard. For more information, see FIPS 140-2 installations.
9. On the next Install Packages screens, provide configuration information for the packages that are being installed. Use Next and Back to go through the configuration options.
10. Optional: If you are installing Network Manager at the same time as Tivoli Netcool/OMNIbus, or in the same package group as an installation of Tivoli Netcool/OMNIbus that was not configured for use with Network Manager, a new aggregate ObjectServer is created. Configure the new ObjectServer:

    Name

    Accept the default name of NCO_AGG_P, or enter a new name for the ObjectServer. If this ObjectServer is intended for use in an architecture with multiple ObjectServers, keep the _AGG_P suffix to the name. By convention, ObjectServer names are in uppercase. You need this name later to start and stop the ObjectServer. Make a note of the name in the Checklist for installation.

    Host

    Enter the host name of the server where Tivoli Netcool/OMNIbus is installed.

    Port

    Enter a port to use for connection to the ObjectServer or accept the default.

    Super user ID

    The installation uses the root Tivoli Netcool/OMNIbus user.

    Password

    Enter the password for the root user.

    Confirm password

    Enter the password again.

11. Optional: If you are installing Network Manager on a different server to Tivoli Netcool/OMNIbus, Network Manager connects to an existing ObjectServer. The ObjectServer must be running and accessible from this server. Specify the details of the ObjectServer for Network Manager to connect to.

    Name

    Enter the name of the ObjectServer.

    Host

    Enter the host name of the server where Tivoli Netcool/OMNIbus is installed.

    Port

    Enter a port to use for connection to the ObjectServer or accept the default.

    Super user ID

    Enter the user name of a user with administrative permissions for Tivoli Netcool/OMNIbus.

    Password

    Enter the password for this user.

    The connections details are checked against the running ObjectServer. Select Skip ObjectServer connection details verification and configuration if you are currently unable to verify the details, for example, if the ObjectServer is not accessible. If you skip this process, you must the changes later manually.
12. Configure the Network Manager default users. The users itnmadmin and itnmuser are created by the installer in the ObjectServer. The same password is used for both users.

    Password

    Specify a password for these users. Record the password.

    Confirm password

    Confirm the password.

13. Enter a name for the network domain. This name is visible to network operators and product administrators. You can also add, remove, and change domains later. Record the name that you choose. You need this name to start Network Manager components.
14. Enter the details for the topology database that is installed. Make a note of these details. You need the same details when you install the GUI components.
    1. Select the database type.
    2. Enter the database connection details:
       If you selected Db2® as the database type, enter the following details:

       Database name

       Enter the name of the database.

       Server host

       Enter the host name of the server where the database is installed.

       Server port

       Enter the port number for connecting to the database.

       User ID

       Enter the ID of an existing Db2 user that has permissions to create tables.

       Password

       Enter the password for this user.

       If you selected Oracle as the database type, enter the following details:

       Oracle Service Name

       Enter the Service Name for the database.

       Server host

       Enter the host name of the server on which the database is installed.

       User ID

       Enter the ID of an existing Oracle user that has permissions to access NCIM tables. The default user ID is ncim.

       Password

       Enter the password for this user.

    3. Select Create tables to hold topology data in created database to create the database tables that are needed by Network Manager. If you already created the database tables by using the database creation scripts, you do not need to select this option. If you already created the tables and you select the option to create them again, you receive an error at the end of the installation. This error indicates that the tables were not created.
    4. Select Skip database connection details verification if you do not want to verify the connection, if the database is inaccessible or for other reasons.
15. Configure the details for the poller aggregation:

    Python path

    Enter the full path to a compatible version of Python.

    Poller aggregation user

    If you are installing as a root user, you must enter the user name of a non-root user here. This user is needed to run the poller aggregation engine. If you are installing as a non-root user, the installing user is used to run the poller aggregation engine and you do not see this option in the installer. This user must be created before poller aggregation can occur.

    Poller aggregation group

    Enter the group to which the poller aggregation user belongs. If the user belongs to a different group than the installing user, the installer changes default permissions on files and folders so that poller aggregation functions. The user must exist as a member of this group before poller aggregation can occur.

16. Review the summary information and click Install.