1.0 Overview of Post-Installation Configurations

After installing NetIQ® Operations Center, it is necessary to perform the following actions and configurations:

  1. If you are installing on a cluster, do all of the following steps after completing installations on all servers. For more information on installing and configuring Operations Center servers in a clustered environment, see Implementing a High Availability Solution in the Operations Center Server Installation Guide.

  2. Run the Configuration Manager, an Operations Center utility used to set configuration settings for the Operations Center servers and for Configuration Storage. Specify server settings for networking, trace logs, java, memory, and more. For instructions on using the Configuration Manager, see Section 2.0, Updating Server Settings Using the Configuration Manager.

    At any time, specific configurations can be created and copied for ease in moving Operations Center (for example from a development or test environment to production) by using the Configuration Explorer utility. Configurations are stored in one of these data stores called Configuration Storage. For instructions on using the Configuration Explorer, see Section 8.0, Managing Configurations

  3. Configure the Operations Center start options. Refer to Configuring Operations Center Start Conditions for details.

  4. Perform further customizations as required for networking, trace logs, and Java and memory settings. Refer to the following sections for instructions:

    • Configuring Network Communication Settings

      Operations Center is installed using default ports, but do consider the ports currently used and how they fit within your environment.

    • Configuring Trace Logs

      Configure trace logs for the Operations Center server and other components. Define settings applicable for the current session and those that will persist for each session.

    • Configuring Java and Memory

      The Java Virtual Machine is configured with parameters for memory allocation and installs with these default values. Before adjusting the memory, it is important to understand how memory is allocated.

  5. If you plan to use any external databases with Operations Center, you’ll need to create the database instance. Both the Operations Center data store and any external databases require a database definition to be created and managed in the Operations Center console. Refer to the following sections for instructions:

    • Configuring the Database for Configuration Storage

      The Operations Center data store is an embedded Object ODB that stores Operations Center configuration data, version tracking, and to control connections to all databases configured for use with Operations Center. Configure an external database to handle this data repository.

    • Setting Up an External Database

      Run scripts to create and configure the database instance before configuring Operations Center to connect with the database.

    • Creating and Editing a Database Definition

      Create a database definition for each database connection.

    • Configuring the Service Warehouse

      The Service Warehouse stores alarm history, alarm comments, historical performance and service level data. Even if you do not plan to use SLAs and Service Level Manager, create and define a Service Warehouse for alarm history data.

  6. Set up server security settings.

    For information about security in Operations Center, see the Operations Center Security Management Guide.

  7. Customize the implementation for users and administrators by configuring how elements and alarms are displayed in the Operations Center console, how alarm and performance history is captured, when alerts are issued after network events, and how element states are calculated. For information and instructions, see Section II, Customizing the Implementation.