Develop new Web services from an existing WSDL file using an EJB implementation

This task explains how to develop a new Web service from an existing Web Services Description Language (WSDL) file using a stateless session enterprise bean.

 

Before you begin

Set up a Web services development and unmanaged client run-time environment.

Locate the Web Services Description Language (WSDL) file that defines the Web service to implement. The SOAP address URI is not required because it is updated when your new implementation is deployed.

 

Overview

This task is one of four ways that one can develop a Web service. We can also develop a Web service from a JavaBeans implementation, develop a Web service from a stateless session enterprise bean, or develop a Web service with an existing WSDL file using a Java bean.

Create the enterprise bean and artifacts that enable the enterprise bean as Web services and assemble those artifacts into the enterprise application:

 

Procedure

  1. Develop implementation templates and bindings from a WSDL file. You need to complete this step to create the deployment descriptor templates that are configured to map the service implementation to the enterprise bean implementation.

  2. Complete the enterprise bean implementation.

  3. Configure the webservices.xml deployment descriptor. Configure the ibm-webservices-bnd.xml deployment descriptor so that WAS can process the incoming Web services requests.

  4. Configure the ibm-webservices-bnd.xmi deployment descriptor. Configure the ibm-webservices-bnd.xml deployment descriptor so that WAS can process the incoming Web services requests.

  5. Assemble a JAR file that is enabled for Web services from an enterprise bean. This article explains how to assemble the artifacts required to enable the EJB module for Web services into the JAR file.

  6. Assemble a Web services-enabled enterprise bean JAR file into an EAR file. This topic explains how to assemble the artifacts required for Web services into to the EAR file

  7. Enable the EAR file. When the EAR file contains EJB modules, the EAR file must have the Web services endpoint WAR file added with the endptEnabler command or with an assembly tool before deployment.

  8. Deploy the EAR file into WebSphere Application Server. This topic presents the steps necessary to deploy the EAR file that has been configured and enabled for Web services.

 

Result

You have an EJB implementation of a Web service that is defined in the WSDL file.

 

What to do next

After you deploy the EAR file, test the Web service to make sure that it works with WebSphere Application Server.

 

See also


Developing EJB implementation templates and bindings from a WSDL file

 

Related Tasks


Completing the EJB implementation
Developing Web services deployment descriptor templates for an EJB implementation
Assembling an enterprise bean JAR file into an EAR file
Assembling a Web services-enabled enterprise bean JAR file from a WSDL file
Enabling an EAR file for Web services
Deploying Web services
Developing a Web service from an enterprise bean
Configuring the ibm-webservices-bnd.xmi deployment descriptor
Configuring the webservices.xml deployment descriptor

 

See Also


Artifacts used to develop Web services
WSDL2Java command