Using Universal Agent to Publish to a SOA Workload - Windows and UNIX
- 1 Basic Structure of Using Universal Agent to Publish to a SOA Workload
- 1.1 Command Line Options
- 1.2 Components
- 2 Example Workloads
- 2.1 JMS ActiveMQ Workload
- 2.1.1 Command Options
- 2.2 JMS Websphere Workload
- 2.2.1 Command Options
- 2.3 XD Workload
- 2.3.1 Command Options
- 2.4 MQ Series Workload
- 2.4.1 Command Options
- 2.1 JMS ActiveMQ Workload
Basic Structure of Using Universal Agent to Publish to a SOA Workload
The following figure illustrates the basic structure of using Universal Agent to publish to a SOA workload.
Command Line Options
The command line options used in this example are:
|
Option |
Description |
|
File containing the options that instruct the container what type of workload publish | |
|
Type of script specified by -script. | |
|
hostname or IP Address of the UAC Container. | |
|
Valid username. | |
|
Valid password for userid. | |
|
Start of stdin options. | |
|
Redirect the standard file from or to <filename> |
The contents of the file options.txt define the type of workload being published to (see Example Workloads).
Components
Universal Command Agent for SOA
Example Workloads
The following examples illustrate various workloads.
JMS ActiveMQ Workload
Command Options
The command options used in this example are:
JMS Websphere Workload
Command Options
The command options used in this example are:
Note
The preceding example utilizes a properties file that is located on the UAC server. The following illustrates the contents of the listed properties file:
XD Workload
Command Options
The command options used in this example are:
MQ Series Workload
Command Options
The command options used in this example are: