Universal Broker for IBM i
Currently, IBM i runs Workload Automation 5.1.1. These pages provide information for that version.
Configuration
Universal Broker reads configuration options only from the Universal Broker configuration file.
The Universal Broker configuration file is named UNVPRD511/UNVCONF(UBROKER). File UNVCONF is a physical source file located in the UNVPRD511 library. File member UBROKER contains the configuration options for the Universal Broker. File UNVCONF contains configuration members for the Workload Automation 5 for IBM i components. This file can be edited manually with any text editor.
Configuration Options
The following table identifies all of the Universal Broker for IBM i configuration options. Each Option Name is a link to detailed information about that option.
Option Name | Description |
Specification for whether or not product activity monitoring events are generated. | |
Path to PEM formatted trusted CA X.509 certificates. | |
Path to Broker's PEM formatted X.509 certificate. | |
Path to PEM formatted CRL. | |
Text translation code page. | |
SSL/TLS cipher list for the control sessions. | |
Time-out for DNS cache. | |
Events to be generated as persistent events. | |
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. Note This option was introduced to IBM i in version 5.1.1.0. | |
Duration of a monitoring event record in the Universal Broker local UES database. | |
Duration of a persistent event record in the Universal Broker local UES database. | |
Path to Broker's PEM formatted RSA private key. | |
Password for the Broker's PRIVATE_KEY. | |
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, Note This option was introduced to IBM i in version 5.1.1.0. | |
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. | |
Maximum number of lines written to the trace file. | |
Memory trace table specification. |
Component Management
Universal Broker is aware only of Universal Agent components that have been defined. It is the responsibility of Universal Broker to start, stop, and query these defined components.
One of the steps in the installation of a component is defining it to the local Universal Broker. These component definitions provide Universal Broker with the necessary information that it needs to manage the components.