...
Option Name | Description |
Specification for generation of product activity monitoring events. | |
Broker Interface Directory where Universal Broker will create its broker interface file. | |
Path to PEM formatted trusted CA X.509 certificates. | |
Path to Broker's PEM formatted X.509 certificate. | |
Number of days prior to certificate expiration to begin issuing informational messages about the expiration. | |
Path to PEM formatted CRL. | |
Text translation code page. | |
Component interface backlog size for pending connection requests. | |
Component definition file directory. | |
SSL cipher list for the control sessions. | |
Time-out for DNS cache. | |
Events to be generated as persistent event records. | |
Base directory where product is installed. | |
Log file directory. | |
Total number of log files that will be saved within the log directory. | |
Total number of lines to be written to the log file before the log file is wrapped. | |
Location where messages are written. | |
Language of written messages. | |
Level of messages written. | |
Minimum SSL protocol level that will be negotiated and used for communications channels. | |
Duration of a monitoring event record in the Universal Broker local UES database. | |
List of message IDs representing Universal messages to be suppressed. | |
UMC and UTT file directory. | |
Duration of a persistent event record in the Universal Broker local UES database. | |
PID file location. | |
Path to Broker's PEM formatted RSA private key. | |
Password for the Broker's PRIVATE_KEY. | |
REQ_UPPS_CONN | Number of PeopleSoft connections that Universal Broker will request from a pool of connections permitted by your Universal Agent license. |
REQ_USAP_CONN | Number of SAP connections that Universal Broker will request from a pool of connections permitted by your Universal Agent license. |
Specification for whether or not Universal Broker will enforce the use of SSL connections by the clients (managers) of Universal Command Server and Universal Data Mover Server, | |
Specification for whether or not the Start Component request is retryable when the maximum number of components are running. | |
Maximum number of simultaneous components. | |
Service interface backlog size for pending connection requests. | |
TCP/IP address on which the Broker listens. | |
TCP/IP port number on which the Broker listens. | |
Spool file directory. | |
Temporary file directory. | |
Trace file directory. | |
Maximum number of lines written to the trace file. | |
Memory trace table specification. | |
Broker's working directory. | |
Override Options | The following Universal Broker configuration options let you override UAG, OMS, and UEM automatically start component definition options and multiple UAG configuration options at Universal Broker start-up. |
UAG_AUTOSTART | UAG AUTOMATICALLY_START component definition option override. |
UEM_AUTOSTART | UEM AUTOMATICALLY_START component definition option override. |
OMS_AUTOSTART | OMS AUTOMATICALLY_START component definition option override. |
UAG_AGENT_CLUSTERS | UAG AGENT_CLUSTERS configuration option override. |
UAG_EXTENSION_ACCEPT_LIST | UAG EXTENSION_ACCEPT_LIST configuration option override. |
UAG_EXTENSION_CANCEL_TIMEOUT | UAG EXTENSION_CANCEL_TIMEOUT configuration option override. |
UAG_EXTENSION_DEPLOY_ON_REGISTRATION | UAG EXTENSION_DEPLOY_ON_REGISTRATION configuration option override. |
UAG_EXTENSION_PYTHON_LIST | UAG EXTENSION_PYTHON_LIST configuration option override. |
UAG_NETNAME | UAG NETNAME configuration option override. |
UAG_OMS_SERVERS | UAG OMS_SERVERS configuration option override. |
UAG_TRANSIENT | UAG TRANSIENT configuration option override. |
...
- Stopping and starting Universal Broker
- Sending Universal Broker a Universal Control REFRESH command, which instructs Universal Broker to reread all its configuration files, including the UACL file.
...