Contents of Application EAR File

The EAR file that is produced has the following structure and contents:

• META-INF Directory
  • application.xml

    This file is automatically generated and lists the mapping of EJB modules to JAR files that are contained in the application.

  • ibm-application-bnd.xmi

    A generated WebSphere Application Server -specific extension file.

  • ibm-application-ext.xmi

    A generated WebSphere Application Server -specific extension file.

  • was.policy

    WebSphere Application Server security policy file that grants the application the Java permissionjava.security.AllPermission.

  • MANIFEST.MF

    The manifest file which details the contents of the EAR file.

• Core JAR Files

  The core JAR files include¹:

  • antlr.jar
  • appinf.jar
  • appinf_internal.jar
  • coreinf.jar
  • rules.jar
  • jde_commons.jar
  • log4j.jar
  • commons-pool.jar
  • commons-codec.jar
  • commons-discovery.jar
  • jdom.jar
  • axis.jar
  • castor.jar
  • jaxrpc.jar
  • saaj.jar
  • java_cup.zip
  • InfrastructureModule.jar
  • InvalidationModule.jar
  • DBtoJMS.war
  • ClientModule.war
• Facade JAR Files

  This is only present if facade generation has been enabled. All facades defined in the application are packaged into one JAR file, FacadeModule.jar. This JAR file contains the bean implementation classes for the EJB modules that represent the facades. The JAR file contains the following files in the META-INF directory:

  • ejb-jar.xml

    This file is automatically generated and contains the definition of every EJB module contained in the JAR file. All the publicly available methods are listed and the details of the resources available to the EJB modules.

  • ibm-ejb-jar-bnd.xmi

    A generated WebSphere Application Server -specific extension file.

  • ibm-ejb-jar-ext.xmi

    A generated WebSphere Application Server -specific extension file.

  • Manifest.mf

    The manifest file, detailing the classpath for the EJB.

• Other JAR Files

  The other JAR files contain the generated and hand crafted code from the application. These include application.jar, codetable.jar, events.jar, struct.jar, messages.jar, implementation.jar and properties.jar. The properties.jar file contains the Bootstrap.properties file. This is the file containing the machine specific configuration properties for initially getting a connection to the database.