Overview

Universal Agent features are implemented via a set of inter-related components that provide for a complete independent scheduling agent business solution. One or more components provide the technical structure for the implementation of every feature.

This page provides a description of each component that comprises Universal Agent. Each description provides links to the technical documentation (Reference and Quick Reference Guides) specific to that component. Reference Guides provide detailed technical information about the usage, syntax, format, and values of component commands and configuration options, as well as other information specific to the component. Quick Reference Guides provide summary information on the usage, syntax, format, and values of component commands or configuration options.

Stonebranch also provides separate documents for the installation of operating system-specific component packages and for component-specific error messaging. For links to these documents, see Additional Documentation.

Universal Command

Universal Command (UCMD), the core component for Universal Agent's enterprise scheduling functionality, allows you to extend the command line interface of a local operating system to the command line interface of any remote system that can be reached on a computer network. Any type of program, command, or script file that can be run from the command line interface can be run by Universal Command.

The Universal Command interface is operating-system independent. The remote and local systems can be running two different operating systems.

Universal Command consists of two components:

• Manager, on the local system, extends a command line interface to a remote system.

• Server, on the remote system, executes commands on behalf of the manager.

The manager supplies input files to, and receives output files from, the remote command on the server in real-time. As long as the remote command is running, the manager runs. When the remote command ends, the manager ends with the exit status of the remote command. With standard out and standard error as well as the exit status of the remote command available from the manager, there is no need for access to or expertise on the remote operating system.

As such, Universal Command interfaces with your platform-specific job scheduling solutions, providing visibility and control throughout your entire enterprise. This enables you to have an end-to-end view of all workload activity.

Technical Documentation

For detailed information on Universal Command, see the following documents:

Universal Command 7.4.x Reference Guide

Universal Command 7.4.x Quick Reference Guides

Universal Command Agent for SOA

Universal Command Agent for SOA - the SOA "Publisher" - lets you extend the workload execution and management features of Universal Agent to Internet and message-based workload. It receives its payload input from Universal Command through STDIN. When the parameters and data are passed in, the workload execution request is processed and any return data is passed back to Universal Command. It lets you invoke these workloads using protocols such as JMS, HTTP, and SOAP.

Universal Command Agent for SOA can be initiated from a variety of sources, regardless of platform, such as one or more job scheduling systems, workflow engines, or EAI tools, as well as from business applications and end users, enabling you to consolidate your Internet and message-based workload within your current enterprise scheduling environment.

Universal Command Agent for SOA enables you to:

1. Consolidate your Internet and message-based workload within your current Enterprise Scheduling environment.

2. Use your existing scheduler, or other workload management applications, along with your new or existing Stonebranch components.

3. Use your existing development, test, and production business processes.

4. Use a single point of workload execution that is not tied to specific vendor hardware or software platforms.

Technical Documentation

For detailed information on Universal Command Agent for SOA, see the following documents:

Universal Command Agent for SOA 7.4.x Reference Guide

Getting Started with Universal Command Agent for SOA - MQ Connector

Getting Started with Universal Command Agent for SOA - XD Connector

Universal Data Mover

Universal Data Mover (UDM) is the core component for Universal Data Mover's managed file transfer functionality. In a secure and automated manner, it allows you to transfer data between any platforms in your environment and initiated from any platform.

Every Universal Data Mover transfer operation is comprised of three components: manager, primary server, and secondary server. The manager receives commands from the user through an interactive session and/or an external script file. It then establishes a transfer session, invoking the primary and secondary servers, which actually conduct the transfer operations. Data is transferred between the servers, with either able to act as the source in a transfer operation.

A transfer session can either be two-party or three-party:

• In a two-party transfer session, the manager also serves as the primary transfer server. Transfer operations occur between the manager/primary server and the secondary server.

• In a three-party transfer session, the manager acts solely as a control point for transfer operations, sending commands to the primary and secondary servers to be executed. Transfer operations take place between the two machines under which these servers are running.

The extensive integration capabilities of Universal Data Mover allow data to be pre- and post-processed.

Universal Data Mover exceeds current security and auditing requirements, including SOX, GLBA, and HIPAA. It supports the most modern security standards and methodology, including SSL/TLS encryption, X.509 certificates, and proxy certificates.

If there is a connection failure, Universal Data Mover ensures that all interrupted transfers resume without manual intervention. It integrates with your existing workload management solution to issue alerts if connections are not reestablished after an acceptable time interval.

Technical Documentation

For detailed information on Universal Data Mover, see the following documents:

Universal Data Mover 7.4.x Reference Guide

Universal Data Mover 7.4.x Quick Reference Guide

Universal Event Monitor

Universal Event Monitor (UEM) provides a platform-independent means of monitoring local and remote system events, and executing system commands and scripts based on the outcome of those events.

It integrates with your workload management infrastructure to initiate both movement of the data to the appropriate platform and immediate processing of the data as soon as it is available; that is, by executing system commands and scripts based on the outcome of the events that it is monitoring.

Universal Event Monitor detects file creation in real-time on the operating system level and invokes a "handler" to take action on every file matching predefined criteria - whether it is renaming it, processing it locally, moving the file to another server, or notifying your job scheduling system to initiate further processing. It provides rule-based alerts and notifications that enable you to immediately handle any issues that may arise.

Universal Event Monitor can run in either of two modes: demand-driven or event-driven.

• In demand-driven mode, the Universal Event Monitor manager provides the Universal Event Monitor server with event definitions and event handlers, which is a command or script that the server executes based on the outcome of the event. This can be initiated from any system running Universal Agent and scheduled through your scheduling engine.

• In event-driven mode, a server monitors one or more system events simultaneously based on event definitions stored in its event definition database. The server monitors each event until it is no longer active, or until the event-driven server ends.
  Universal Event Monitor supports the most modern security standards and methodology, including SSL/TLS encryption.

UEMLoad

The UEMLoad utility handles all event definition and event handler database management tasks, including adds, updates, deletes, and lists / exports. UEMLoad forwards database requests to a UEM Server, which validates the information.

Technical Documentation

For detailed information on Universal Event Monitor and UEMLoad, see the following documents:

Universal Event Monitor 7.4.x Reference Guide

Universal Event Monitor 7.4.x Quick Reference Guide

UEMLoad 7.4.x Quick Reference Guide

Universal Event Monitor for SOA

Universal Event Monitor for SOA - the SOA "Listener" - lets you create file-based events from inbound Internet and message-based messages, and write the events to file.

It integrates Internet and message-based applications with systems management functions such as alerting and notification, incident and problem management, job scheduling, and data movement.