The fields for Standard Properties and Connector-Specific Properties are color-coded to show which are configurable:
To change the value of a standard property:
For connector-specific configuration properties, you can add or change property names, configure values, delete a property, and encrypt a property. The default property length is 255 characters.
The Update Method displayed for each property indicates whether a component or agent restart is necessary to activate changed values. For further information, see User Guide for WebSphere Business Integration Express for Item Synchronization
Connector-specific properties can be encrypted by selecting the Encrypt check box in the Edit Property window. To decrypt a value, click to clear the Encrypt check box, enter the correct value in the Verification dialog box, and click OK. If the entered value is correct, the value is decrypted and displays.
The adapter user guide for each connector contains a list and description of each property and its default value.
If a property has multiple values, the Encrypt check box will appear for the first value of the property. When you select Encrypt, all values of the property will be encrypted. To decrypt multiple values of a property, click to clear the Encrypt check box for the first value of the property, and then enter the new value in the Verification dialog box. If the input value is a match, all multiple values will decrypt.
Connector properties are almost all static and the Update Method is Component restart. For changes to take effect, you must restart the connector after saving the revised connector configuration file. For further information, see User Guide for WebSphere Business Integration Express for Item Synchronization.
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.
Each connector supports a list of business object definitions and their associated maps that are currently active in WebSphere InterChange Server. This list appears when you select the Associated Maps tab.
The list of business objects contains the application-specific business object which the connector supports and the corresponding generic object that the controller sends to the subscribing collaboration. The association of a map determines which map will be used to transform the application-specific business object to the generic business object or the generic business object to the application-specific business object.
If you are using maps that are defined for specific source and destination business objects, the maps will already be associated with their business objects when you open the display, and you will not need to change them.
If more than one map is available for use by a supported business object, you will need to explicitly bind the business object with the map that it should use.
The Associated Maps tab displays the following fields:
These are the application-specific and generic business objects supported by this connector, as designated in the Supported Business Objects tab. If you designate additional business objects under the Supported Business Objects tab, they will be reflected in this list after you save the changes by choosing Save to Project from the File menu of the Connector Configurator Express window.
The display shows all the maps that have been installed to the system for use with the supported business objects of the connector. The source business object for each map is shown to the left of the map name, in the Business Object Name display. To display the maps, you must first designate the supported business objects, and then save the connector configuration to project. To see the maps, you must first designate the supported business objects and save the connector configuration to project.
In some cases, you may need to explicitly bind an associated map.
Explicit binding is required only when more than one map exists for a particular supported business object. When InterChange Server Express boots, it tries to automatically bind a map to each supported business object for each connector. If more than one map takes as its input the same business object, the server attempts to locate and bind one map that is the superset of the others.
If there is no map that is the superset of the others, the server will not be able to bind the business object to a single map, and you will need to set the binding explicitly.
To explicitly bind a map:
The messaging properties are available only if you have set MQ as the value of the DeliveryTransport. These properties affect how your connector will use queues.
When you open a connector configuration file, Connector Configurator Express uses the logging and tracing values of that file as default values. You can change those values in Connector Configurator Express.
To change the logging and tracing values:
The data handlers section is available for configuration only if you have designated a value of JMS for DeliveryTransport and a value of JMS for ContainerManagedEvents. Adapters that make use of the guaranteed event delivery enable this tab.
See the descriptions under ContainerManagedEvents in the Standard Properties appendix for values to use for these properties.