Before you begin
Before you can work with your Java API for XML-based Remote Procedure
Call (JAX-RPC) handlers, you must complete the following steps:
- Make the handler classes available to the application server in one of
the following ways:
- Copy each individual class file into a directory structure under install_root/classes that
matches the package name of the class, where install_root is
the
root directory for the installation of IBM WebSphere Application Server.
Therefore a handler class com.ibm.jaxrpc.handler.TestHandler is
copied into the install_root/classes/com/ibm/jaxrpc/handler directory.
- Package the class files for all your handlers as a JAR file, then copy
it into install_root/lib/app.
- Stop then restart the application server.
Note: When you add or change a handler class in the install_root/classes directory,
you make the handler class potentially available to all application servers
on the node. New or changed handler classes are then picked up by each individual
application server within the node when you restart that server.
Why and when to perform this task
A Java API for XML-based remote procedure call (JAX-RPC) handler
is a Java class that performs a range of handling tasks - for example logging
messages, or transforming their contents, or terminating an incoming request.
For more detailed information about JAX-RPC and JAX-RPC handlers, see the
IBM developerWorks article Support for J2EE Web Services in WebSphere
Studio Application Developer V5.1 -- Part 3: JAX-RPC Handlers.
To
enable JAX-RPC handlers to perform more complex operations, you chain them
together into handler lists. You can then associate each JAX-RPC handler list
with one or more ports, so that the handler list can monitor activity at the
port, and take appropriate action depending upon the sender and content of
each message that passes through the port.
From the administrative console,
you can complete the following service integration tasks for JAX-RPC handlers
and handler lists: