If you are running Clarify 12.0 on a Solaris or HP UX platform, you
must complete the following steps before you start the connector:
- Set the Library Path (LD_LIBRARY_PATH/SHLIB_PATH) to the <Clarify
Install>db_admin directory.
- Change the ORACLE_HOME variable in
<AdapterFramework>/connectors/Clarify/start_Clarify.sh to the
root directory where Oracle is installed.
- Copy clarify.env from <Clarify Install>/db_admin to the
location from which you are starting the connector.
- Note:
- If you see the following error message: Unable to load PPOMS
Library: : 'Orappoms.DLL'. (0x60004c),
check the LD_LIBRARY_PATH to ensure that the following files are
included:
- libOrappoms.sl (.so)
- libclcrt.sl (.so)
- libclutils.sl (.so)
- libkosapi.sl (.so)
A connector must be explicitly started using its connector start-up
script. The startup script should reside in the connector's
runtime directory:
ProductDir\connectors\connName
where connName identifies the connector. The name of
the startup script depends on the operating-system platform, as Table 5 shows.
Table 5. Startup scripts for a connector
Operating system
| Startup script
|
UNIX-based systems
| connector_manager_connName
|
Windows
| start_connName.bat
|
You can invoke the connector startup script in any of the following
ways:
- On Windows systems, from the Start menu
Select Programs>IBM WebSphere Business Integration
Adapters>Adapters>Connectors. By default, the program name
is "IBM WebSphere Business Integration Adapters". However, it
can be customized. Alternatively, you can create a desktop shortcut to
your connector.
- From the command line
where connName is the name of the connector and
brokerName identifies your integration broker, as follows:
- For WebSphere InterChange Server, specify for brokerName the
name of the ICS instance.
- For WebSphere message brokers (WebSphere MQ Integrator, WebSphere MQ
Integrator Broker, or WebSphere Business Integration Message Broker) or
WebSphere Application Server, specify for brokerName a string that
identifies the broker.
- Note:
- For a WebSphere message broker or WebSphere Application Server on a Windows
system, you must include the -c option followed by the
name of the connector configuration file. For ICS, the -c is
optional.
- From Adapter Monitor (WebSphere Business Integration Adapters product
only), which is launched when you start System Manager
You can load, activate, deactivate, pause, shutdown or delete a connector
using this tool.
- From System Monitor (WebSphere InterChange Server product only)
You can load, activate, deactivate, pause, shutdown or delete a connector
using this tool.
- On Windows systems, you can configure the connector to start as a Windows
service. In this case, the connector starts when the Windows system
boots (for an Auto service) or when you start the service through the Windows
Services window (for a Manual service).
For more information on how to start a connector, including the
command-line startup options, refer to one of the following documents:
- For WebSphere InterChange Server, refer to the System Administration
Guide.
- For WebSphere message brokers, refer to Implementing Adapters with
WebSphere Message Brokers.
- For WebSphere Application Server, refer to Implementing Adapters with
WebSphere Application Server.
