IBM E02HMLL-I Implementation Guide - Page 24
generic, business, object.
![]() |
View all IBM E02HMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 24 highlights
somewhat different set of information, store the information in a different order or format, or have a different name. After the connector agent has built an application-specific business object, it sends the business object to the connector controller in the InterChange Server Express. The connector controller exchanges business objects between collaborations and the connector agent. Collaborations are generally application-neutral, so the business object that a connector controller exchanges with a collaboration must be a generic business object. The use of generic business objects enhances the reusability of the collaboration because its business logic is not bound to specific versions of specific applications. Note: Generic business object names do not include a company name or product name. Examples include Contact, Employee, and Customer. Figure 7 shows where the two kinds of business objects fit within the IBM WebSphere Business Integration Server Express system: the collaboration interacts using generic business objects and the connector agent supports business objects designed for specific applications. InterChange Server Generic Application-Specific Collaboration Generic Business Objects App A Business Objects App A Connector Agent App B Business Objects App B Connector Agent App C Business Objects App C Connector Agent Figure 7. Generic and application-specific business objects You can use the same connector to run multiple types of collaborations, if the connector supports the business objects used by those collaborations. 12 IBM WebSphere Business Integration Server Express and Express Plus: System Implementation Guide
![](/manual_guide/products/ibm-e02hmlli-implementation-guide-69bfebe/24.png)