For Web services deployed with Java bindings (or EJB bindings even
where the Web service is on a different server) you must make additional classes
available to the gateway.
Why and when to perform this task
For EJB bindings,
make the EJB client JAR file available. If the Web service is deployed on
the same server as the gateway, the necessary interfaces and classes are already
visible. If not, implement one of the following options:
- Copy the EJB client JAR file into the install_root/lib or install_root/lib/app directory,
where install_root is the root directory for your installation
of IBM WebSphere Application Server (by default WebSphere/AppServer).
- Update the application server class path to include the EJB client JAR
file.
For Java bindings, make the Java classes for the Web service
available by implementing one of the following options:
- Copy the JAR file or class files that contain the Java classes into the install_root/lib or install_root/lib/app directory.
- Update the application server class path to include the JAR file.
- Wrap the Java classes in an enterprise bean and deploy it on the same
application server. WebSphere Application Server then makes the classes available
to the gateway application.