Starting Components

There are four ways in which Universal Agent components are started.

Starting Manually

The following components are started manually and run in the background until they are stopped manually:

• Universal Broker
• Universal Enterprise Controller

(See Starting and Stopping Agent Components - Examples.)

Starting via Manager

The following components are started on demand (that is, via their Managers) and run until the specified task has completed, then stop automatically.

• Universal Command Server
• Universal Control Server
• Universal Event Monitor Server (demand-driven)

Starting Automatically

The following components are auto-start components; that is, they start automatically when the Universal Broker starts and run until they are stopped manually:

• Universal Application Container Server
• Universal Event Monitor Server (event-driven)
• Universal Automation Center Agent (UAG)
• Universal Message Service (OMS)

Starting via Universal Control

Universal Control can start Server components, via the Universal Control START_CMD option, that do not require interaction with a Manager. Currently, only three Universal Agent components can be started via Universal Control:

• Universal Event Monitor Server (event-driven)
• Universal Automation Center Agent (UAG)
• Universal Message Service (OMS)

(See Starting and Stopping Agent Components - Examples.)

Stopping Components

Any Universal Agent Server component can stopped via the Universal Control STOP_CMD option.

Authorized users also are able to use the I-Activity Monitor, a Universal Enterprise Controller (UEC) client application, to stop running any Universal Agent Server component (if it is a component of an Agent being polled by UEC).