Setting the configuration file properties (WebSphere MQ Integrator Broker)

The topics in this section apply if you are using WebSphere MQ Integrator (also referred to as WMQI) as the integration broker.

When you create and name a new connector configuration file, or when you open an existing connector configuration file, Connector Configurator displays a configuration screen with tabs for the categories of required configuration values.

Connector Configurator requires values for properties in all of these categories:

  1. Standard Properties
  2. Connector-Specific Properties
  3. Supported Business Objects
  4. Trace/Log File values
  5. Data Handlers (where applicable)
Note:
For connectors that use JMS messaging, an additional category may display, for configuration of data handlers that convert the data to business objects. For information about the values to use in the Data Handlers category, see the Connector Development Guide for C++ or the Connector Development Guide for Java.
Important:
Connector Configurator accepts property values in either English or non-English character sets. However, the names of both standard and connector-specific properties, and the names of supported business objects, must use the English character set only.

Standard properties differ from connector-specific properties as follows:

The fields for Standard Properties and Connector-Specific Properties are color-coded to show which are configurable:

Setting standard connector properties

To change the value of a standard property:

  1. Click in the field whose value you want to set.
  2. Either enter a value, or choose from the drop-down menu if one appears.
  3. After entering all values for the standard properties, you can do one of the following:

Setting application-configuration properties

For application-specific configuration properties, you can add or change property names, configure values, delete a property, and encrypt a property:

  1. Click in the field whose name or value you want to set.
  2. Enter a name or value.
  3. To encrypt a property, click the Encrypt box.
  4. Choose to save or discard changes, as described for Setting Standard Connector Properties.

The Update Method displayed for each property indicates whether a component or agent restart is necessary to activatechanged values.

Important:
Changing a preset application-specific connector property name may cause a connector to fail. Certain property names may be needed by the connector to connect to an application or to run properly.

Encryption for connector properties

Application-specific properties can be encrypted by clicking 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 choose OK. If the entered value is correct, the value is decrypted and displays. The adapter guide for each connector contains a list and description of each property and its default value.

Update method

When WebSphere MQ Integrator Broker is the integration broker, connector properties are static. The Update Method is always Agent Restart. In other words, for changes to take effect, you must restart the connector agent after saving the revised connector configuration file.

Specifying supported business object definitions

The procedures in this section assume that you have already created:

The *.set files contain message set IDs that Connector Configurator requires for designating the connector's supported business objects. See the Implementation Guide for WebSphere MQ Integrator Broker for information about creating the MQ message set files.

Each time that you add business object definitions to the system, you must use Connector Configurator to designate those business objects as supported by the connector.

Important:
If the connector requires meta-objects, you must create message set files for each of them and load them into Connector Configurator, in the same manner as for business objects.

To specify supported business objects:

  1. Select the Supported Business Objects tab and choose Load. The Open Message Set ID File(s) dialog displays.
  2. Navigate to the directory where you have placed the message set file for the connector and select the appropriate message set file (*.set) or files.
  3. Choose Open. The Business Object Name field displays the business object names contained in the *.set file; the numeric message set ID for each business object is listed in its corresponding Message Set ID field. Do not change the message set IDs. These names and numeric IDs are saved when you save the configuration file.
  4. When you add business objects to the configuration, you must load their message set files. If you attempt to load a message set that contains a business object name that already exists in the configuration, or if you attempt to load a message set file that contains a duplicate business object name, Connector Configurator detects the duplicate and displays the Load Results dialog. The dialog shows the business object name or names for which there are duplicates. For each duplicate name shown, click in the Message Set ID field, and choose the Message Set ID that you wish to use.

Setting trace/log file values

When you open a connector configuration file or a connector definition file, Connector Configurator uses the logging and tracing values of that file as default values. You can change those values in Connector Configurator.

To change the logging and tracing values:

  1. Choose the Trace/Log Files tab.
  2. For either logging or tracing, you can choose to write messages to one or both of the following:

Configuring data handlers

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. See the descriptions under ContainerManagedEvents in Appendix A, Standard Properties, for values to use for these properties. For additional details, see the Connector Development Guide for C++ or the Connector Development Guide for Java

Copyright IBM Corp. 1997, 2003