The application server provides command-line tools to develop Web services clients and implementations that are based on the Web Services for Java™ Platform, Enterprise Edition (Java EE) specification. You must set up your development environment before you start developing Web services.
You can develop Java artifacts from a Web Services Description (WSDL) file for JAX-RPC applications from a WSDL file by using the WSDL2Java command-line tool to create Java implementation templates and bindings.
You can develop Enterprise JavaBeans™ (EJB) implementation deployment descriptor templates and bindings from a Web Services Description Language (WSDL) file for a JAX-RPC application.
After you have developed the Java artifacts necessary to develop a Java API for XML-based RPC (JAX-RPC) Web service, you must complete the JavaBeans implementation to assemble a Java archive (JAR) file or a Web archive (WAR) file based on your programming model. The resulting JAR file or WAR file contains the JavaBeans implementation and the supported classes created from the tooling.
After you have developed the Java artifacts necessary to develop a Java API for XML-based RPC (JAX-RPC) Web service, you must complete the Enterprise JavaBeans (EJB) implementation to assemble a Java archive (JAR) file or a Web archive (WAR) file based on your programming model. The resulting JAR file or WAR file contains the Enterprise JavaBeans (EJB) implementation and the supported classes created from the tooling.
You can configure the webservices.xml deployment descriptor with an assembly tool.
You can use an assembly tool to configure the webservices.xml deployment descriptor for user-provided handler classes.
Use assembly tools to configure the ibm-webservices-bnd.xml deployment descriptor. This file stores binding information that is associated with the endpoints defined with the webservices.xml deployment descriptor file.