1. Developing SOA Applications with Oracle SOA Suite
  2. Using the Human Workflow Service Component
  3. Configuring Human Tasks
  4. Specifying Java or Business Event Callbacks
  5. Specifying Business Event Callbacks

Specifying Business Event Callbacks

To specify business event callbacks:

  1. In the State column of the Events section, select a task state. Leave the Java Class field empty.
  2. Select the Trigger Workflow Event check box. This action disables the Java Class column, as shown in Figure 29-61. Each callback, such as OnAssigned, corresponds to a business event point. When a business event is fired, the event details contain the task object and a set of properties that are populated based on the context of the event being fired.

    Figure 29-61 CallBack Details Dialog with Business Events Selected

    Description of Figure 29-61 follows
    Description of "Figure 29-61 CallBack Details Dialog with Business Events Selected"

    A pre-seeded, static event definition language (EDL) file (JDev_Home\jdeveloper\integration\seed\soa\shared\workflow\HumanTaskEvent.edl) provides the list of available business events to which to subscribe. These business events correspond to the callbacks you select in the Callback Details dialog box. You must now create an Oracle Mediator service component in which you reference the EDL file and subscribe to the appropriate business event.

    Note:

    A file-based MDS connection is required so that the EDL file can be located. The location for the file-based MDS is JDev_Home\jdeveloper\integration\seed.

  3. Create an Oracle Mediator service component in the same or a different SOA composite application that can subscribe to the event.
  4. In the Template list during Oracle Mediator creation, select Subscribe to Events.
  5. Click the Add icon to subscribe to a new event.
  6. To the right of the Event Definition field, click the Browse icon to select the EDL file.

    The SOA Resource Browser dialog box appears.

  7. Select the previously created file-based MDS connection.
  8. From the list at the top, select Resource Palette.
  9. Select SOA > Shared > Workflow > HumanTaskEvent.edl.

    Click OK.

    The Event Chooser is now populated with EDL file business events available for selection.

  10. In the Event field, select the event to which to subscribe. Figure 29-62 provides details.

    Figure 29-62 Event Callbacks

    Description of Figure 29-62 follows
    Description of "Figure 29-62 Event Callbacks"

    You can have multiple human tasks available for subscribing to the event. For example, assume you performed the following:

    • Configured a human task named TaskA to subscribe to the event (for example, OnAssigned)

    • Configured a human task named TaskB to subscribe to the same event

    To distinguish between events for TaskA and TaskB and ensure that an event is processed only by the intended Oracle Mediator, you can add a static routing filter: 

    xpath20:compare(med:getComponentName(), 'TaskA')

    This only invokes this routing when the sending component is TaskA.

  11. If the EDL file was not selected from the file-based MDS connection, accept to import the dependent XSD files when prompted, and click OK. If the EDL file was selected from the file-based MDS connection, you are not prompted.

    The Oracle Mediator service component is now populated with the business event to which to subscribe. You can also subscribe to other business events defined in the same EDL file now or at a later time.

See the following documentation for additional details about business events and callbacks: