WAS v8.5 > Develop applications > Develop web services > Assemble web services applications

Assemble 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 you develop the web service application, you 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 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.

1. Start an assembly tool. Read about starting the assembly tool in the Rational Application Developer documentation.
2. Assemble the web services enabled bean into the appropriate module.

   • For JavaBeans enabled as web services:
     1. Assemble a WAR file that is enabled for web services from Java code.
     2. Assemble a web services-enabled WAR file from a WSDL file.

   • For enterprise beans enabled as web services:
     1. Assemble a JAR file that is enabled for web services from an enterprise bean.
     2. Assemble a web services-enabled enterprise bean JAR file from a WSDL file.

     WAS v8.5 supports packaging enterprise beans in WAR files. If you include a web services-enabled enterprise bean JAR file into a WAR file, you must merge any information in the webservices.xml deployment descriptor files that are 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.

     Best practice: 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 your JAX-WS application. However if the application does not use the fault bean classes that are generated by the JAX-WS tooling (that is, we use a bottom-up development approach starting from Java and you 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.

3. Assemble the web services enabled module into an EAR file.
   • Assemble a web services-enabled WAR into an EAR file.
   • Assemble an enterprise bean JAR file into an EAR file.

4. Enable the EAR file for EJB modules containing web services.
   When the EAR file contains EJB modules containing 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 JMS or SOAP over HTTP.
5. Assemble a web services-enabled WAR file into an EAR file.
   

Results

You have a web services-enabled EAR file that we can deploy onto the application server.

Now you 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

• Assemble a JAR file that is 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.
• Assemble 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.
• Assemble a WAR file that is enabled for web services from Java code
  We can assemble a WAR file that is enabled for web services from Java code with an assembly tool.
• Assemble a web services-enabled WAR file from a WSDL file
  We can assemble a WAR file from a WSDL file that is enabled for web services.
• Assemble an enterprise bean JAR file into an EAR file
  We can assemble an enterprise bean JAR file into an 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.
• Assemble a web services-enabled WAR into an EAR file
  We can assemble a web services-enabled WAR file into an EAR file with an assembly tool.
• Enable an EAR file for EJB modules containing web services
  When your EAR file contains enterprise JavaBeans (EJB) modules containing Web services, run the endptEnabler command-line tool or an assembly tool before deployment to produce a web services endpoint WAR fiile.

Related concepts:

EJB content in WAR modules
Development and assembly tools

Related

Assemble a web services-enabled client JAR file into an EAR file
Assemble a JAR file that is enabled for web services from an enterprise bean
Assemble a web services-enabled enterprise bean JAR file from a WSDL file
Assemble a WAR file that is enabled for web services from Java code
Assemble 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

Reference:

JAX-RPC web services enabled module - deployment descriptor settings (ibm-webservices-bnd.xmi file)

+

Search Tips   |   Advanced Search