Adapter business object structure

After installing the adapter, you must create business objects. There are no requirements regarding the structure of the business objects other than those imposed by the configured data handler. The business objects that the connector processes can have any name allowed by InterChange Server.

The adapter 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.

Sample business object properties

This section describes sample business object properties for an ACORD XML connector with the XML data handler.

[BusinessObjectDefinition]
 Name = ACORD_TXLife_VendorName
 Version = 1.0.0
 AppSpecificInfo = target_ns=http://ACORD.org/Standards/Life/2;
   elem_fd=unqualified;attr_fd=unqualified
 [Attribute]
 Name = VendorCode
 Type = String
 Cardinality = 1
 MaxLength = 255
 IsKey = true
 IsForeignKey = false
 IsRequired = true
 AppSpecificInfo = attr_name=VendorCode;type=attribute
 IsRequiredServerBound = false
 [End]
 [Attribute]
 Name = VendorName
 Type = String
 Cardinality = 1
 MaxLength = 255
 IsKey = false
 IsForeignKey = false
 IsRequired = true
 AppSpecificInfo = elem_name=VendorName;type=pcdata;notag
 IsRequiredServerBound = false
 [End]
 [Attribute]
 Name = ObjectEventId
 Type = String
 Cardinality = 1
 MaxLength = 255
 IsKey = false
 IsForeignKey = false
 IsRequired = false
 IsRequiredServerBound = false
 [End]
 [Verb]
 Name = Create
 [End]
 [Verb]
 Name = Retrieve
 [End]
 [Verb]
 Name = Delete
 [End]
 [Verb]
 Name = Update
 [End]
 [End]
 

Copyright IBM Corp. 1997, 2003