Configuring the connector

Connectors have two types of configuration properties: standard configuration properties and connector-specific configuration properties. You must set the values of these properties before running the connector. As you enter the configuration values, they are saved in the repository.

To configure connector properties, use one of the following tools:

A connector obtains its configuration values at startup. During a run-time session, you may want to change the values of one or more connector properties. Changes to some connector configuration properties, such as AgentTraceLevel, are dynamic, taking effect immediately. Changes to other connector properties are static, requiring component restart or system restart after a change. To determine whether a property is dynamic or static, refer to the update method column in Connector Designer.

Standard connector properties

Standard configuration properties provide information that all connectors use. For detailed information about these properties, see Appendix A, "Standard configuration properties for connectors".

Note:
Because the connector for i2 supports the InterChange Server, WebSphere MQ Integrator, and WebSphere Application Server integration brokers, configuration properties for all three brokers are relevant to the connector.

In addition, the following supplemental information on standard connector properties applies to i2.

LogAtInterchangeEnd

Tells whether to log errors on the InterChange Server (ICS).

The default value is false.

MessageFileName

Path of the error message file if it is not located in the standard message location %ProductDir%\connectors\messages. If the message file name is not in a fully qualified path, the message file is assumed to be located in the directory specified by the HOME environment variable or the startup parameter user.home. If a connector message file does not exist, the WBIA API message file is used. If that file does not exist, the InterchangeSystem.txt file is used as the message file.

The default value is i2Adapter.txt.

Connector-specific properties

Connector-specific configuration properties provide information needed by the connector at run time. They also provide a way of changing static information or logic within the connector without having to recode and rebuild it.

The following table lists the connector-specific configuration properties for the connector along with their descriptions and possible values.

Property Description Possible values
ApplicationName Unique name specified for each connector i2 adapter
ApplicationUserName User name for the i2 connection used for authentication i2User
ApplicationPassword Password for the i2 connection used for authentication i2Password
CISAgentHostName Name used when the CIS agent is running on a remote machine. If it is not set, the current local host is assumed to have the CIS agent running. If it is set, the i2 connector establishes a connection with this remote host. String host name

Example: any machine name like California

ExecutionTimeout Time in milliseconds before the call to i2 application terminates. Default is 30000
EventSubscriptionConnectionId Default connectionId to be used for request processing EventConn1
InteractionResolutionAttempts Number of times that an interaction should be attempted to be resolved Default is 2
PollQuantity Number of messages that will be retrieved from the client queue while polling for each registered operation; it will be pollQuantity multiplied by the number of registered operations. Default is 1
UseDefaults Value that the connector checks for to identify the default value of the attributes during request processing. This is not used by the i2 connector. Not required for this connector

Configuring start_i2.bat (for Windows) or start_i2.sh (for UNIX)

You need to add the proper path to the start files for CIS-SDK and j2ee.jar.

Example: The following path information needs to be added to the start_i2.bat file. These are just examples. You should change the path information depending on your local installation.

set I2_CIS_HOME_DIR=C:\i2\CIS\6.0.1\cis-sdk
 set J2EE_PATH=C:\J2EE_JAR
 set i2PROPERTIES="%i2_CIS_HOME_DIR%"\properties;
 

(The last line refers to the contents of the "properties" directory of your i2 CIS.)

Note:
If your CIS agent is configured for guaranteed messaging and an adapter uses MQ Bindings, you will need to have the ".bindings" file in the same relative path as your i2 CIS install. This is the jndiProviderURL attribute of your MQ Binding configuration element.

Configuring the data handler

You also need to configure the data handler. Set the following values for the child business object text/xml in MO_DataHandler_Default:

Validation false
ClassName com.crossworlds.DataHandlers.text.xml
UseNewLine false
InitialBufferSize any appropriate value like 2097152
DummyKey 1
Note:
The rest of the fields should be blank.

For detailed information about data handler configuration, see the Data Handler Guide.

Copyright IBM Corp. 1997, 2003