Starting the connector

Important:
As noted earlier in this chapter, the connector, business objects, the SOAP data handler meta-objects, and collaborations must be configured after installation and before starting the connector to assure proper operation. For a summary of these tasks, see Overview of configuration tasks. In addition, connector polling should not be disabled (connector polling is enabled by default).

A connector must be explicitly started using its connector start-up script. The startup script should reside in the connector's run-time directory. For example, for Windows, use:

ProductDir\connectors\connName

where connName identifies the connector. The name of the startup script depends on the operating-system platform, as Table 4 shows.

Table 4. Startup scripts for a connector

Operating system Startup script
Windows start_connName.bat
OS/400 start_connName.sh
Linux Before executing the startup script you must set environmental variables. The following command will set these variables and run the startup script start_connName.sh automatically:
connector_manager -start connName
WebSphereICSName [-cConfigFile ]

For more information on how to start a connector, including the command line start-up options, see the System Administration Guide.

Invoking the startup script on Windows

On Windows platforms, you can invoke the connector startup script in the following ways:

Invoking the startup script on OS/400

On OS/400 platforms, you can invoke the connector startup script in the following ways:

Note:
To start with TCP/IP servers, use the command:
/QIBM/ProdData/WBIServer43/bin/add_autostart_adapter.sh 
connName WebSphereICSName pathToConnNameStartScript 
jobDescriptionName

where connName is the name of your connector, WebSphereICSName is the name of the InterChange Server Express instance, pathToConnNameStartScript is the full path to the connector start script, and jobDescriptionName is the name of the job description for the adapter.

Invoking the startup script on Linux

On Linux platforms, you can invoke the connector startup script in the following way:

Copyright IBM Corp. 2004