Configuring the UPES

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.

Note:
You must have the WebSphere MQ Workflow Buildtime environment installed on your system before configuring a UPES.
  1. Start the MQ Workflow Buildtime application and click the Network tab.

    Figure 12. WebSphere MQ Workflow Buildtime: Network view


  2. From the menu bar, select System > New User-Defined Program Execution Server.

    Figure 13. WebSphere MQ Workflow Buildtime: Choosing the new UPES


  3. In the dialog box, enter a unique name for the UPES (for example, CWLDSVR).

    Figure 14. WebSphere MQ Workflow Buildtime: Naming the new UPES


  4. Click the Message Queuing tab and enter the names of the input queue and the queue manager for the connector.

    Figure 15. WebSphere MQ Workflow Buildtime: Configuring the message queue


  5. Click the Implementations tab.

    Figure 16. WebSphere MQ Workflow Buildtime: Implementations view


  6. Select Programs > New Program from the menu bar.

    Figure 17. WebSphere MQ Workflow Buildtime: Choosing new program


  7. Specify a name for the program. Because a separate UPES program must be defined for each node-to-collaboration relationship, you may want to use the same name as the collaboration.

    Figure 18. WebSphere MQ Workflow Buildtime: Naming the new program


  8. Click the Data tab and specify the data structures to be accepted by the program or collaboration. Ensure that box "Program can run unattended" is checked.

    Figure 19. WebSphere MQ Workflow Buildtime: Specifying data structures


  9. Click the Windows tab and enter an existing program to execute.
    Note:
    Although the program you specify is not executed, WebSphere MQ Workflow requires that it be defined.

    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.

    Figure 20. WebSphere MQ Workflow Buildtime: Specifying command-line parameters


  10. To make a program node issue requests to the WebSphere MQ Workflow connector, create a new program node and specify the name of the program (as defined in step 7).

    Figure 21. WebSphere MQ Workflow Buildtime: Creating the new program node


  11. Define the program execution server (CWLDSVR.FMCSYS.FMCGRP) and select either synchronous or asynchronous for the type of request.

    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.

Copyright IBM Corp. 1997, 2004