Component Information Database
Component Information Database
The component information database records information about all Universal Agent server components that the Universal Broker manages. It is opened during Universal Broker start-up processing.
The information captured by the Universal Broker includes, but is not limited to, the component's process ID, start time, current state, and end time.
One important aspect of this database is its ability to record the current state of a Universal Agent server component. Each time a component's state changes, it sends a notification to Universal Broker, which updates that component's record.
For the Universal Agent components that offer it, this component state provides the basis for reconnect or restart functionality, otherwise known as network or manager fault tolerance (for Universal Agent: see Fault Tolerance Implementation or network fault tolerance (for Universal Data Mover: see Network Fault Tolerance - Universal Data Mover.
When a Universal Agent server process finishes executing and its component state indicates that it has completed, Universal Broker deletes that component's information from the database.
Universal Broker stores Universal Agent component information in the bcomponent.db and scomponent.db database files.
IBM i | The database, UBR_CMP_DB, is located in the spool library, UNVSPL620. |
---|---|
UNIX | The database file resides in the /var/opt/universal/spool directory. |
Windows | The database file default location is |
z/OS | Universal Agent components access this file via an HFS- or zFS-allocated dataset, which is mounted on the z/OS Unix System Services (USS) file system. Universal Broker is capable of dynamically mounting this database during start-up, if it is not already mounted. |
Universal Spool
The Universal Spool - or more simply, the spool - supports storage of the standard file I/O that Universal Command Server redirects from user processes. When Universal Command Server executes with spooling enabled, it captures a user process' standard input, standard output, and standard error and writes them to the spool.
Universal Spool is implemented as a set of databases. Universal Broker and Universal Command Server remove the database records automatically when they are no longer required. No database maintenance jobs are required.
Universal Broker and server components are the only programs that access the spool. No user access is required. The operating system's file system security should be used to prevent all access to the spool except for the broker and server. The Broker and server require full control permissions to the spool in order to add, delete, update, and read database files.
All standard I/O files written to the spool are encrypted to insure data privacy.
The spool database files that store redirected standard input, standard output, and standard error have the format spool.stdin.compid.db, spool.stdout.compid.db, and spool.stderr.compid.db, respectively. In each of the names, compid is replaced by the server's actual component ID.
IBM i | These files are located in the spool library, UNVSPL520, in the following format:
In each file name, xxxxxxxx is the component ID expressed in hexadecimal. (The component ID is the Component ID used to identify a Stonebranch process. This is the same Component ID output by Universal Query.) |
---|---|
UNIX | These files reside in the /var/opt/universal/spool directory. |
Windows | The database files' default location is: |
z/OS | Universal Agent components access these files via an HFS- or zFS-allocated dataset, which is mounted on the z/OS Unix System Services (USS) file system. Universal Broker is capable of dynamically mounting this database during start-up, if it is not already mounted. |
---|