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 must develop a service endpoint interface if you are developing a JAX-RPC web service from a JavaBeans implementation.
You can develop a service endpoint interface from an Enterprise JavaBeans (EJB) for JAX-RPC web services.
You can develop a Web Services Description Language (WSDL) file to describe the characteristics of your Java API for XML-based RPC (JAX-RPC) web services application including where the service resides and how to invoke the service using an XML format.
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 application 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 application 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.