Universal Command Agent for SOA - Script File Command Options
Command Options Categories
Universal Command Agent for SOA uses a script file interface to accept the values needed to create the workload execution request.
The following table categorizes the command options into logical areas of application. Each Category name is a link to a table of options in that category. Each Option Name in those tables is a link to detailed information about that option.
Category | Description |
---|---|
Required for Universal Command Agent for SOA to process the workload execution request. | |
Required, depending on the PROTOCOL option value; otherwise, these options are invalid. | |
Optional usage only; use only as appropriate. |
Required Options
Option Name | Description |
---|---|
Message exchange pattern to be used for the current operation. | |
Message protocol to be used for the current operation. | |
URL (internet, network, or file-based) of the target workload. |
Dependent Options
Option Name | Description |
---|---|
Connection factory to be used to establish a connection to a JMS provider. | |
Java class name of the JMS providers initial context factory. | |
Name of the target JMS destination queue or topic for the JMS message. | |
Name of the JMS reply queue for the return JMS message. | |
Name of the MQ channel. | |
Name of the server running MQSeries. | |
Name of the MQ QUEUE Manager. | |
Name of the MQ Queue to use. | |
Name of the MQ Queue from which to read the reply when MEP is set to request. | |
Operation to submit to the WebSphere XD environment. | |
Correlates jobs. |
Optional Options
Option Name | Description |
---|---|
Lists the command options and values. | |
http authorization scheme to use. | |
Specification for whether or not there is HTTP form data, in a name-value format, in the payload file. | |
Type of HTTP operation to execute. | |
Version of the HTTP protocol to use. | |
Name and location of an XML document containing the JMS properties to be included in the JMS message. | |
Name of the port on which the MQ Broker is listening. | |
Name of the file containing the MQ name / value pairs. | |
Password to be passed to the target workload for authentication. | |
User name to be passed to the target workload for authentication. | |
soapAction HTTP header value. | |
Version of the SOAP protocol to use when making the SOAP request. | |
Length of time to wait for the request to complete. |
Command Options Syntax
The following figure illustrates the syntax of Universal Command Agent for SOA command options.
-protocol {HTTP|SOAP|JMS|XDSOAP|MQ} -mep {Publish|Request} -serviceurl url -jmsconnectionfactoryname name -jmscontextfactoryname name -jmsdestination name -jmsreplyto name -mqchannel channel | CCDT -mqhost server -mqqueuemanagername manager -mqqueuename queue -mqreplyto queue -xdcmd {SUBMIT|RESTART} -xdcmdid ID * [-httpauth {BASIC|DIGEST|NTLM}] [-httpformdata {true|false}] [-httpmethod {GET|POST}] [-httpversion {OneDotZero|OneDotOne}] [-jmspropertiesfile file] [-mqport port] [-mqpropertiesfile file] [-serviceusername name] [-servicepassword password] [-soapaction header] [-soapversion {OneDotOne|OneDotTwo}] [-timeoutsec time] -help
* The -xdcmdid option is required if -protocol is set to XDSOAP.