Starting the connector

A connector must be explicitly started using its connector start-up script. The startup script should reside in the connector's runtime 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 7 shows.

Table 7. Startup scripts for a connector

Operating system Startup script
Windows start_connName.bat
OS/400 start_connName.sh
Linux connector_manager -start connName [-cConfigFile] sets environmental variables and starts the start_connName.sh start-up script automatically. You do not have to run the start-up script manually.

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

Invoking the start-up script on Windows

On Windows platforms, you can invoke the connector start-up script in the
following ways:

Invoking the start-up script on OS/400

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

Note:
To start with TCP/IP servers, use this command: /QIBM/ProdData/WBIServer43/bin/add_autostart_adapter.sh with the following parameters in this order: connName, WebSphereICSName, pathToConnNameStartScript, and jobDescriptionName as explained on the previous page.

Invoking the start-up script on Linux

On Linux platforms, you can invoke the connector start-up script in the following way:

connector_manager -start connName WebSphereICSName [-cConfigFile]

where connName is the name of the connector and WebSphereICSName is WebSphereICS

Copyright IBM Corp. 2004