Previous Topic: Use a Handler Chain to Invoke the SOA Agent for HTTP Requests

Next Topic: Configure Policies for the SOA Agent

Use a Handler Chain to Invoke the SOA Agent for JMS Requests

To configure services implemented as JWS files to invoke the SOA Agent for requests received over JMS transport, define the SOA Agent JAX-RPC Handler class in a handler chain configuration file.

To use a handler chain to invoke the SOA Agent for a JWS web service for JMS requests

  1. Create a handler chain configuration file that defines a JAX-RPC handler chain. The chain can include as many handler classes as you require but must define the SOA Agent JAX-RPC Handler class first.

    Example HandlerConfig.xml:

    <jwshc:handler-config xmlns:jwshc="http://www.bea.com/xml/ns/jws"
     xmlns:soap1="http://HandlerInfo.org/Server1"
     xmlns:soap2="http://HandlerInfo.org/Server2"
     xmlns="http://java.sun.com/xml/ns/j2ee" >
      <jwshc:handler-chain>
       <jwshc:handler-chain-name>HandlerChainName</jwshc:handler-chain-name>
       <jwshc:handler>
    	  <handler-name>handlerOne</handler-name>
    	  <handler-class>
    	    com.ca.soa.agent.appserver.jaxrpc.jms.XMLAgentJMSJaxrpcHandlerProxy
    	  </handler-class>
    	</jwshc:handler>
      </jwshc:handler-chain>
    </jwshc:handler-config>
    
    HandlerChainName

    Specifies the name of handler chain.

  2. Add the JWS annotation @HandlerChain(file="HandlerConfig.xml", name="HandlerChainName") to the web service JWS file.
  3. Rebuild the JWS web service.

WebLogic server will invoke SOA Agent JAX-RPC handler for JMS requests.

Note: For more information on SOAP message handlers and handler chains, see the WebLogic documentation.