Introduction

After installing the connector, you must create business objects.

The connector comes with sample business objects only. The systems integrator, consultant, or customer must build business objects.

The connector is a metadata-driven connector. In business objects, metadata is data about the application, which is stored in a business object definition and which helps the connector interact with an application. A metadata-driven connector handles each business object that it supports based on metadata encoded in the business object definition rather than on instructions hard-coded in the connector.

Business object metadata includes the structure of a business object, the settings of its attribute properties, and the content of its application-specific information. Because the connector is metadata-driven, it can handle new or modified business objects without requiring modifications to the connector code. However, the connector's configured data handler makes assumptions about the structure of its business objects, object cardinality, the format of the application-specific information, and the database representation of the business object. Therefore, when you create or modify a business object for the iSoft connector, your modifications must conform to the rules the connector is designed to follow, or the connector cannot process new or modified business objects correctly.

The business objects that the connector processes can have any name allowed by the InterChange server. For more on naming conventions, see Naming WebSphere InterChange Components.

The connector retrieves messages from a queue and attempts to populate a business object (defined by the meta-object) with the message contents. The required business object structure is dependent on the meta-object definitinos as well as the connector's data handler requirements.

Copyright IBM Corp. 1997, 2003