Through its ports, a collaboration interacts with connectors, with the Access Interface, and with other collaborations. The collaboration receives its trigger, sends requests, and gets responses through these ports. These are translated to and from application operations.
Using the scenario shown in Figure 23 as a simple example, Figure 24 shows how the collaboration drives operations throughout the in a publish-and-subscribe interaction. Figure 24 shows only a single execution path, the path that is taken if the destination application does not yet contain information about the employee. The shaded arrow paths in Figure 24 show the translations that Connector B makes as it transfers collaboration requests into requests to the application API and transfers application responses into its own responses to the collaboration.
Figure 24. Processing at runtime
In this figure, the representation of a connector includes both the connector agent and connector controller functions.
Figure 24 illustrates the following process: