Universal Agent Components

Universal Agent is comprised of a suite of components that are installed as a single installation package.

There is a separate package for each of the Universal Agent supported platforms. There also are additional, separate packages for Windows and UNIX.

The following table provides links to the installation requirements and summary (including any customization information) for the packages on each platform:

Platforms	Packages
z/OS	Universal Agent 7.4.x for z/OS
Windows	Universal Agent 7.4.x for Windows Universal Enterprise Controller 7.4.x Universal Enterprise Controller Client Applications 7.4.x Universal Agent for SOA 7.4.x
UNIX	Universal Agent 7.4.x for UNIX Universal Agent for SOA 7.4.x
IBM i	Workload Automation 5.1.1 for IBM i

For complete instructions on product installation and customization, see the Universal Agent 7.4.x Installation, Upgrade, and Applying Maintenance.

Platform Requirements

Since platform requirements may change with new releases of a product, please consult the Platform Support for Universal Controller 7.4.x and Universal Agent 7.4.x page to make sure that your platform is supported before performing an installation.

Space Requirements

Space requirements for Universal Agent are driven largely by logging. A minimum 500MB of space is recommended. Each Agent contains a Universal Broker log and an Agent log.

The Universal Broker LOG_FILE_GENERATIONS configuration option lets you specify how many log files to save in the Universal Broker log directory. The default is 5.

The Agent log rolls over at midnight (12:00 a.m.) or whenever the Agent is restarted. The Log File Retention Period in Days Universal Controller system property lets you specify the number of days that an Agent log file (in addition to a Controller log file) is retained before it is purged. The default is 5 days.

Network Requirements

Universal Agent components run on z/OS, Windows, UNIX, and IBM i operating systems. These systems must be connected with a network that supports TCP/IP. For example, the Universal Command Manager running on a z/OS system must be able to establish a TCP/IP socket connection with the Universal Command Server running on a UNIX or Windows system.

TCP/IP provides a set of commands to verify network connectivity between systems. For example, the ping command can determine if an IP connection is possible between two systems. However, the ping command may not work in all network environments. In addition, the ping command may work, but a firewall may deny all other connection attempts between the two systems. Check with your local network administrator to determine the capabilities and topology of your network.

Universal Agent offers configuration parameters that can facilitate connections through network firewalls. Due to the large variety of firewall configurations, all possibilities cannot be discussed in this document. Check with your local network administrator to determine if a firewall is between the computer systems involved.

Ports Configuration

Universal Agent is composed of several components that utilize the TCP/IP network for component communications. TCP/IP routes must be available between the distributed components and firewall rules open, if necessary. The primary components using TCP/IP are Universal Broker, Universal Managers, and Universal Automation Center Agent (UAG).

Universal Broker executes on all servers on which workload management services are required. The Universal Broker accepts TCP socket connections on port 7887 from remote clients such as Universal Command Manager and Universal Data Mover Manager. A server running Universal Agent will need to be able to accept TCP connections on port 7887 in order to provide such services.

Universal Manager components include Universal Command Manager, Universal Data Mover Manager, and others. Manager components initiate TCP socket connections to remote Universal Brokers. If Universal Manager services are required, the Managers will need to be able to open TCP connections to remote Universal Brokers on port 7887.

UAG initiates a TCP socket connection to the Universal Message Service (OMS) deployed on a remote, centrally located server. OMS accepts TCP connections on port 7878. UAG must be able to open a TCP connection to the remote OMS server on port 7878.

The port numbers above are default port numbers. They can be changed in the respective component configuration, if necessary.

Additional Requirements

In order to install any of these Universal Agent components, you must be able to write to the directory from which the installation is launched.

Browser not supported