EAI MQSeries Transport -Session 1

In the previous post we have talked about HTTP transport in this we are going to talk about the Queue based transport.

In simple words a Queue is nothing but a medium through which the data gets transported to other system. Siebel supports multiple queue mechanisms such as MSMQ , JMS, MQ Series etc.

We will be discussing about sending the message to external system using IBM MQ Series Queue Mechanism. Siebel provides vanilla business service 'EAI MQSeries Server Transport'  to send/ receive messages from queue based on MQ Series.

Pre-requisite:

• IBM MQ Server should be up and running .
• Queue Manager and Send Queue must be set before sending the data to the Queue .

Create a sample workflow to explain the input and output arguments required for EAI MQSeries Server Transport

to send message or placing a message on Queue.

Input Arguments- 

      1.     <Value> - This is a required input parameter and it contains the message to be send .

      2.     MqPhysicalQueueName - This is an optional parameter using it you provide your workflow which Mq transport

            service it has to use. (These details will be provided to you by the other team).

      3.    MqQueueManagerName – This is an optional parameter  it contains the Name of queue manager for request  

           connection.(These details will be provided to you by the other team). 

Output Arguments –

       1)     MqSentMessageId – This is an optional parameter used to indentify the sent message.

Sample workflow to send the data to Queue.

Validation

To validate whether data has been successfully reached go to IBM Websphere MQ Explorer Queue. Please find the screenshot below:

  

You can browse the message and see in the message properties data in message data.

We are going to talk about the Inbound Transport using Queue in the next post.