Adapter business object structure

After installing the adapter, you must create business objects. Business object definitions are based on QAD-defined Qdoc XML schemas. Qdoc is a proprietary XML format. To generate business objects, see Generating business object definitions: overview below.

The QAD MFG/PRO business object mirrors the structure of a Qdoc. The definition contains two first-level child business objects, one for the Qdoc header and one for the Qdoc body. When you installed the adapter, you also installed a header business object definition (that is common to all Qdocs) and a template for creating a business object definition that contains a placeholder for the body. The body business object is message-type specific.

Business objects take the name of the corresponding Qdoc schema with the addition of the prefixBIA_ and the suffix BO. For example: BIA_maintainSupplierBO.

Note:
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.

Copyright IBM Corp. 1997, 2003