The MFG/PRO data handler is a pivotal component in the connector for QAD MFG/PRO. The connector calls the data handler to transform business objects into CIM or triplet-formatted MFG/PRO messages and to transform triplet messages into business objects.
The information in data handler meta-objects plays a crucial role in these transformations. You configure this information after you install the product files, but before startup. Unless you are customizing or extending the MFG/PRO data handler, configure the following item only:
Figure 11 illustrates the data handler meta-object hierarchy, which includes the QADDataHandlerMO and the MappingMO objects.
Figure 11. MFG/PRO data handler meta-objects
Table 8 describes the attributes for the QADDataHandlerMO.
Table 8. Meta-object attributes for QADDataHandlerMO
Attribute name | Type | Description |
---|---|---|
OutboundMappingMO | String | Name of the meta-object for outbound mapping (event processing). If this attribute is set to CxIgnore, no outbound mapping is performed. |
OutboundMappingClass | String | Class name for event processing mapping handler. This class is used to perform the mapping from triplet to Qdoc XML. If this attribute is set to CxIgnore, no triplet-to-Qdoc mapping is performed. |
XMLDataHandlerClass | String | Class name for XML data handler. |
XMLDataHandlerMO | String | Name of the meta-object used by the XML data handler |
InboundMappingMO | String | Name of the meta-object inbound mapping (request processing) |
InboundMappingClass | String | Class name for request processing mapping handler. This class is used to perform the mapping from Qdoc XML to CIM format. If this attribute is set to CxIgnore, no Qdoc-to-CIM mapping is performed. |
Table 10 describes the attributes for the OutboundMappingMO (event processing).
Table 9. Meta-object attributes for OutboundMappingMO (event processing)
Attribute name | Type | Description |
---|---|---|
tripletMapFile | String | Fully qualified pathname for the triplet XML mapping file |
qdocTemplate | String | Fully qualified pathname for the Qdoc template files |
headerMetaFile | String | Fully qualified pathname of the file containing the triplet-to-Qdoc header mappings |
confMetaFile | String | Fully qualified path name of the file containing the triplet-to-Qdoc mappings for confirmation messages |
schemaPath | String | Fully qualified pathname for the root directory containing the Qdoc XML schema files. |
Table 9 describes the attributes for the InboundMappingMO (request processing).
Table 10. Meta-object attributes for InboundMappingMO (request processing)
Attribute name | Type | Description |
---|---|---|
tripletMapFile | String | Fully qualified pathname for the triplet XML mapping file |
cimTemplatePath | String | Fully qualified pathname for the CIM template files |
inboundBoDateFormats | String | List of patterns used to parse incoming date fields, separated by ";". Default: mm/dd/yyyy;mm-dd-yyyy;yyyy-mm-dd |
Mapping meta-data and its role in format conversions is discussed in the appropriate sections below.