Use the Connect-MQ method to invoke a connector to an external system that uses IBM WebSphere MQ messaging services.
This method operates on a named clipboard page that is the source and destination of data mappings. Make sure the Step Page column that calls this method contains the non-blank name of such a page.
This method has two parameters:
|ServiceName||Enter the Service Name (second key part) of a Connect MQ rule ( Rule-Connect-MQ rule type). The system uses the class of the step page as the first key part of the rule.|
|RunInParallel||Select if this connector is intended to run in parallel as a child requestor of the current requestor. If selected, use the Connect-Wait method later in the current or a follow-on activity to access results from the connector.|
The Connect-MQ method works as follows:
- Using rule resolution, locates the Connect MQ rule identified by the ServiceName parameter and the class of the step page or primary page.
- Uses request information in the Connect MQ rule to assemble an MQ request message.
- If the step page does not exist, creates a new page, of the class identified in the Pages & Classes tab.
- Checks whether simulation is in force for this rule. If so, calls the simulation stub activity.
- If simulation is not in force, sends the MQ message, in a separate thread if the
RunInParallel box is selected. (This temporary requestor has the
same access group and clipboard as the original.) If the limit of parallel requestors is
then eventually reached, the parent requestor will fail as well. By default, the limit is
10 requestors in parallel; you can establish a higher or lower value in the
prconfig.xmlfile or dynamic system settings using the
- Processes the MQ response message if any when it is received.
Checking the method status
This method updates the pxMethodStatus property. See How to test method results using a transition.