Develop a new Web service from an existing WSDL file using a stateless session enterprise beanSet up a Web services development and unmanaged client execution 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.
Create the enterprise bean and artifacts that enable the enterprise bean to be a Web service and assemble those artifacts into the enterprise application as follows:
- Develop implementation templates and bindings from a WSDL file.
- Complete the enterprise bean implementation.
- Assemble a Web services-enabled enterprise EJB JAR file.
- Configure the webservices.xml deployment descriptor.
- Configure the ibm-webservices-bnd.xmi deployment descriptor.
- Assemble a Web services-enabled EJB JAR into an EAR file.
- Enable the EAR file. When the EAR file contains EJB modules, it must have the Web services endpoint Web archive (WAR) file added with the endptEnabler command or Assembly Toolkit before deployment.
- Deploy the EAR file into WAS.
An EJB implementation of a Web service defined in the WSDL file.
See AlsoCompleting the EJB implementation
Developing Web services deployment descriptor templates for an EJB implementation
Assembling a Web services-enabled EJB JAR into an EAR file
Assembling Web services-enabled EJB JAR file when starting from WSDL
Enabling a Web services-enabled EAR file
Deploying Web services based on Web Services for J2EE
Developing a Web service using a stateless session enterprise bean
Configuring the ibm-webservices-bnd.xmi deployment descriptor
Configuring the webservices.xml deployment descriptor
Artifacts used to develop Web services based on Web Services for J2EE