Toggling event sequencing for access requests

When synchronous requests are sent to the collaboration using the access framework, the sequence of requests may not be important, especially when tuning for performance. By default, event sequencing is turned on at the collaboration level for synchronous access requests.

In the 4.3 release of InterChange Server Express, new properties have been added which increase the control that users have over event sequencing. A new check box has been added to the General properties panel of the Collaboration Object in the System Manager. This check box is denoted Event Isolation, and is checked by default.

Event sequencing for synchronous access requests, is controlled both by the System Manager and by editing the ACCESS section of the InterchangeSystem.cfg file to set the value of the EVENT_SEQUENCING to FALSE. (Recall that the InterchangeSystem.cfg file is now in XML format).

The behavior of the system is dependent on the nature of the request, the value of the EVENT_SEQUENCING parameter in the configuration file and the status of the check box in the System Manager. Table 2 explains how event sequencing is affected by the various settings.

Table 2. The effect of relevant settings on event sequencing
Is External Request (SAI)? EVENT_SEQUENCING property in ACCESS section of InterchangeSystem.cfg "Event Isolation" check box in Collaboration General Properties Event Sequencing in collaboration enabled?
Yes True/Not specified Checked Yes
Not checked No
False No effect No
No No effect Checked Yes
Not checked No

Copyright IBM Corp. 2004, 2005