| Panel | |
|---|---|
|
Overview
Universal Broker 7.5.x Reference Guide maintains the configuration files Configuration Methods - Configuration File for all Universal Agent components, including itself. The components do not read their configuration files themselves (except for Universal Enterprise Controller 7.5.x Reference Guide, which does read its own configuration file).
...
- Universal Broker is recycled (stopped and restartedStarting and Stopping Agent Components - Examples#Starting and Stopping Universal Broker Examples).
- Universal Broker is refreshed via Configuration Refresh via Universal Control.
- Universal Broker is refreshed via the Configuration Refresh via I-Management Console UEC client application.
- Universal Broker is refreshed via Configuration Refresh via Universal Configuration Manager (Windows only).
...
Universal Control refreshes the Universal Broker by issuing a configuration refresh request via its REFRESH_CMD - UCTL Manager configuration option configuration option.
The configuration refresh request directs Universal Broker to take the following actions:
Step 1 | Read all component configuration files, or the configuration file of a single, specified component, and update the configuration data in Universal Broker memory. (Currently, the only individual component that can be refreshed this way is the Universal Event Monitor Server, uems.) |
|---|---|
Step 2 | Read all component definitions Component Definition (or only the component definition for uems) in the Component Definition directory COMPONENT_DIRECTORY - UBROKER configuration option. Universal Broker replaces all component definitions with the newly read component definitions. New component definitions are added and deleted component definitions are removed. |
Step 3 | Read the Universal Access Control List (UACL) configuration entries (or only entries for uems) from the registry. Universal Broker replaces its UACL entries with the newly read entries. |
Configuration Refresh via Universal Control for Universal Event Monitor Server
Because an event-driven UEM Servers - Demand-Driven vs. Event-Driven Universal Event Monitor Server typically is a long-running process, the ability to refresh an active UEM Server's configuration and list of assigned event definitions is provided. Automatic refresh of configuration and event information for a demand-driven UEM Servers - Demand-Driven vs. Event-Driven UEM Server is not supported; the values it obtains at start-up are the ones it uses throughout its lifetime.
When a change is made to the stored UEM Server configuration settings (see Configuration Methods - Configuration File), active event-driven UEM Servers must be notified that a change has taken place. This is done via Universal Control, using the Universal Control Manager REFRESH_CMD - UCTL Manager configuration option option, along with a component type value that identifies the component to refresh (see Refreshing via Universal Control Examples).
...
When a change is made to the stored UAG configuration settings (see Configuration Methods - Configuration File), active UAG components must be notified that a change has taken place. This is done via Universal Control, using the Universal Control Manager REFRESH_CMD - UCTL Manager configuration option option, along with a component type value that identifies the component to refresh (see Refreshing via Universal Control Examples).
...
The following UAG configuration file options are dynamically updated by Universal Control Manager REFRESH_CMD - UCTL Manager configuration option:
Option | Description |
|---|---|
Logging level of UAG. | |
Level of messages to write for UAG. | |
Activates user security. | |
Timeout period between CANCEL request and force termination. | |
Directory that UAG uses for trace files (MESSAGE_LEVEL option value is set to trace). | |
Maximum number of lines to write to the trace file. | |
Size of a wrap-around trace table maintained in memory. |
...
Additionally, the following UAG UACL file entry is dynamically updated by Universal Control Manager REFRESH_CMD - UCTL Manager configuration option:
Entry | Description |
|---|---|
Allows or denies access to a task execution request and if allowed, specifies whether or not user authentication is performed. |
...
When configuration options are updated using the I-Management Console, a configuration refresh request automatically is sent to Universal Broker, and its configuration data is refreshed.
...
Step 1 | Read all component configuration files and update the configuration data in Universal Broker memory. |
|---|---|
Step 2 | Read all component definitions Component Definition in the Component Definition directory COMPONENT_DIRECTORY - UBROKER configuration option. Universal Broker replaces all component definitions with the newly read component definitions. New component definitions are added and deleted component definitions are removed. |
Step 3 | Read the Universal Access Control List (UACL) configuration entries from the registry. Universal Broker replaces its UACL entries with the newly read entries. |
...
Step 1 | Read its configuration file. Universal Broker refreshes its configuration options. |
|---|---|
Step 2 | Read all component definitions Component Definition in the Component Definition directory COMPONENT_DIRECTORY - UBROKER configuration option. Universal Broker replaces all component definitions with the newly read component definitions. New component definitions are added and deleted component definitions are removed. |
Step 3 | Read the Universal Access Control List (UACL) configuration entries from the registry. The Broker replaces its UACL entries with the newly read entries. |
...
However, unlike other components, not all Universal Broker options can be modified via I-Management Console. (In I-Management Console, these Universal Broker options are read-only.). These options can be modified only by editing the Universal Broker configuration file, ubroker.conf. For these modifications to be updated in Universal Broker memory and take immediate effect, Universal Broker must be recycled.
...
- Universal Broker must be recycled.
- Universal Broker must be refreshed by issuing a Universal Control configuration refresh request (via the REFRESH_CMD - UCTL Manager configuration option configuration option), if the modifications are made in ubroker.conf.
- Universal Broker is refreshed automatically, if the modifications are made via I-Management Console or the Universal Configuration Manager.
For a list of the Universal Broker configuration options in each category, see Universal Broker Configuration Options Refresh.