Examples

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

Figure 17. Two collaborations 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 18) 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 18, 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 18. Retrieving a full-valued business object


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. 2003, 2004