13.3 Archive-format J2EE applications

This section describes the deployment of J2EE applications using the archive format.

An archive-format J2EE application is one of the application formats that can be executed on a J2EE server. An archive-format J2EE application holds the application entities, such as the EJBs and servlets, in the working directory of the J2EE server. The following figure shows an archive-format J2EE application.

Figure 13-1 Archive-format J2EE application

[Figure]

With the archive-format J2EE applications, the application entity exists on the J2EE server and the components of the application are stored in the working directory of the J2EE server.

Normally, when you replace an archive-format J2EE application, operations, such as stopping the J2EE application that is running on the J2EE server, importing and deploying a new J2EE application, are performed. At this time, if you use the redeploy functionality, you can replace an archive-format J2EE application using fewer steps as compared to replacing a normal J2EE application.

When you replace a J2EE application using the redeploy functionality, the attribute information of the J2EE application can be inherited and the operations, such as stopping a J2EE application that is running on the J2EE server, importing and redeploying a new J2EE application, are no longer required. For details on the redeploy functionality, see 13.7 Redeploying J2EE applications.

Note
If the application version is Java EE 5 or later, you cannot specify a level higher than the root of the application package for the entry name in the EAR file. If a higher level is specified, the KDJE42387-E message is displayed when the J2EE application is imported and an error occurs.