Post-installation tasks

After you install Network Manager, you need to perform some post-installation tasks.

About this task

To perform post-installation tasks:

Procedure

  1. Ensure your Network Manager installation is completed.
    You can check that the installation was successful by viewing the packages that the IBM Installation Manager successfully installed using the following commands:
    1. In IBM Installation Manager click File > Installation History.
    2. Review the status of the installed packages.
      The Package Group Name column lists the installed packages, and the Status column lists the results of the installation of that package.
    3. Click View Log to view the log file for any selected package.
  2. If you are integrating with Netcool Configuration Manager, you must now install it and then install the Netcool Configuration Manager Integration Pack. For instructions on installing these components, refer to the integration documentation at: http://www.ibm.com/support/knowledgecenter/SS7UH9/welcome
  3. Depending on the additional settings that are required, complete the steps in the following topics:
    Option Description

    Configuring LDAP for user authentication

    After a successful installation of Network Manager, you can configure LDAP for user authentication, as described in Changing the user authentication method.

    Configuring the Tivoli Netcool/OMNIbus Web GUI data source name

    		 If you installed the Network Manager GUI components and chose not to create a new Web GUI data source, you must configure Network Manager to use an existing data source. Refer to the instructions at Configuring the Tivoli Netcool/OMNIbus Web GUI data source name.
    Non-root post-installation tasks (UNIX only)
    • You can configure what user manages Network Manager processes, as described in Configuring root/non-root permissions
    • For non-root installations, you can configure your Network Manager processes to start automatically when your system is started or restarted, as described in Configuring processes to start automatically in a non-root installation.
      Note: You do not need to perform these steps if you installed Network Manager as the root user. The automatic restart is set up as part of a root installation without the need for this postinstallation step.
    Setting up a topology database after installation for Network Manager. For details of how to create the database schemas manually after installation, see Creating the topology database schemas.
    Enabling poll data aggregation if you installed Network Manager as root If you installed Network Manager as the root user, then you must run the setup_run_storm_as_non_root.sh script to enable the historical polling data processes. For details on how to do this see Enabling historical polling.
    Upgrading from a previous Network Manager version

    Follow the steps in Upgrading and migrating.
    Installing the Monitoring agent

    If you want to use IBM Tivoli Monitoring for IBM Tivoli Network Manager IP Edition, follow the steps in Integrating with IBM Tivoli Monitoring
    Configuring Network Manager for different time zones. If you are installing distributed Network Manager core component and Web application servers with different time zones, then you should set the same time zone on all servers which includes the database server as well as the core and GUI servers. This ensures that Network Manager is able to perform accurate timestamp comparisons from processes on different servers. You should also advise end users, such as network operators, that the system might display times that are different to the time in their location.
    Configuring additional cryptographic routines for the GUI

    By default, the GUI does not use any cryptographic routines that are excluded from a FIPS140-2 installation, regardless of the installation status of the core server. If you want to configure SNMP discovery options to enable MD5 and DES, set tnm.fips.mode=false in the tnm.properties file.
    Setting up automatic network view maintenance If you have multiple GUI servers, you must configure them so that only one server performs automatic network view and path view maintenance. If you have only one GUI server, you do not need to perform this task. For more information, see Setting up automatic view maintenance
  4. Depending on your requirements, you might need to carry out further configuration tasks. Check the Configuring Network Manager information.
  5. After successfully installing and configuring Network Manager, see the getting started sections. For more information, see Getting started.