Connector business object structure

After installing the connector, you must create business objects or use (or modify) those shipped with the connector.

The Telcordia connector can processes Telcordia schema files. Each schema file has a corresponding IBM WebSphere InterChange Server business object. The business objects are generated using the XML Object Discovery Agent (ODA). You must specify a prefix, such as Telcordia_, for these objects; follow the naming conventions specified in the TelcordiaPrefix_SchemaFileType. The six tested adapter-specific business objects are:

For more on generating business objects using the XML ODA, see Generating Telcordia business objects based on schema documents.

There are no additional requirements regarding the structure of the business objects other than those imposed by the configured data handler. For more on naming conventions see the Naming Components Guide.

The connector retrieves messages from a queue and attempts to populate a business object (defined by the meta-object) with the message contents. Strictly speaking, the connector neither controls nor influences business object structure. Those are functions of meta-object definitions as well as the connector's data handler requirements. In fact, there is no business-object level application information. Rather, the connector's main role when retrieving and passing business objects is to monitor the message-to-business-object (and vice versa) process for errors.

Copyright IBM Corp. 1997, 2004