You can configure collaboration objects and connector controllers to process multiple event-triggered flows at the same time. This can significantly improve the performance for event-triggered interfaces.
Collaborations can be configured to process multiple event-triggered flows concurrently. System throughput and response time to event processing improve when concurrent event processing is properly used (see tip below). By default, a collaboration processes one event-triggered flow at a time.
When a collaboration is processing concurrent event-triggered flows, the collaboration identifies dependencies among those flows and processes them in the order that they were sent from the connector controller. Concurrent processing of event-triggered flows is performed on flows that do not have data conflicts, while flows with data conflicts are processed in the order received.
To configure a collaboration to handle multiple event-triggered flows, see Maximum number of concurrent events.
If a collaboration's inbound ports are bound only to receive external calls through the Server Access Interface, and are not bound to any connectors, you can improve performance by setting the value of Maximum number of concurrent events to zero. But do not set this value to zero if the collaboration is being used for bidirectional exchanges with connectors.
Each collaboration in a collaboration object group can be configured independently for processing a number of concurrent event-triggered flows. It is recommended that you set the same value for the number of concurrent event-triggered flows for all of the collaborations in a group, so that a collaboration with a low concurrency rate does not become a bottleneck.
Connector controllers can be configured to process multiple event-triggered flows concurrently.
Event-flow processing performance improves when a connector is configured to process triggered event flows concurrently. This is because multiple business objects can be transformed in mapping at the same time.
To configure concurrent event-triggered flow processing for connector controllers, you set the ConcurrentEventTriggeredFlows property to the maximum number of flows you want processed at the same time. For more information on this property, see ConcurrentEventTriggeredFlows. For more information on using Connector Configurator to set connector properties, see in Configuring connectors general.
If a connector is being used only as a destination, you can improve performance by setting the value of ConcurrentEventTriggeredFlows to zero. But do not set this value to zero if the connector is being used in bidirectional exchanges with a collaboration.