6.0 Using Remote Containers

A Remote Container is used to distribute the running of Operations Center adapters and integrations across several machines or to run Operations Center adapters and integrations under a different JVM, or other configurations, than the Operations Center server.

A Remote Container server is a Java program that runs in its own Java Virtual Machine (JVM) on either the same host machine or a different host machine as a Operations Center server, and uses the same daemon port as the Operations Center server.

Use Remote Containers when you want to:

  • Tighten Security on Firewall: If running the Operations Center server outside your firewall and you need to limit the number of open ports to the firewall, install a Remote Container on a host server inside the firewall that will connect with all your management systems and integrations inside the firewall. The Remote Container connection requires only one port to be open to deliver all information back to the Operations Center server.

  • Integrate to Different JVMs: If running an Operations Center server with a 64-bit JVM, configure the Remote Container to use a 32-bit JVM in order to integrate to Remedy 7, which is an integration that only supports 32-bit JVMs.The Remote Container connects to the Remedy integration and reports back to the Operations Center server.

  • Integrate to Different Operating Systems: If the Operations Center server is running on a UNIX server and you need to integrate to SMARTS EMC (which is only supported on Windows), install a Remote Container on the Windows server. The Remote Container connects to the SMARTS EMC integration and reports back to the Operations Center server.

  • Decrease Memory Demands and Start Up Time: If the Operations Center server is at memory capacity, you can off-load one or more running adapters and integrations onto Remote Container servers running on a different host server. In addition, off-loading adapters and integrations can improve Operations Center server start up time.

Adapter instances on a Remote Container server are configured and viewed using the Operations Center console. Elements originating from adapters on Remote Container servers transparently display alongside local elements. A Remote Container adapter is like any other Operations Center adapter that collects information from management systems. The difference is a Remote Container adapter collects information from the Remote Container server.

For more information about Remote Containers and how they are different from an Operations Center server, see Section 6.1, About Remote Containers.

The basic steps to setting up and using Remote Containers are:

  1. Install the Remote Container server. A Remote Container server is automatically installed with Operations Center. You’ll only need to do this step if you want to run the Remote Container on a different host server from Operations Center, or create additional Remote Container instances than those defined by default.

    For instructions, see Section 6.2, Installing Remote Container Servers.

  2. Configure and Manage the Remote Container servers. Remote Container server options are set in the Operations Center Configuration Manager and apply to all Remote Containers.

    For instructions, see Section 6.3, Configuring Remote Container Servers and Section 6.4, Starting, Monitoring or Stopping a Remote Container Server.

  3. Define connections to the Remote Container servers. One or more connections must be created to allow Operations Center to communicate with the Remote Container. They also run all adapters and integrations just like in Operations Center.

    For instructions, see Section 6.5, Defining Remote Container Connections.

  4. Create adapters on the Remote Container.

    For instructions, see Section 6.6, Configuring Adapters on Remote Containers.