+

Search Tips   |   Advanced Search

Configure the ibm-webservices-bnd.xmi deployment descriptor for JAX-RPC web services

Use assembly tools to configure the ibm-webservices-bnd.xml deployment descriptor. This file stores binding information associated with the endpoints defined with the webservices.xml deployment descriptor file.

The ibm-webservices-bnd.xmi deployment descriptor is for JAX-RPC based web services application. It is not used for JAX-WS enabled applications.

To configure the client deployment descriptor, read about the configuring the client deployment descriptor in the Rational Application Developer information.

Before we can configure the ibm-webservices-bnd.xml deployment descriptor, we must develop the deployment descriptor templates and complete the implementation.

This task is one of the steps in developing a web service. We configure the deployment descriptors so that WebSphere Application Server can process the incoming web services requests.

Depending on if we are developing a web service from JavaBeans or an enterprise bean:

Then, complete the EJB implementation or complete the JavaBeans implementation. When the EJB implementation is complete, the enterprise bean Java archive (JAR) file is assembled. When the JavaBeans implementation is complete, the web module web application archive (WAR) file is assembled. These archive files contain the webservices.xml deployment descriptor. The archive files must be assembled before we can configure the webservices.xml deployment descriptor.

Configure the webservices.xml deployment descriptor by following the steps provided in this task section.


Tasks

  1. Start an assembly tool. Read about starting the assembly tool in the Rational Application Developer information.

  2. If we have not done so already, configure the assembly tool so that it works on Java EE modules. We need to make sure that the Java EE and Web categories are enabled. Read about configuring the assembly tool in the Rational Application Developer information.
  3. Migrate JAR files created with the Assembly Toolkit, Application Assembly Tool or a different tool to the Rational Application Developer assembly tool. To migrate files, import your JAR files to the assembly tool. Read about migrating code artifacts to an assembly tool in the Rational Application Developer information.

  4. Configure the client deployment descriptor. Read about the configuring the client deployment descriptor in the Rational Application Developer information.

The ibm-webservices-bnd.xmi deployment descriptor is configured for the web service implementation module.


What to do next

If we are developing a web service from JavaBeans, assemble a WAR file enabled for web services from Java code. See the assembling a WAR file enabled for web services from Java code information.

If we are developing a web service from an enterprise bean, assemble a JAR file enabled for web services from an enterprise bean. To learn more about assembling the artifacts required to enable the EJB module for web services into the JAR file, see the assembling a JAR file enabled for web services from an enterprise bean information.


Subtopics


Related:

  • Development and assembly tools
  • Configure the webservices.xml deployment descriptor for JAX-RPC web services
  • Assembling a JAR file enabled for web services from an enterprise bean
  • Assembling a web services-enabled enterprise bean JAR file from a WSDL file
  • Assembling a WAR file enabled for web services from Java code
  • Assembling a web services-enabled WAR file from a WSDL file
  • Developing JAX-RPC web services deployment descriptor templates for a JavaBeans implementation
  • Developing JAX-RPC web services deployment descriptor templates for an enterprise bean implementation