Before you can use the WebSphere® Adapters
nodes, you must set up the IBM® Integration Bus runtime
environment so that you can access the Enterprise Information System
(EIS).
About this task
To enable the WebSphere Adapters
nodes in the IBM Integration Bus runtime environment,
configure the integration node with the location of the EIS provider
JAR files and native libraries. (On Windows, the location of the JAR
files cannot be a mapped network drive on a remote Windows computer; the directory
must be local or on a Storage Area Network (SAN) disk.)
Procedure
- The WebSphere Adapters
nodes require libraries from the EIS vendors. For more information
on how to obtain and use these libraries, see Developing message flows that use WebSphere Adapters.
- Use the following commands to make the JAR files and shared
libraries available to the WebSphere Adapters
nodes.
- To set up the dependencies, use the following command.
mqsichangeproperties integrationNodeName -c EISProviders -o EIS type -n jarsURL -v jar directory
mqsichangeproperties integrationNodeName -c EISProviders -o EIS type -n nativeLibs -v bin directory
For
example:mqsichangeproperties integrationNodeName -c EISProviders -o SAP -n jarsURL -v c:\sapjco\jars
mqsichangeproperties brk6 -c EISProviders -o SAP -n nativeLibs -v c:\sapjco\bin
After
you have run the mqsichangeproperties command,
restart the integration node so that the changes take effect.
- To report the dependencies, use the following command.
mqsireportproperties integrationNodeName -c EISProviders -o EIS type -r
For
example:mqsireportproperties integrationNodeName -c EISProviders -o SAP -r
- On z/OS®, run this command
by customizing and submitting BIPJADPR.
You can also connect to different versions of Siebel
by creating a custom EISProviders configurable service and setting
the location of the appropriate library files. For more information,
see Connecting to different versions of Siebel.
What to do next
When you have set up the environment for the WebSphere Adapters nodes, you can perform
the preparatory tasks that are listed in Developing message flows that use WebSphere Adapters.