Preventing event ping-pong
Ping-pong
occurs when the successful execution of a request to an application
triggers an event in that application that results in an event being
created in the event table. If the connector is set to poll the
event table, it picks up the new event, sends it back to the original
source application, which in turn triggers its own additional event.
This new event in the source application continues the cycle.
Note:
When the WebSphere InterChange Server is the integration
broker, collaboration look-up and cross-reference mapping should
prevent a duplicate record from being created in the source application.
However, this additional processing is unnecessary.
To prevent ping-pong with the connector, do the following:
- Go to IBM WebSphere BI Station (transaction /n/CWLD/HOME).
- Click the Tools tab, and then click the Config Objects button.
- Click the New Entries button and enter the following information:
Configuration name--Trigger: NoEventForUser
Text--Prevent triggering for certain users
- Return to the Configuration Tab in IBM WebSphere BI Station,
and then click the Configuration Values button.
- Click the New Entries button, and then add an entry for each User Id for
which you want to prevent triggering of events.
- Configuration Name--Trigger: NoEventForUser
- Counter--Any Number
- Configuration value--User Id (connector name)
Note:
Keep in mind that this prevents the connector from
triggering events.
