Configuring an EDA-Triggered Process

The EDA (For EDA Event Triggered Processes) protocol is built on the JMS protocol. Configuration is very similar to a JMS triggered process. The Connection Alias options are filtered for an EDA (deprecated) triggered process so that only JNDI-compliant entries are displayed.

Note:
If you are working in an environment where the targeted Integration Server nodes are in cluster or distributed mode, you must:

Ensure that all of the Integration Server nodes are connected to the same webMethods Broker (deprecated) instance.

Add the current Broker (deprecated) information to the file com.softwareag.eda.nerv.properties found on node 2 in: \profiles\IS\configuration\ com.softwareag.platform.config.propsloader.

Message start and message intermediate events that use the EDA (For EDA Event Triggered Processes) protocol do not have subscription filters. The filtering for EDA (deprecated) events occurs before the events reach the step. For more information, see About Message Start Events and About Message Start Events.

1. On the Implementation page in the Properties view of the receive step, select EDA (For EDA Event Triggered Processes) as the Receive Protocol.

Accept the default Connection Alias, or select a different one with the Browse button. The connection alias must exist and be enabled on the Integration Server used by the receive step.

Click the Browse button to select a Destination Name (required). The Destination Type is displayed when you hover your mouse over a specified Destination Name field.

Note:
The destination name for the start none event is a pre-configured internal value and cannot be viewed or modified.

4. Click the Browse button to select a custom Destination Name instead of using the default trigger names created at generation. The Destination Type is displayed when you hover your mouse over a specified Destination Name field.