Designing application-specific business objects

An application-specific business object contains data, actions to be performed on the data (verbs), and information about the data (application-specific information). Many connector methods pass an application-specific business object as an argument. For example:

Designing the relationship among the connector, the data handler, and their supported application-specific business objects is one of the tasks in connector and data handler development. Because application-specific business object design can generate requirements for connector and data handler programming logic that must be integrated into the connector development process, the developers of the connector, data handler, and application-specific business objects must work together to develop specifications for those components. The layout and design of an application-specific business object should be determined by the connector or data handler that processes it.

Note:
For best performance with InterChange Server, application-specific business objects should be smaller than 1 MB when possible and should never exceed 5 MB. Larger business objects cause performance problems due to limitations to the Java Virtual Machine upon which the InterChange Server runs.

This section covers the following topics:

Copyright IBM Corp. 1997, 2004