The key to the design of business objects is to develop a business object
definition that models as closely (and efficiently) as possible the data that
needs to be transmitted between components of the business integration
system:
- For data that is transferred between a connector and an integration
broker, you design
application-specific business objects that model the appropriate
application entities. These entities might correspond to data
structures or technology standards used by a particular application, or to
specific technology standards used by a web server.
- For data that is processed within the business logic of an InterChange
Server collaboration object, you design
generic business objects that contain a superset of information for
the application entities that need to communicate. When the
collaboration object exchanges information with an application, maps convert
the data between the generic business object and application-specific business
object structures.
This chapter presents information on the structure of business objects for
the WebSphere business integration system, and makes recommendations for
designing both application-specific and generic business objects. The
material presented here assumes that:
- You understand the basic object concepts described in the Technical
Introduction to IBM WebSphere InterChange Server if your integration
broker is InterChange Server.
- You understand the basic concepts described in the Implementation
Guide for WebSphere MQ Integrator Broker if your integration broker is
WebSphere MQ Integrator Broker.
The main topics of this chapter are:
