WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Advanced configuration properties when using IBM Sterling Connect:Direct nodes

CDInput and CDOutput nodes can get connection details and staging directories in conjunction with a configurable service. To pick up new values when a configurable service is created or modified, you must reload the broker or execution group, by using the mqsistop and mqsistart commands, or the mqsireload command.

Before you start:

Use the CDServer configurable service to change connection details for an IBM Sterling Connect:Direct node. The properties of the CDServer configurable services are described in CDServer configurable service.

Use the following scenarios as examples of how you use the staging directories.

To create a configurable service, use the WebSphere Message Broker Explorer; see Using the WebSphere Message Broker Explorer to work with configurable services for more information, or the mqsicreateconfigurableservice command.
mqsicreateconfigurableservice MYBROKER -c CDServer -o myCDServer  
where
MYBROKER
is the name of the broker
CDServer
is the name of the configurable service
myCDServer
is the object name.

Note the -o ObjectName parameter can take any value.

Output

This example transfers a file using the CDOutput node called CDOutput, in a message flow called messageflow1, in execution group default, on broker MYBROKER.

The broker stages the file in the local file path /tmp/cdtransfer/MYBROKER/default/messageflow1/CDOutput.

The Connect:Direct server then tries to transfer the file using the file path /cdserver/transfers/MYBROKER/default/messageflow1/CDOutput.

These properties are used when the files systems are mounted differently on the broker and Connect:Direct server machines.

mqsichangeproperties MYBROKER -c CDServer
-o myCDServer -n brokerPathToStagingDir,cdPathToStagingDir
-v /tmp/cdtransfer,/cdserver/transfers 
To pick up the updated values in the configurable service, restart the execution group and message flow.

Input

This example receives a file using the CDInput node called CDInput, in a message flow called messageflow1, in execution group default, on broker MYBROKER.

A file is transferred to the Connect:Direct server, to the directory /cdserver/transfers/example1.

WebSphere Message Broker attempts to process the same file, but using the path /tmp/cdtransfer/example1.

These properties are used when the file systems are mounted differently on the WebSphere Message Broker and Connect:Direct server machines.

mqsichangeproperties MYBROKER -c CDServer -o myCDServer 
-n brokerPathToInputDir,cdPathToInputDir 
-v /tmp/cdtransfer/example1,/cdserver/transfers/example1 
To pick up the updated values in the configurable service, restart the execution group and message flow.

To display Connect:Direct server configurable services, use the mqsireportproperties command, as shown in the following example:

mqsireportproperties MYBROKER -c CDServer -o AllReportableEntityNames -r
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:43


Task topicTask topic | Version 8.0.0.7 | bc14060_