Using Universal Agent to Publish to a SOA Workload - Windows and UNIX
- Stonebranch (Deactivated)
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.
ucmd -script options.txt -script_type SERVICE -host [hostname or IP Address] -userid username -pwd password -stdin
-localfile payload_file.txt
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
/wiki/spaces/UA73/pages/3770270
/wiki/spaces/UA73/pages/3770241
Example Workloads
The following examples illustrate various workloads.
JMS ActiveMQ Workload
-jmsdestination dynamicQueues/Soatest2TestQueue1 -jmsconnectionfactoryname ConnectionFactory -protocol JMS -serviceurl tcp://soatest2:61616 -timeoutsec 120 -jmscontextfactoryname org.apache.activemq.jndi.ActiveMQInitialContextFactory -mep Publish
Command Options
The command options used in this example are:
Option | Description |
|---|---|
Name of the target JMS destination queue or topic for the JMS message. | |
Connection factory to be used to establish a connection to a JMS provider. | |
Message protocol to be used for the current operation. | |
URL (internet, network, or file-based) of the target workload. | |
Length of time to wait for the request to complete. | |
Java class name of the JMS providers initial context factory. | |
Message exchange pattern to be used for the current operation. |
JMS Websphere Workload
-jmsdestination jms/Soatest2TestQueue1 -jmsconnectionfactoryname jms/SBSConnectionFactory -protocol JMS -serviceurl iiop://soatest2:2809 -timeoutsec 120 -jmscontextfactoryname com.ibm.websphere.naming.WsnInitialContextFactory -jmspropertiesfile websphere_only.properties.xml -mep Publish
Command Options
The command options used in this example are:
Option | Description |
|---|---|
Name of the target JMS destination queue or topic for the JMS message. | |
Connection factory to be used to establish a connection to a JMS provider. | |
Message protocol to be used for the current operation. | |
URL (internet, network, or file-based) of the target workload. | |
Length of time to wait for the request to complete. | |
Java class name of the JMS providers initial context factory. | |
Name and location of an XML document containing the JMS properties to be included in the JMS message. | |
Message exchange pattern to be used for the current operation. |
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:
<?xml version="1.0" encoding="UTF-8"?>
<sb:JMSProperties xmlns:sb="http://com.stonebranch/UAI/JMSProperties"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://com.stonebranch/UAC/JMSProperties
JMSProperties.xsd ">
<sb:Property>
<sb:Name>jms.initialcontext.com.ibm.CORBA.ORBInit</sb:Name>
<sb:Value>com.ibm.ws.sib.client.ORB</sb:Value>
</sb:Property>
</sb:JMSProperties>
XD Workload
-xdcmd SUBMIT -xdcmdid XDJOB1 -servicepassword xdservicepass -protocol XDSOAP -serviceurl http://soatest2:9080/LongRunningJobSchedulerWebSvcRouter/services/JobScheduler -serviceusername xdusername -timeoutsec 120 -mep REQUEST
Command Options
The command options used in this example are:
Option | Description |
|---|---|
Operation to submit to the WebSphere XD environment. | |
Used to correlate jobs. | |
Password to be passed to the target workload for authentication. | |
Message protocol to be used for the current operation. | |
URL (internet, network, or file-based) of the target workload. | |
User name to be passed to the target workload for authentication. | |
Length of time to wait for the request to complete. | |
Message exchange pattern to be used for the current operation. |
MQ Series Workload
-mqqueuemanagername MyQueueManager -mqqueuename UpsQaQueue -mqhost soatest2 -mqchannel UpsQaChannel -protocol mq -timeoutsec 120 -mep publish
Command Options
The command options used in this example are:
Option | Description |
|---|---|
Name of the MQ QUEUE Manager. | |
Name of the MQ Queue to use. | |
Name of the server running MQSeries. | |
Name of the MQ Queue to use. | |
Message protocol to be used for the current operation. | |
Length of time to wait for the request to complete. | |
Message exchange pattern to be used for the current operation. |