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. There are two business object structures: one that corresponds to event processing and another that corresponds to request processing.

Event processing business object structure

The QAD MFG/PRO business object mirrors the structure of a QDoc. For event processing, 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. For guidelines on creating business object definitions for event processing, see Overview of generating business object definitions for event processing.

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

Request processing business object structure

For request processing, which is synchronous, you create top level objects (TLOs). TLOs are specialized objects that contain child request, response, and fault business objects. The request child BO corresponds to, and is generated from, a QDoc XML schema. It has a header and a body part. The data handler converts the request child business object into a QDoc SOAP/XML message. The connector's protocol handler then sends the request message to the QXtend web service. When it receives a the reply QDoc, it populates the response child BO of the TLO with the reply data. The response child BO corresponds to the QDoc XML response schema. If a fault message is returned, the connector populates the fault child BO. The BIA_FaultBO has been created based on the SOAP 1.2 schema (http://www.w3.org/2002/12/soap-envelope), using the XML ODA.

Business object definitions use the name of the corresponding QDoc and have a QDoc_TLO suffix.

For guidelines on creating business object definitions for request processing, see Overview of generating TLOs for request processing.

Copyright IBM Corp. 1997, 2004