This chapter describes how to define and configure a User-defined Program Execution Server (UPES). Via a UPES, workflow nodes can issue requests to the connector for WebSphere MQ Workflow.
Two command line parameters must be specified at workflow design time that indicate which verb and collaboration to use when posting the data structure to ICS. The connector requires that these parameters follow a name-value format and that multiple name-value pairs be delimited by semi-colons. Currently, three values can be specified: verb, collab, and boname. For example, to specify that the workflow data structure be issued to the connector and then processed with an Update verb in collaboration CreditInfoSync, the program parameters must equal verb=Update; collab=CreditInfoSync.
Additionally, you can also supply the business object name, if required. This is helpful in the case where the request is synchronous from Workflow and asynchronous from the adapter's perspective (no collaboration name specified). Consider a scenario in which two or more collaborations are expecting the same event. This scenario would require duplicate business object definitions instead of duplicate MQWF data containers. Supplying a boname will solve the problem.
For example:
verb=Retrieve;collab=SampleItemOrderSync_MQWF_to_Port;
boname=MQWF_SampleItemOrder
If a collaboration name is not specified (a verb=Update program parameter), the business object or (for) data structure is posted to all subscribing collaborations.
When this node is reached in WebSphere MQ Workflow, a message containing the workflow data structure is issued to the connector. The connector processes the business content and returns any changes or errors with the content.