Assembling web services applications
We can assemble Java-based web services applications using assembly tools.
We can assemble Java-based web services modules with assembly tools provided with the application server.
After developing a web service application, we are now ready to assemble the application. Assembling a web service application consists of creating the Java EE modules that we can deploy onto application servers. The modules are created from code artifacts such as WAR files for JavaBeans applications or enterprise beans Java archive (JAR) files for enterprise beans applications. This packaging and configuring of code artifacts into enterprise application modules (EAR files) or standalone web modules is necessary for deploying the modules onto an application server.
Tasks
- Start an assembly tool. Read about starting the assembly tool in the Rational Application Developer documentation.
- Assemble the web services enabled bean into the appropriate module.
- For JavaBeans enabled as web services:
- Assembling a WAR file enabled for web services from Java code.
- Assembling a web services-enabled WAR file from a WSDL file.
- For enterprise beans enabled as web services:
- Assembling a JAR file enabled for web services from an enterprise bean.
- Assembling a web services-enabled enterprise bean JAR file from a WSDL file.
This product supports packaging enterprise beans in WAR files. If we include a web services-enabled enterprise bean JAR file into a WAR file, we must merge any information in the webservices.xml deployment descriptor files in the JAR files into the webservices.xml deployment descriptor in the WEB-INF directory of the WAR file. To learn more, see the EJB content in WAR modules information.
When developing faults for a JAX-WS application, it is a best practice to always include the fault bean generated by the JAX-WS tooling in the packaging of our JAX-WS application. However if the application does not use the fault bean classes generated by the JAX-WS tooling (that is, we use a bottom-up development approach starting from Java and we choose not to package the fault bean classes), the application server runtime environment dynamically generates the fault beans. Even so, it is a best practice to always package the fault bean.bprac
- Assemble the web services enabled module into an EAR file.
- Assembling a web services-enabled WAR into an EAR file.
- Assembling an enterprise bean JAR file into an EAR file.
- Enable the EAR file for EJB modules that contain web services. When the EAR file contains EJB modules that contain web services, run the endptEnabler command-line tool or an assembly tool before deployment to produce a web services endpoint WAR file. This tool is also used to specify whether the web services are exposed using SOAP over Java Message Service (JMS) or SOAP over HTTP.
- Assemble a web services-enabled WAR file into an EAR file.
We have a web services-enabled EAR file that we can deploy onto the application server.
What to do next
Now we need to deploy the web services-enabled EAR file onto the application server. To learn more, read about deploying web services applications onto application servers
Subtopics
- Assembling a JAR file enabled for web services from an enterprise bean
We can assemble a web service-enabled enterprise bean JAR file with an assembly tool using artifacts generated from tooling.- Assembling a web services-enabled enterprise bean JAR file from a WSDL file
We can assemble a web services-enabled enterprise bean JAR file from a WSDL file with an assembly tool.- Assembling a WAR file enabled for web services from Java code
We can assemble a web application archive (WAR) file enabled for web services from Java code with an assembly tool.- Assembling a web services-enabled WAR file from a WSDL file
We can assemble a web application archive (WAR) file from a WSDL file enabled for web services.- Assembling an enterprise bean JAR file into an EAR file
We can assemble an enterprise bean JAR file into an enterprise archive (EAR) file with an assembly tool. Assembling the JAR file, and now the EAR file, are required tasks to enable Java code for web services.- Assembling a web services-enabled WAR into an EAR file
We can assemble a web services-enabled web application archive (WAR) file into an EAR file with an assembly tool.- Enable an EAR file for EJB modules that contain web services
When wer EAR file contains enterprise JavaBeans (EJB) modules that contain Web services, run the endptEnabler command-line tool or an assembly tool before deployment to produce a web services endpoint web application archive (WAR) fiile.- Assembling a JAR file enabled for web services from an enterprise bean
We can assemble a web service-enabled enterprise bean JAR file with an assembly tool using artifacts generated from tooling.- Assembling a web services-enabled enterprise bean JAR file from a WSDL file
We can assemble a web services-enabled enterprise bean JAR file from a WSDL file with an assembly tool.- Assembling a WAR file enabled for web services from Java code
We can assemble a web application archive (WAR) file enabled for web services from Java code with an assembly tool.- Assembling a web services-enabled WAR file from a WSDL file
We can assemble a web application archive (WAR) file from a WSDL file enabled for web services.- Assembling an enterprise bean JAR file into an EAR file
We can assemble an enterprise bean JAR file into an enterprise archive (EAR) file with an assembly tool. Assembling the JAR file, and now the EAR file, are required tasks to enable Java code for web services.- Assembling a web services-enabled WAR into an EAR file
We can assemble a web services-enabled web application archive (WAR) file into an EAR file with an assembly tool.- Enable an EAR file for EJB modules that contain web services
When wer EAR file contains enterprise JavaBeans (EJB) modules that contain Web services, run the endptEnabler command-line tool or an assembly tool before deployment to produce a web services endpoint web application archive (WAR) fiile.
Related:
EJB content in WAR modules Development and assembly tools Assembling a web services-enabled client JAR file into an EAR file Assembling a JAR file enabled for web services from an enterprise bean Assembling a web services-enabled enterprise bean JAR file from a WSDL file Assembling a WAR file enabled for web services from Java code Assembling a web services-enabled WAR file from a WSDL file Deploy web services applications onto application servers Assemble applications Configure the webservices.xml deployment descriptor for JAX-RPC web services Configure the webservices.xml deployment descriptor for handler classes Configure the ibm-webservices-bnd.xmi deployment descriptor for JAX-RPC web services JAX-RPC web services enabled module - deployment descriptor settings (ibm-webservices-bnd.xmi file)