WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Modifying an existing JAX-RPC handler configuration

Use this task to modify the configuration details for a Java API for XML-based Remote Procedure Call (JAX-RPC) handler that has been configured for use (as part of a handler list) with service integration bus-deployed Web services.

If you add or change a handler class, make the class available to the application server in one of the following ways:
  • Copy the 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.
When you add or change a handler class, 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.

If you modify a handler class but do not change the class name, you do not need to modify the handler configuration as described in this topic. You just need to stop then restart the application server on which the gateway is running.

To list the handlers, and to view and modify their configuration details, complete the following steps:
  1. Start the administrative console.
  2. In the navigation pane, click Service integration > Web services > JAX-RPC handlers. A list of handlers is displayed in a JAX-RPC handlers collection form.
  3. Click the name of a handler in the list. The current JAX-RPC handlers settings for this handler are displayed.
  4. Modify the following general properties:
    Name
    Modify the name of the handler. This name must be unique, and it must obey the following syntax rules:
    • It must not start with "." (a period).
    • It must not start or end with a space.
    • It must not contain any of the following characters: \ / , # $ @ : ; " * ? < > | = + & % '
    Note: When you change a handler name, the system looks up all objects that refer to it and updates the name.
    Description
    Modify the (optional) description of the handler.
    Class name
    Modify the name of the class that is to be instantiated. You must also make this class available to the application server as detailed in Creating a new JAX-RPC handler configuration.
  5. Modify the following additional properties:
    SOAP roles
    Add, modify or remove SOAP actor definitions from the list of SOAP roles in which this handler acts. For more information, see the SOAP specification.
    JAX-RPC headers
    Add, modify or remove JAX-RPC header definitions (Namespace URI and Local part) from the list of JAX-RPC headers against which this handler operates. JAX-RPC headers are SOAP headers that are processed by a JAX-RPC handler.
    Custom properties
    Add, modify or remove custom properties (name/value pairs, where the name is a property key and the value is a string value that can be used to set internal system configuration properties).
  6. Apply the changes.
If the processing completes successfully, the list of handlers is redisplayed. Otherwise, an error message is displayed.
Related concepts
Service integration technologies and JAX-RPC handlers

Task topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tjw_jaxrpc_handler_config.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)