Use the Supported Business Objects tab in Connector Configurator Express to specify the business objects that the connector will use. You must specify both generic business object definitions and application-specific business object definitions, and you must specify associations for the maps between the business objects.
For you to specify a supported business object, the business objects and their maps must exist in the system. Business object definitions, including those for data handler meta-objects, and map definitions should be saved into ICL projects. For further information on ICL projects, see User Guide for WebSphere Business Integration Express for Item Synchronization
To specify that a business object definition is supported by the connector, or to change the support settings for an existing business object definition, click the Supported Business Objects tab and use the following fields.
To designate that a business object definition is supported by the connector, with System Manager running:
To delete a business object from the supported list:
Deleting a business object from the supported list changes the connector definition and makes the deleted business object unavailable for use in this implementation of this connector. It does not affect the connector code, nor does it remove the business object definition itself from System Manager.
If a business object has Agent Support, the system will attempt to use that business object for delivering data to an application via the connector. Typically, application-specific business objects for a connector are supported by that connector's agent, but generic business objects are not.
To indicate that the business object is supported by the connector agent, check the Agent Support box. The Connector Configurator Express window does not validate your Agent Support selections.
The maximum transaction level for a connector is the highest transaction level that the connector supports.
For most connectors, Best Effort is the only possible choice, because most application APIs do not support the Stringent level.
You must restart the server for changes in transaction level to take effect.