6.3 Configuring Remote Container Servers

6.3.1 Setting Configuration Options for Remote Containers

After installing a Remote Container server either with the standard Operations Center install or separately as a custom install, Remote Container configuration options must be set using the Operations Center Configuration Manager.

Since any number of Remote Container servers can run from a single installation, updating the Configuration Manager settings updates the settings for all Remote Container servers that have been defined.

To configure Remote Container servers:

  1. Open the Configuration Manager by performing one of the following steps, depending on your operating system:

    • For Windows, from the desktop, click Start > Programs > NetIQ Operations Center > Configure NetIQ Operations Center.

    • For UNIX, from the /OperationsCenter_install_path/bin directory, enter Customizer at the command prompt.

    For more information about the Configuration Manager, see the Operations Center Server Configuration Guide.

  2. Click Remote Container.

    The Remote Container server settings display in the right pane.

  3. Configure the following settings as necessary.

    Setting

    Description

    Remote Container Java Runtime Environment

    Specifies the path to the moscontainer.exe file. The ‑jvmhome setting points to the Java Runtime Environment (JRE) used to run the Remote Containers servers.

    Remote Container Java Runtime Options

    Command line options used by the specified JRE for running the Remote Container server. Usually does not need to be changed.

    Remote Container Trace Destination

    The settings for the Remote Container server trace logs.Click Settings and configure the logging TRC file output.

    For more information about configuring Trace Log settings, see Configuring Trace Logs in the Operations Center Server Configuration Guide.

    Remote Container Server Trace Level

    Controls how much information is passed to the Remote Container server trace logs. Set the trace file logging level.

    For more information about configuring Trace Log settings, see Configuring Trace Logs in the Operations Center Server Configuration Guide.

  4. To configure the remote container to start when the daemon starts, do the following:

    1. Click Daemon.

    2. If only Remote Container servers run from this installation, then delete the default Database Image Formula value from the Automatically Start Servers setting.

    3. Append the Automatically Start Servers setting with the names of the remote container servers to that should start automatically when the mosdaemon starts.

      For example, ContainerRCServer1,ContainerRCServer2

      By default, two predefined Remote Container servers are installed: (ContainerRCServer1 and ContainerRCServer2). Additional Remote Container servers can be created using the mkcontainer command (see Step 2).

  5. Restart the Remote Container server.

6.3.2 Customizing Remote Container Servers for Data Integrator Adapters

Data Integrator definitions cannot be created on a Remote Container; they must be created and deployed on a Operations Center server. Data Integrator definitions are only available to Remote Containers as adapter instances.

If running a server that is dedicated to Remote Containers and not sharing the same directory structure as the Operations Center server, you must manually copy the JAR file for Data Integrator integrations to the Remote Container server before the adapter instance can run on the Remote Container server.

NOTE:For an installation having both a Remote Containers and a full Operations Center integration sharing the same directory structure, you do not need to perform the following procedure.

To prepare a Remote Container server (not sharing the same directory structure as the Operations Center server) to run Data Integrator adapters:

  1. After deploying the Data Integrator definition, copy the DataIntegratorDefintionName.jar file from the /OperationsCenter_install_path/integrations directory on the Operations Center server to the /OperationsCenter_install_path/integrations directory on the Remote Container server.

    For example, if you have created and deployed a Data Integrator definition named DBDATA on server A and wish to create and run an adapter instance on an installation of Remote Containers on server B, copy /OperationsCenter_install_path/integrations/DBDATA.jar from server A to the /OperationsCenter_install_path/integrations directory on server B.

  2. Restart the Remote Container.

For more information about the Data Integrator, see the Operations Center Data Integrator Guide.

6.3.3 Changing Individual Remote Container Server Settings

To configure a specific Remote Container server without affecting other Remote Container servers that have been defined, you must manually edit the Remote Container’s INI file or add a custom properties file for the Remote Container.

To make setting changes for a single Remote Container server:

  1. Do one of the following:

    • Edit the INI file for the remote container, /OperationsCenter_install_path/config/template/ContainerRemoteContainer_name.ini

      For example, ContainerRCServer1.ini is the INI file for a Remote Container server named RCServer1.

    • Create and add the custom setting to a custom properties file named ContainerRemoteContainer_name.custom.properties in the /OperationsCenter_install_path/config directory.

      For example, ContainerRCServer1.custom.properties is a properties file for a Remote Container server named RCServer1.

      For more information about custom properties files, see Making Custom Changes in the Operations Center Server Configuration Guide

  2. Stop and restart the Remote Container server for changes to take effect.

    For instructions, continue to Section 6.4, Starting, Monitoring or Stopping a Remote Container Server.