WebSphere Business Integration Adapters: An Adapter Development and WebSphere Business Integration Solution

Chapter 10. Local versus remote deployment 153

ConnectorBatchFile Is set to the path and name of the batch file that starts

the connector (for example:

C:\IBM\WebSphereAdapters\connectors\JDBC\start_s

ervice_JDBC.bat).

ConnectorName Is set to the name of the connector (for example,

JDBCConnector).

InterChangeServer Is the name of the InterChange Server instance with

which the connectors communicate if InterChange

Server is the broker. If you are using a broker other

than InterChange Server, specify a placeholder value

such as WMQI or WAS.

ThreadMode Is set to MULTI_THREADED or SINGLE_THREADED.

The command creates a Windows service named CWInterchange

ConnectorName, where ConnectorName is the value that you specified for the

ConnectorName parameter when executing the command.

10.2.2 Configuring startup in a UNIX environment

In UNIX environments, you should create a startup script that contains the

commands that are needed to initiate the adapter. This script should be included

in the system startup routines so that the adapter gets started when the system

starts.

10.3 Remote deployment

Even though the local installation might be the most desirable choice for the

installation, sometimes installing the adapter to another platform might be

required, as discussed in 10.1, “Overview of adapter deployment” on page 150.

When installing an adapter to a remote platform, you should consider the

following:

1. Make sure that the platform requirements are fulfilled, such as installing

adapter locally and installing the MQClient (see 10.2, “Local deployment” on

page 151). Make sure that the Java Messaging feature is installed with the

MQClient installation.

154 WebSphere Business Integration Adapters

2. You have to install the WebSphere Business Integration Adapter Framework

regardless which broker you are using. The installation differs depending on

the broker:

– If your integration broker is WebSphere Application Server or one of the

supported messaging brokers, do the following:

i. Install the Adapter Framework as described in the Installation Guide for

WebSphere Business Integration Adapters. Read the “Installing and

configuring the connector” chapter in the guide for each adapter that

you plan to install in the environment and determine any data handler

requirements for the environment.

ii. Install each data handler that is required for the environment and each

adapter that is required, as described in the Installation Guide for

WebSphere Business Integration Adapters.

– If your integration broker is WebSphere InterChange Server, do the

following:

i. Run the installer for WebSphere InterChange Server on the distributed

computer to install the proper version of the Adapter Framework on it.

When the InterChange Server Configuration Wizard opens, specify the

same configuration values as those specified when installing

InterChange Server on the broker host computer. For more information

about installing WebSphere InterChange Server, see the System

Installation Guide for Windows or UNIX. Note that you should not start

this instance of InterChange Server. You are only installing it to install a

compatible version of the Adapter Framework on the adapter host

computer.

ii. Apply any patches that have been applied to the InterChange Server

host computer to the distributed computer so that the broker and

adapter environments are running at the same patch level.

iii. Install the adapter as described in the Installation Guide for

WebSphere Business Integration Adapters. At the IBM WebSphere

InterChange Server window, specify the name of the InterChange

Server instance on the broker host computer, rather than the name of

the InterChange Server instance that you installed on the adapter host

computer (on which you had to install to install the Adapter

Framework).

iv. Import the connector definition that was created in the repository

directory into your development environment, as described in the

Implementation Guide for WebSphere InterChange Server.

v. Configure the connector as described in the guide for the adapter.