IBM E02HMLL-I Implementation Guide - Page 26
Binding, destinations, mapping
![]() |
View all IBM E02HMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 26 highlights
Collaboration Subscribe Connector Controller Publish Client Connector Framework Figure 8. A connector providing a triggering event Multiple collaborations can subscribe to the same event. When the connector controller publishes the event, it can publish simultaneously to all subscribers. Binding to receive access requests Instead of binding the collaboration to a connector for triggering, you can specify that the collaboration will receive access requests from external processes as triggers. Binding destinations In addition to binding collaborations to triggering elements, you also bind collaborations to the destination elements with which the collaborations will engage in request/response interactions. Destination elements can be either connectors or other collaborations. A single collaboration can be bound to multiple destination elements. Data mapping Figure 7 shows different types of business objects at each application and at the collaborations. The IBM WebSphere Business Integration Server Express system, therefore, must convert business objects into like forms so that it can send events and data across applications and collaborations. Data mapping is the process of converting business objects from one type to another. Data mapping is required whenever the IBM WebSphere Business Integration Server Express system sends data between a source and a destination that does not share exactly the source's data model. Unlike custom application integration solutions that map data directly from one application to another, InterChange Server Express collaborations generally use the generic business object between the application-specific data models. The generic business object serves as a common, cross-application data set. If you change applications in the future, you need only get a new connector and map the new application-specific business object to the generic business object. Collaborations then continue to work as they did previously. Whenever a collaboration transfers a business object across dissimilar applications, mapping transforms the business object to and from the common data set. Business object transformation takes place: 14 IBM WebSphere Business Integration Server Express and Express Plus: System Implementation Guide
![](/manual_guide/products/ibm-e02hmlli-implementation-guide-69bfebe/26.png)