Getting Started with Universal Command Agent for SOA - MQ Connector

Owned by Former user (Deleted)
Last updated: Nov 29, 2022 by IT StonebranchVersion comment


Objective

The objective of this document is to assist in the following activities regarding the Universal Command Agent for SOA: MQ Connector:

  • Installing Universal Agent for SOA 6.4.x, which is comprised of:
    • Universal Command Agent for SOA
    • Universal Event Monitor for SOA
  • Running Universal Command Agent for SOA with an MQ Connector.

Installation Requirements

The following is required for running Universal Command Agent for SOA with an MQ Connector:

  • Universal Agent 6.2.0.0 or later (32-bit package); installed, licensed, and running.
  • MQ Environment version 6 or later, with working queues.
  • MQ Client jar files for native communication to MQ must be in the following path:

The MQ Client for Java version 7.0 package with the latest fix pack is recommended.

When using a MQ CCDT to establish connections to queue managers, 7.0.1.3 or later is highly recommended.

Installation

 

Note

These instructions describe installation of the Universal Agent for SOA 6.4.x for AIX package.

 

Universal Agent for SOA 6.4.x is packaged as a compressed tar file.

The name of the Universal Agent for SOA 6.4.x package file has the following format:

sb-soa-6.4.1.0-aix-5.3.tar.Z

(The name assumes product maintenance level 6.4.1.0 for Universal Agent for SOA 6.4.x.)
 

To unpack and install Universal Agent for SOA, perform the following steps:

Step 1

Create a directory (or select an existing directory) in which to save the package file.

Step 2

Save the package file into that directory.

Step 3

Uncompress and extract the installation files in the current working directory. The command to extract the files is:
 

 
If your operating system does not support the zcat command, use the following command:
 

 
The output of the gunzip command provides the following tar file:
tar -xvf sb-soa-6.4.1.0-aix-5.3.tar

Step 4

After the extraction is complete, run the installation script, upsinst, which executes the installp command:
 

 
An installation log is written to file install.log in the current directory. upsinst automatically restarts the Universal Broker daemon, ubrokerd, at the end of the install.

Step 5

From the license file that was sent to you by Stonebranch, Inc., add the license information to the following file:
/etc/universal/uacs.conf

Step 6

Recycle Universal Broker using the following commands (cd to /opt/universal/ubroker)
 
First:
 

 
Then:
 

Step 7

Use Universal Query (cd to /opt/universal/bin) to validate that the Universal Application Container Server component of Universal Command Agent for SOA 6.4.x is running:
 
uquery -host localhost (or the name of your server)
 
The output should have the following format:
 

MQ Environment Verification

Verify that you have a working MQ environment. You must define the following MQ values, as these are needed for the Universal Command Agent for SOA jobs that you will submit: queuemanager, queuename, and channel.

You now can run jobs in MQ using the Universal Command Agent for SOA: MQ Connector.

Running a Universal Command Agent for SOA Job on z/OS Connecting to MQ Connector

Step 1

Create the UCMD Manager JCL. This provides the UCMD Manager options, references to the MQ Connector options, and the payload. It has the following format:
 

Step 2

Create the MQ Connector Command Options Data Set Member.
 
This member contains the UCA for SOA command options for the MQ Connector that specifies the required information to submit a job to the MQ environment. It is referenced with the SCR ddname and has the following format:
 

Note

If the port on which the MQ Broker is listening has been changed from its default value (1414), you must include the -mqport option to specify the current port.

Step 3

Create the Payload Data Set Member. This member contains the MQ message and is read in via STDIN.
 

Note

The LRECL length depends on the job it describes. Verify that your data set member record length can accommodate the maximum line length of your message.

 
Example:

Running a Universal Command Agent for SOA Job on UNIX Connecting to MQ Connector

Step 1

Create the UCMD script file (Mqopt) to contain the the UCA for SOA command options for the MQ Connector that specifies the required information to submit a job to the MQ environment.
 

Note

If the port on which the MQ Broker is listening has been changed from its default value (1414), you must include the -mqport option to specify the current port.

 
MQPayload.xml

Step 2

From a command prompt, execute the following command to send a message to an MQ Queue:
 

 
You can also execute the command using the Universal Command options for STDIN (-I for input and -F for file):

 
Example output:
MQ message published successfully on destination UpsQaQueue.