Starting the connector

A connector must be explicitly started using its connector startup script. The startup script should reside in the connector's runtime directory. For example, on a Windows system, the startup script resides in the ProductDir\connectors\connName directory, where connName identifies the connector.

The name of the startup script depends on the operating-system platform, as Table 8 shows.

Table 8. Startup scripts for a connector

Operating system Startup script
Windows start_connName.bat
OS/400 start_connName.sh
Linux start_connName.sh
Note:
You do not have to run the start_connName.sh startup script manually. Instead, use the following command to set required environment variables and invoke the startup script automatically:
connector_manager -start connName 
[-cConfigFile]

Invoking the startup script on Windows systems

You can invoke the connector startup script in the following ways:

Invoking the startup script on OS/400 systems

You can invoke the connector startup script in the following ways:

Note:
To start the connector with automatically started TCP/IP servers on OS/400 systems, use the following script:
/QIBM/ProdData/WBIServer43/bin/add_autostart_adapter.sh connName
 WebSphereICSName pathToConnNameStartScript jobDescriptionName

where connName is the name of the connector, WebSphereICSName is the name of the InterChange Server Express instance, pathToConnNameStartScript is the full path to the connector startup script, and jobDescription Name is the name of the job description to use in the QWBISVR43 library.

Invoking the startup script on Linux systems

You can invoke the connector startup script on a Linux system by entering the following command:

connector_manager -start connName WebSphereICSName [-cConfigFile]

where connName is the name of the connector and WebSphereICSName is the name of the InterChange Server Express instance (by default, WebSphereICS).

Copyright IBM Corp. 2004