Transports and Interfaces: Siebel Enterprise Application Integration > EAI MQSeries Server Transport >
Invoking a Workflow Using MQSeries Server Receiver
Following are examples of commands to create named subsystems and start a MQSeries Server Receiver to invoke a workflow.
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 an EAI Transport Data Handling Subsystem
The following command creates an EAI Transport Data Handling Subsystem:
create named subsystem MYDataSubSys for subsystem EAITransportDataHandlingSubsys with DispatchWorkflowProcess="MQ Inbound Workflow"
Command to Create an EAI Transport Connection Subsystem
The following command creates an EAI Transport Connection Subsystem:
create named subsystem MYSubSys for subsystem mqseriesserversubsys with MQQueueManagerName=QueueMgr, MQPhysicalQueueName=LocalQueue
Command to Start an MQSeries Server Receiver
The following command starts an MQSeries Server Receiver:
start task for component MqSeriesSrvRcvr with ReceiverConnectionSubsystem=MYSubSys, ReceiverDataHandlingSubsystem=MYDataSubSys, ReceiverMethodName=ReceiveDispatch
When calling your workflow 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: