Table 162 lists the standard features for connector handling of business object requests. The table includes a brief description of each feature and a page number of the section in the book containing more information on the feature.
Table 162. Standard features for request processing
Category and name | Description | Supported? |
---|---|---|
Business Object and Attribute Naming | ||
Business object names | Business object names should have no semantic value to the connector. Two business objects with the same structure, data, and application-specific information but with different names should process identically in the connector. |
|
Attribute names | Attribute names in a business object should have no semantic value to the connector. Values such as application table name or column name should be stored in the application-specific information field of the attribute and not in the attribute name. |
|
Create | ||
Create Verb | The connector creates the object in the destination application. The application object includes all values in the business object, including child objects. See "Handling the Create verb". |
|
Delete | ||
Delete Verb | The connector supports the Delete verb, and when processing this verb, it does a true physical delete, not a logical delete. See "Handling the Delete verb". |
|
Logical delete | The connector supports logical deletes operations via the Update verb only. The Delete verb is used only for physical deletes. See "Implications of business objects representing logical Delete events". |
|
Exist | ||
Exist Verb | The connector checks for the existence of an entity in the application database. It returns SUCCEED if the object passed in exists in the application database, and FAIL if the object does not exist in the application database. See "Handling the Exists verb". |
|
Retrieve | ||
Retrieve Verb | The entire hierarchical image (including all child business objects) is retrieved from application when the Retrieve verb is processed. The retrieve is based only on the key values of the business object. See "Handling the Retrieve verb". |
|
Ignore missing child object | If IgnoreMissingChildObject is set to true in the business object level application-specific information, the connector returns SUCCEED even if not all the children specified in the business object are found in the application. See "Retrieving child objects". |
|
RetrieveByContent | ||
RetrieveBy Content Verb | The entire hierarchical image (including all child objects), based solely on a subset of non-key values, is retrieved. See "Handling the RetrieveByContent verb". |
|
Multiple results | If more than one object is retrieved from the application, RetrieveByContent should return the first object and use the return code MULTIPLE_HITS. See "Handling the RetrieveByContent verb". |
|
Ignore missing child object | If IgnoreMissingChildObject is set to true in the business object level application-specific information, the connector returns SUCCEED even if not all the children specified in the business object are found in the application. |
|
Update | ||
After-image support | The connector performs all the steps necessary to make the object in the destination application exactly match the business object received in the doVerbFor()call. See "Handling the Update verb". |
|
Delta support | Connector processes exactly the objects and verbs that are received in the source business object. The destination application object is updated only by processing the contents of source business object, not by making the application representation match the source business object. [Not currently an IBM standard.] |
|
KeepRelations | When KeepRelations is specified, child relations are not destroyed in the target application. Otherwise, all the child relations are destroyed first, then the child objects sent in from InterChange Server are created and the relations restored. "Destroyed" means a logical or physical delete of the relation to the child, or, in some cases, deletion of the child itself, depending on the functionality of the connector and application. KeepRelations is set as application-specific information on the child array in the parent object (not as text on the child itself). The syntax should be keeprelations=true. |
|
Verb Support | ||
Subverb support | The connector supports processing of verbs on child objects independent of the verb on the parent object. When a verb is set in a child business object, the connector performs the operation that the child verb indicates, regardless of the verb on the top-level business object. If a verb in a child business object request is not set, the connector can either leave the child verb as NULL, set the child verb to the verb in the top-level business object, or set the value of the verb to the operation that the connector needs to perform. See "Verb stability". |
|
Verb Stability | Verbs in a business object should remain stable throughout the request and response cycle. When a connector receives an business object request, the hierarchical object returned to InterChange Server should have the same verb(s) as the original request, with the exception of verbs that are set on child business objects that were null in the original request |
|