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.
Figure 13. WebSphere MQ Workflow Buildtime: Choosing the new UPES
Figure 14. WebSphere MQ Workflow Buildtime: Naming the new UPES
Figure 15. WebSphere MQ Workflow Buildtime: Configuring the message queue
Figure 16. WebSphere MQ Workflow Buildtime: Implementations view
Figure 17. WebSphere MQ Workflow Buildtime: Choosing new program
Figure 18. WebSphere MQ Workflow Buildtime: Naming the new program
Figure 19. WebSphere MQ Workflow Buildtime: Specifying data structures
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, two values can be specified: verb and collab. 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. If a collaboration name is not specified (a verb=Update program parameter), the data structure is posted to all subscribing collaborations.
Figure 20. WebSphere MQ Workflow Buildtime: Specifying command-line parameters
Figure 21. WebSphere MQ Workflow Buildtime: Creating the new program node
Figure 22. WebSphere MQ Workflow Buildtime: Defining the program server
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.