OMS Server

The OMS Server is a central communication hub for OMS clients. The OMS server maintains persistent OMS messages in a message database in order to provide message reliability. As messages are received, the OMS Server routes messages to the appropriate OMS clients.

The OMS Server is deployed as a server component managed by Universal Broker. Universal Broker manages server components by providing the following services:

Start and stop servers
Manager server configuration data
Monitor server status
Provide server restart services

The OMS Server is defined as an auto-started server. As such, it is started and stopped automatically when Universal Broker is started and stopped.

Configuration

The OMS Server is configured using a set of configuration options that change its default behavior.

For detailed information on the configuration options, see OMS Server Configuration Options.

Component Definition

The Component Definition defines the OMS server to the Universal Broker. A component definition consists of a set of options the Universal Broker uses to provide server component services.

For detailed information on the Component Definition options, see OMS Server Component Definition Options.

Universal Access Control List

Universal Access Control Lists (UACLs) provide an additional layer of control for the OMS server. UACL entries are available to limit OMS client access to the OMS server.

For detailed information about UACL entries, see OMS Server UACL Entries.

Message Database

The OMS server maintained persistent OMS messages in a message database. The message database is maintain on persistent storage in order to provide message reliability.

For detailed information on the OMS message database, see OMS Server Message Database.

Universal Controller Connectivity

When a Universal Controller cluster node is not processing work, it is possible that its OMS Server connection can be silently dropped.

To detect this, a cluster node issues a heartbeat through the OMS server, and back to itself, every 30 seconds if no outgoing activity to the OMS server has occurred. The difference between the time the Controller issues the heartbeat and the time it receives the heartbeat is logged in the opswise.log.

OMS Server High Availability

The OMS server provides critical communication infrastructure for the Universal Automation Center product line. In order to provide reliable service, an OMS server High Availability (HA) deployment is required.

For detailed information on the OMS message database, see OMS Server High Availability.

Browser not supported