In addition to copying the ns.jar from the WebSphere
server to the machine where JMSAdmin is run, the following steps must be
performed. Copy the files mentioned below must from a WebSphere
Application Server installation on Solaris.
- Create a new directory under the Sun JDK™ called ibm_bin.
- Copy all the files from the $WSAS_HOME/java/ibm_bin directory to the
new $Sun_JDK/ibm_bin directory.
- Create a new directory under the Sun JDK called ibm_lib.
- Copy the following files from $WSAS_HOME/java/ibm_lib directory to the
Sun_JDK/ibm_lib directory:
- Copy all the files from the $WSAS_HOME/java/jre/lib/ext directory to
the $Sun_JDK/jre/lib/ext directory.
- Copy the $WSAS_HOME/java/jre/lib/orb.properties to the
$Sun_JDK/jre/lib/ directory.
- Copy the following files from the $WSAS_HOME/java/jre/lib/sparc
directory to the $Sun_JDK/jre/lib/sparc directory:
- Copy the following files from $WSAS_HOME/java/lib directory to
$Sun_JDK/lib/ directory.
- ibmtools.jari
- ir.idl
- orb.idl
- Copy the file $WSAS_HOME/java/jre/lib/security/java.security to the
$Sun_JDK/jre/lib/security directory.
- Ensure that you maintain all of the same access rights.
After you complete these steps, the JMSAdmin tool is able to connect to
the WebSphere namespace successfully.
|