Creating multiple connector instances

Note:
When you create an additional instance of this adapter (or any adapter that is supplied with WebSphere Business Integration Server Express or Express Plus), that instance of the adapter will be counted as a separate adapter by the licensing function that limits the total number of adapters that can be deployed.

You can set your system up to create and run multiple instances of a connector by following the steps below. You must:

Create a new directory

You must create a connector directory for each connector instance. This connector directory is named according to the platform you are using.

Windows systems

The directory must be named ProductDir\connectors\connectorInstance, where connectorInstance uniquely identifies the connector instance.

If the connector has any connector-specific meta-objects, you must create a meta-object for the connector instance. If you save the meta-object as a file, create the ProductDir\repository\connectorInstance directory to store that file.

You can specify the InterChange Server Express server name as a parameter of the startup.bat file. For example:

start_JText.bat connName WebSphereICSName

OS/400 systems

The new directory must be named /QIBM/UserData/WBIServer43/WebSphereICSName/connectors/connectorInstance, where connectorInstance uniquely identifies the connector instance and WebSphereICSName is the name of the InterChange Server Express instance.

If the connector has any specific meta-objects, you must create a meta-object for the connector instance. If you save the meta-object as a file, create the /QIBM/UserData/WBIServer43/WebSphereICSName/repository/connectorInstance directory to store the file.

You can specify the InterChange Server Express server name as a parameter of the start_JText.sh script, as follows:

start_JText.sh connName WebSphereICSName [-cConfigFile]

Linux systems

The new directory must be named ProductDir/connectors/connectorInstance, where connectorInstance uniquely identifies the connector instance.

If the connector has any connector-specific meta-objects, you must create a meta-object for the connector instance. If you save the meta-object as a file, create the ProductDir/repository/connectorInstance directory to store the file.

You can specify the InterChange Server Express server name as a parameter of the connector_manager command, as follows:

connector_manager -start connName WebSphereICSName [-cConfigFile]

Create business object definitions

If the business object definitions for each connector instance do not already exist within the project, you must create them.

  1. If you need to modify business object definitions that are associated with the initial connector, copy the appropriate files and use Business Object Designer Express to import them. You can copy any of the files for the initial connector. Just rename them if you make changes to them.
  2. Files for the initial connector should reside in one of the following directories, depending on your platform

Create a connector definition

You create a configuration file (connector definition) for the connector instance in Connector Configurator Express. To do so:

  1. Copy the initial connector's configuration file (connector definition) and rename it.
  2. Make sure each connector instance correctly lists its supported business objects (and any associated meta-objects).
  3. Customize any connector properties as appropriate.

Create a start-up script

To create a startup script:

  1. Copy the initial connector's startup script and name it to include the name of the connector directory:

    dirname

  2. (Linux systems only) You must change the startup script CONJAR from CONJAR=${CONDIR}/CW${CONNAME}.jar to the following:
    CONJAR=${CONDIR}/CWJText.jar
    
  3. Put this startup script in the connector directory you created in Create a new directory.
  4. (Windows systems only) Create a startup script shortcut.
  5. (Windows systems only) Copy the initial connector's shortcut text and change the name of the initial connector (in the command line) to match the name of the new connector instance.
  6. (OS/400 systems only) Create a job description for the connector using the information below:
    CRTDUPOBJ OBJ(QWBIJTEXTC) FROMLIB(QWBISVR43) 
    OBJTYPE(*JOBD) TOLIB(QWBISVR43) NEWOBJ(newConName)
    

    where newConName is a ten-character name that you use for the job description for the new JText connector.

  7. (OS/400 systems only) Add the new connector to the Console. For more information, refer to the online help provided with the Console.

You can now run both instances of the connector on your integration server at the same time.

Copyright IBM Corp. 2004