Installation Guides › SOA Agent for IBM WebSphere Guide › Final Steps › Edit Deployment Descriptors of JAX-RPC Applications

Edit Deployment Descriptors of JAX-RPC Applications

To protect a JAX-RPC web service you must edit its deployment descriptor to add the SOA Agent JAX-RPC Handler.

To edit a JAX-RPC web service deployment descriptor

1. Unpack the enterprise archive (EAR) containing one or more web services.
2. Examine the EAR to determine which of the modules within it contains a JAX-RPC web service.(A module that contains a JAX-RPC web service if it has a webservices.xml file in the META-INF folder for EJB endpoints, or the WEB-INF folder for servlet endpoints.)
3. For each module in the EAR identified as a JAX-RPC web service:
   1. Unpack the archive containing the module. (The archive will be a JAR file for EJB endpoints and a WAR file for servlet endpoints.)
   2. Find the webservices.xml file.
   3. For each port-component element found in the webservices.xml file, add a handler element:

      <handler>
         <handler-name>SOA Agent Handler</handler-name>
         <handler-class>
            com.ca.soa.agent appserver.jaxrpc.XMLgentJaxrpcHandler
         </handler-class>
      </handler>
      

      Note: The SOA Agent JAX-RPC handler must always be invoked first; If other handler elements are already present or subsequently added to the webservices.xml file, the SOA Agent JAX-RPC Handler element must placed before them.

4. Repackage the module into the appropriate archive type (JAR or WAR).
5. When all modules have been configured, repackage the EAR.
6. Install or update the enterprise application.