Develop Web services applications from existing WSDL files with enterprise beans
You can develop a new Web service from an existing Web Services Description Language (WSDL) file using a stateless session enterprise bean.
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 you can develop a Web service. You 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
- Set up a Web services development and unmanaged client execution environment. You do not have to set up a development environment if you are using Rational Application Developer.
- Develop implementation templates and bindings from a WSDL file. We need to complete this step to create the deployment descriptor templates that are configured to map the service implementation to the enterprise bean implementation.
- Complete the enterprise bean implementation.
- Configure the webservices.xml deployment descriptor. Configure the ibm-webservices-bnd.xml deployment descriptor so that WAS can process the incoming Web services requests.
- 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.
- Assemble a JAR file that is enabled for Web services from an enterprise bean. You can assemble the artifacts that are required to enable the enterprise beans module for Web services into a JAR file.
- Assemble a Web services-enabled enterprise bean JAR file into an enterprise archive (EAR) file. You can assemble the artifacts that are required to enable the Web services-enabled JAR file into an EAR file.
- Enable the EAR file. When the EAR file contains enterprise bean modules, the EAR file must have the Web services endpoint WAR file added with the endptEnabler command or with an assembly tool before deployment.
- Deploy the EAR file into WAS. You can now deploy the EAR file that has been configured and enabled for Web services.
Results
You have an enterprise beans 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 the appserver.
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 applications onto appservers
Developing Web services applications from enterprise beans
Configure the ibm-webservices-bnd.xmi deployment descriptor
Configure the webservices.xml deployment descriptor
Related Reference
Artifacts used to develop Web services
WSDL2Java command for JAX-RPC applications
Web services specifications and APIs