Bookshelf Home | Contents | Index | Search | PDF

Transports and Interfaces: Siebel eBusiness Application Integration Volume III > EAI MQSeries Transports >

Invoking a Workflow Process Using MQSeries Server Receiver

---

Following are examples of commands to create named subsystems and start a MQSeries Server Receiver to invoke a workflow process.

NOTE:  If there is either an exception step or an error process in your workflow, the workflow assumes that the error step or the error process will handle the error and the workflow will not send the error out. In order to capture the error, you need to insert a stop step into your workflow. Note that by putting in a stop step, the caller gets the generic workflow stop error and not the original error, but the original error is stored in the Error Code and Error Message process properties.

Command to create EAI Transport Data Handling Subsystem

create named subsystem MYDataSubSys for subsystem EAITransportDataHandlingSubsys with DispatchWorkflowProcess="MQ Inbound Workflow"

Command to create EAI Transport Connection Subsystem

create named subsystem MYSubSys for subsystem mqseriesserversubsys with MQQueueManagerName=QueueMgr, MQPhysicalQueueName=LocalQueue

Command to start a MqSeriesSrvrRcvr

start task for component MqSeriesSrvRcvr with ReceiverConnectionSubsystem=MYSubSys, ReceiverDataHandlingSubsystem=MYDataSubSys, ReceiverMethodName=ReceiveDispatch

When calling your workflow process by the MQSeries Server Receiver, it is not necessary to include a step to pull the messages off the queue and pass them to the next step. The MQSeries Server Receiver automatically pulls the messages off the queue and passes them on if:

You have created a new process property of data type String and a default string of <Value>. This process property stores the inbound message text picked up by the MqSeriesSrvRcvr.
In your workflow process step, where you handle the inbound messages from IBM MQSeries, you insert an input argument of <Value> with type Process Property. The Property Name will be the name of the process property you created in the previous step.

NOTE:  When you type in <Value>, the display name may change to Message Text or XML Document.

Bookshelf Home | Contents | Index | Search | PDF