Designer 10.5 | webMethods BPM Process Development Help | EDA Event Types | Adding an EDA Event Type to an Activity Step
 
Adding an EDA Event Type to an Activity Step
You can add a custom EDA event type to any activity step that supports a BPMN boundary message intermediate event. For a table of which activity steps are supported, see About Interrupting Behavior for Boundary Intermediate Events. At run time, the boundary message intermediate event will automatically emit an EDA event based on the Event Type schema XSD file. You need only to specify an EDA event type.
Note:
The Process Engine also generates and emits predefined EDA events for the process model instance and for process model instance steps. For more information, see About EDA Predefined Process Event Types.
Important:
To fully complete the following procedure, you must have an active connection to an Integration Server when you add an EDA event type to a process. If you do not, you are prompted to open a connection, or to work offline, when you add the event type. For more information, see About EDA Event Types and Integration Server Document Types.
*To add a custom EDA event type to an activity step as a BPMN boundary message intermediate event
1. Do one of the following:
*Drag an EDA event type from the Project Explorer view onto the activity step. A boundary message intermediate event is created on the activity automatically.
*Drag an EDA event from the Project Explorer view onto an existing boundary message intermediate event on an activity.
In both of the above cases, the Receive Document and Receive EDA Event fields are automatically configured for you. The Protocol Properties fields are partially configured, but you must manually specify a Destination Name.
Note:
You can also add an EDA event type by dragging an Integration Server document type that represents an EDA event type from the Package Navigator view.
*To manually configure an existing boundary message intermediate event to use the selected EDA event type:
1. Click the boundary message intermediate event you want to work with to select it.
2. On the Implementation page of the Properties view, select the EDA (For Event Triggered Processes) Receive Protocol.
3. Click the Browse button next to the Receive Document field.
4. Click the Search EDA Event Type Store tab and select the EDA event type you want to work with. You can also click the Browse Integration Server tab and select an IS document type that represents an EDA event type.
5. Verify the Connection Alias in use and specify a Destination Name.
2. Provide any additional configuration to the boundary message intermediate event as described in Configuring a Boundary Intermediate Event.
3. Save the process.
Related Topics