JMS Connector Publish Operation - Usage

Owned by Former user (Deleted)
Last updated: Jan 24, 2023 by Stonebranch (Deactivated)
1 min read


Overview

Usage of Universal Command Agent for SOA: JMS Connector is via the Universal Command (UCMD) Manager, with command input coming from a script file specified with the SCRIPT_FILE option.

Note

Because the protocol is JMS, you must use the dependent command options in addition to the standard command options (see Dependent Options).


Universal Command Options

The following figure illustrates the Universal Command options to execute the JMS Connector Publish operation.

-script OutboundJMS_Queues_Options.txt
-script_type SERVICE
-host server1
-login YES
-userid abc
-pwd 123


Script File

The following figure illustrates the script file.

-protocol JMS
-mep Publish
-serviceurl iiop://server1:2809
-jmsdestination jms/IntegrationTestQueue1
-jmsconnectionfactoryname jms/ConnectionFactory
-jmscontextfactoryname com.ibm.websphere.naming.WsnInitialContextFactory
-jmspropertiesfile xml/websphere.properties.xml


Note

The script file illustrated above is the argument to the -script (SCRIPT_FILE) option for Universal Command shown in the first figure.

Command File

The command options shown in the first figure can be saved in a file and invoked with Universal Command via the -file (COMMAND_FILE_PLAIN) option, as shown in the following figure.

ucmd -file OutboundJMS_Queues_Invoke2.txt < JMSPayLoad.xml