WebSphere Message Brokers
File: ae37170_
Writer: Karen Cameron Task topic This build: July 31, 2007 21:29:11
Preparing the environment for WebSphere Adapters nodes
Before you can use the WebSphere® Adapters
nodes, you must set up the broker runtime environment so that you can access
the Enterprise Information System (EIS).
To enable the WebSphere Adapters nodes in the
broker runtime environment, configure the broker with the location of the
EIS provider jar files and native libraries.
The WebSphere Adapters nodes need libraries from the EIS vendors.
For more information on how to obtain and use these libraries, see the WebSphere
Adapters documentation [link here to WA ID team's docs, when we have them].
Use one of the following methods to make the jar files and shared
libraries available to the WebSphere Adapters nodes.
Use the mqsicreateconfigurableservice command
to make the jar files and shared libraries available to the WebSphere Adapters
nodes.
To set up the dependencies, use the following commands.
mqsichangeproperties broker name -c EISProviders -o EIS type -n jarsURL -v jar directory
mqsichangeproperties broker name -c EISProviders -o EIS type -n nativeLibs -v bin directory
For example:
mqsichangeproperties brk6 -c EISProviders -o SAP -n jarsURL -v c:\sapjco\jars
mqsichangeproperties brk6 -c EISProviders -o SAP -n nativeLibs -v c:\sapjco\bin
To report the dependencies, use the following command.
mqsireportproperties broker name -c EISProviders -o EIS type -r
For example:
mqsireportproperties brk6 -c EISProviders -o SAP -r
On distributed systems, copy the Java™ .jar files and
native libraries into the broker shared-classes directory; for example, C:\Documents
and Settings\All Users\Application Data\IBM\MQSI\shared-classes on Windows. Copying the files into the shared-classes
directory ensures that the Java class path for the WebSphere Adapters nodes
is set correctly.
On z/OS, no shared-classes directory
is used; instead, perform the following steps:
Specify each Java .jar file in the class path in
the BIPPROF member of the broker’s Partitioned Data Set (PDS).
Update the LIBPATH with any native libraries.
Submit the BIPGEN JCL job to update the broker ENVFILE.