WebSphere MQ Suite Async Receive Adapter

Implementing the WebSphere MQ Suite Async Receive

Configuring the WebSphere MQ Suite Async Receive

You must specify field settings in the application, using the Admin Console.

Creating or Setting Up a Service Configuration in the Admin Console

Use the field definitions in the following table to create a new configuration of the WebSphere MQ Suite Async Receive, or to set up the configuration provided with the application:

Parameters Passed From Adapter to Invoked Business Process

The following table contains the parameters passed from the WebSphere MQ Suite Async Receive to the business process it invokes:

Examples

Example 1 – Process Data

The values specified for wsmq_metadata1 and wsmq_metadata2 determine which metadata fields are included with each document. The following example is what process data would look like as a result of specifying 4095 for both wsmq_metadata1 and wsmq_metadata2:

<ProcessData> 
 <WSMQ> 
    <DocumentCount>1</documentCount> 
   <Document1 SCIObjectID="df8f5e:102fa5a6c8f:-7414"> 
     <messageId>414D5120514D5F6761727931303030205D624C4220000502</messageId> 
     <correlationId>000000000000000000000000000000000000000000000000
     </correlationId> 
     <groupId>000000000000000000000000000000000000000000000000</groupId> 
     <accountingToken>16010515000000B5E512BBA14EC030000000000000000B
     </accountingToken> 
     <replyToQueueManagerName>QM_gary1000</replyToQueueManagerName> 
      <replyToQueueName/> 
     <applicationIdData/> 
      <applicationOriginData/> 
     <messageType verbose="Datagram">8</messageType> 
     <format>MQSTR   </format> 
     <report>0</report> 
      <feedback>0</feedback> 
     <groupStatus/> 
      <encoding>273</encoding> 
     <characterSet>819</characterSet> 
     <expiry>-1</expiry> 
      <putDateTime>03-31-2005 15:58:18</putDateTime> 
      <putApplicationName>MQSeries Client for Java    </putApplicationName> 
     <putApplicationType>28</putApplicationType> 
     <messageFlags>0</messageFlags> 
     <messageSequenceNumber>1</messageSequenceNumber> 
     <offset>0</offset> 
      <persistence>0</persistence> 
     <priority>0</priority> 
    </Document1> 
 </WSMQ> 
</ProcessData>

Example 2 – Processing Batch Documents Using GETALL

The following is an example of how to process batch documents received from a WebSphere MQ server. The following example could be used as the bootstrap workflow defined in the WebSphere MQ Suite Async Receive. This example iterates through all batch documents received and extracts each of them using the File System adapter:

<process name="(MyBusinessProcess)">
 <rule name="has more docs">
    <condition>number(/ProcessData/index/text()) &lt; number(
                      /ProcessData/WSMQ/DocumentCount/text())</condition>
 </rule>
  <sequence>
   <assign to="index">0</assign>
   <choice name="for each doc">
      <select>
       <case ref="has more docs" activity="process doc"/>
     </select>
     <sequence name="process doc">
       <assign to="index" from="number(number(index) + 1)"></assign>
       <operation name="File System Adapter">
         <participant name=" (My_File_System_Adapter)"/>
         <output message="FileSystemInputMessage">
           <assign to="." from="*"></assign>
           <assign to="Action">FS_EXTRACT</assign>
           <assign to="PrimaryDocument" from="/ProcessData/WSMQ/*[number(
             /ProcessData/index/text())]/@SCIObjectID"></assign>
         </output>
          <input message="inmsg">
           <assign to="." from="*"></assign>
         </input>
        </operation>
       <repeat name="next doc" ref="for each doc"/>
     </sequence>
    </choice>
 </sequence> 
</process>

Example 3 – Sending Messages Using the Adapter

To send messages using the WebSphere MQ Suite adapter, set the parameters in a business process, as follows:

<PARM> 
<name>SSL_SETTING_ca_cert_ids</name> 
<value>Measle1:1decdec:11159ba495b:-583c,frcppe03z3:1037c71:11584abf184:-7c4d,
       MBradley1:1decdec:11159ba495b:-5837</value> 
</PARM> 
<PARM> 
<name>SSL_SETTING_cipherSuite</name> 
<value>SSL_RSA_WITH_3DES_EDE_CBC_SHA</value> 
</PARM> 
<PARM> 
<name>SSL_SETTING_keyCertID</name> 
<value>frcppe03z3:1df073d:1153772f2cb:-66de</value> 
</PARM> 
<PARM> 
<name>SSL_SETTING_ssl_option</name> 
<value>SSL_MUST</value> 
</PARM>