Examples

Figure 21 illustrates an environment in which event isolation is in effect between two different collaborations, B-Processor collaboration and B-to-C collaboration.

Figure 21. Two collaborations subject to event isolation
The figure shows a collaboration group and a collaboration that are subject to event isolation. In the A/B collaboration group, the B-Processor collaboration retrieves a full-value business object, B from a source connector and sends the resulting business object C to a destination connector. Because these bindings are the same as what occurs with the individual B-to-C collaboration, the 2 collaborations are subject to event isolation.

Notice that both the B-Processor collaboration and the B-to-C collaboration:

Therefore, port matching would result in event isolation for these collaborations.

The next example (shown in Figure 22) illustrates how you can use collaboration objects created from the same template in two different ways in the same environment. This practice enables you to reuse and extend an existing collaboration template, such as when you want to add features to the collaboration.

Suppose that a Y-Processor collaboration template exists and that a collaboration object instantiated from the Y-Processor template, Y-Processor Collaboration1, is in use. You want to create new collaboration features that include and extend the functions of the Y-Processor collaboration template.

One way to do this is to reuse the Y-Processor collaboration template and create a new Y-Processor collaboration object that you use in a collaboration group. That is, you instantiate a second Y-Processor collaboration object, Y-Processor Collaboration2, from the Y-Processor template and place it in a collaboration group. There are now two Y-Processor collaborations for which event isolation is needed. An intermediary collaboration--Collaboration Z in the example--can provide additional functions and ensure event isolation, without requiring changes to Y-Processor.

In Figure 22, the server applies event isolation to the Y business objects received by the collaborations with dark outlines, Collaboration Z and Y-Processor Collaboration1. The numbers indicate the sequence of processing.

Figure 22. Retrieving a full-valued business object
Another example of retrieving a full-value business object. The figure shows a collaboration group with 3 collaborations and then a single collaboration, Y-Processor collaboration1. The collaboration group receives a business object, X with a reference-valued child Y. X-Processor collaboration in the group passes the child Y to collaboration Z for processing. Collaboration Z retrieves the full-value Y business object and passes that full-value business object to Y-Processor collaboration2 for processing. Y-Processor collaboration1 receives a full-value Y business object and processes it. Because both Y-Processor collaboration1 and Y-Processor collaboration2 receive a full-value Y business object and send it to the same destination, they are subject to event isolation.

Collaboration Z and Y-Processor Collaboration2 work as a team, in terms of event isolation. The guidelines for delegated business objects are followed by Collaboration Z on behalf of Y-Processor Collaboration2.

Copyright IBM Corp. 2004, 2005