Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Developer's Guide

- Previous: Naming Standards
- Next: Runtime Environments

## Directory Structure

When you deploy an application, the application is expanded to an open directory structure, and the directories holding the individual modules are named with `_jar`, `_war` and `_rar` suffixes. If you use the `asadmin deploydir` command to deploy a directory instead of an EAR file, your directory structure must follow this same convention.

Module and application directory structures follow the structure outlined in the J2EE specification. Here is an example directory structure of a simple application containing a web module, an EJB module, and a client module.

    + converter_1/
    |--- converterClient.jar
    |--+ META-INF/
    |  |--- MANIFEST.MF
    |  |--- application.xml
    |  |--- sun-application.xml
    |--+ war-ic_war/
    |  |--- index.jsp
    |  |--+ META-INF/
    |  |  |--- MANIFEST.MF
    |  |--+ WEB-INF/
    |     |--- web.xml
    |     |--- sun-web.xml
    |--+ ejb-jar-ic_jar/
    |  |--- Converter.class
    |  |--- ConverterBean.class
    |  |--- ConverterHome.class
    |  |--+ META-INF/
    |     |--- MANIFEST.MF
    |     |--- ejb-jar.xml
    |     |--- sun-ejb-jar.xml
    |--+ app-client-ic_jar/
       |--- ConverterClient.class
       |--+ META-INF/
          |--- MANIFEST.MF
          |--- application-client.xml
          |--- sun-application-client.xml

Here is an example directory structure of an individually deployed connector module.

    + MyConnector/
    |--- readme.html
    |--- ra.jar
    |--- client.jar
    |--- win.dll
    |--- solaris.so
    |--+ META-INF/
       |--- MANIFEST.MF
       |--- ra.xml

- Previous: Naming Standards
- Next: Runtime Environments

- © 2010, Oracle Corporation and/or its affiliates