+

Search Tips   |   Advanced Search

Assembling 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.

We can assemble Java-based web services modules with assembly tools provided with WebSphere Application Server. Before assembling a web services-enabled EAR file you must assemble an enterprise bean JAR file to enable for Web services. To learn more about the artifacts that are needed for the assembly of the enterprise bean JAR file, see the information on assembling an enterprise bean JAR file from Java code that is enabled for web services.

Restriction: Do not include a pound sign (#) in the name of files that are packaged within an application archive. Due to internal processing, the application server fails to correctly deploy the application when a pound sign is included in a file name within the application archive. When this failure occurs, an exception might occur when the application is being processed. Also, parts of the application might be missing after the application is deployed. To address this issue, rename any file names within the application archive so that they do not contain a pound sign.

To assemble a web services-enabled EAR file:

  1. Start an assembly tool. Read about starting the assembly tool in the Rational Application Developer documentation.

  2. If we have not done so already, configure the assembly tool so that it works on Java EE modules. You need to verify the Java EE and Web categories are enabled. Read about configuring the assembly tool in the Rational Application Developer documentation.

  3. Assemble the web services-enabled JAR file into an EAR file. The EAR file can contain an enterprise bean or application client JAR files, WAR files, web applications, and metadata describing the applications or application.xml files.


Results

A web services-enabled EAR file.


Example

In the following example, there is an application.xml deployment descriptor packaged with a web services-enabled JAR file called AddressBook.jar that is packaged into an EAR file called AddressBook.ear. The EAR file contains: 

META-INF/MANIFEST.MF
META-INF/application.xml
AddressBook.jar

An example of the application.xml deployment descriptor is as follows: 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"  "http://java.sun.com/dtd/application_1_3.dtd">
 <application id="Application_ID">
  <display-name>AddressBookJ2WEE</display-name>
  <description>AddressBook EJB Example from Java</description>
  <module id="EjbModule_1">
   <ejb>AddressBook.jar</ejb>
  </module>
 </application>


What to do next

We can enable an EAR file for EJB modules containing web services. Then, deploy the EAR file into WebSphere Application Server.


Related concepts

  • Development and assembly tools


    Related tasks

  • Assembling a JAR file that is enabled for web services from an enterprise bean
  • Assembling a web services-enabled enterprise bean JAR file from a WSDL file
  • Enable an EAR file for EJB modules containing web services