WAS v8.5 > Administer applications and their environment > Administer web services - Bus enabled web services > Enable web services through the service integration bus > Administer the bus-enabled web services resources > Work with JAX-RPC handlers and clients

Create a new JAX-RPC handler configuration

Create a JAX-RPC handler configuration for use, as part of a handler list, with service integration bus-deployed web services. Handlers monitor messages at ports, and take appropriate action depending upon the sender and content of each message.

This task assumes that we have already created your handler. We can do this using IBM Rational Application Developer or a similar tool. For more information, see the IBM developerWorks article Support for J2EE Web Services in WebSphere Studio Application Developer V5.1 -- Part 3: JAX-RPC Handlers.

You must also make the handler class available to the server that hosts the port for the service to monitor, as detailed in Loading JAX-RPC handler classes. A Java API for XML-based remote procedure calls (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. To make WAS aware of your handler, and to make the handler available for inclusion in one or more handler lists, we use the dmgr console to create a new handler configuration.

  1. In the navigation pane, click Service integration -> Web services -> JAX-RPC Handlers. The JAX-RPC handlers collection form is displayed.

  2. Click New. The JAX-RPC handlers settings form is displayed.

  3. Type the following general properties:

    Name

    Type the name by which the handler is known.

    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: \ / , # $ @ : ; " * ? < > | = + & % '

    For example TestHandler.

    Description

    Type the (optional) description of the handler.

    Class name

    Type the name of the class that is to be instantiated. For example com.ibm.jaxrpc.handler.TestHandler.

    We can configure multiple instances of a handler by creating each instance with a different handler name, and pointing to the same handler class.

  4. Click OK. The general properties for this item are saved, and the additional properties options are made available.

  5. Type the following additional properties:

    SOAP roles

    Add SOAP actor definitions to the list of SOAP roles in which this handler acts. For more information, see the SOAP specification.

    JAX-RPC headers

    Add JAX-RPC header definitions (Namespace URI and Local part) to 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 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. Save your changes to the master configuration.


Results

If the processing completes successfully, the list of handlers is updated to include the new handler. Otherwise, an error message is displayed.

To use this handler, add it to a handler list as described in Create a new JAX-RPC handler list or Modify an existing JAX-RPC handler list.


Subtopics


Related concepts:

Service integration technologies and JAX-RPC handlers


Reference:

Implement JAX-RPC handlers to access SDO messages

JAX-RPC: Core web services API in the Java platform

Get Started with JAX-RPC

A developer introduction to JAX-RPC, Part 2: Mine the JAX-RPC specification to improve web service interoperability

Support for J2EE Web Services in WebSphere Studio Application Developer V5.1 -- Part 3: JAX-RPC Handlers


Related information:

Create a new JAX-RPC handler list
Sending web service messages directly over the bus from a JAX-RPC client


+

Search Tips   |   Advanced Search