This subsection describes the notes on using the exploded archive format.

• With the exploded archive-format J2EE applications, you cannot perform the following operations as compared to the archive-format J2EE applications:
  
  • Adding EJB-JARs/ WARs/ RARs
  • Deleting EJB-JARs/ WARs/ RARs
  • Adding library JAR
  • Deleting library JAR
  To perform these operations on an exploded archive-format J2EE application:
  
  1. Delete the exploded archive-format J2EE application from the J2EE server.
  2. Modify the application directory.
  3. Import the modified exploded archive-format J2EE application.
• To use the exploded archive-format J2EE applications, we recommend that you change the security settings so that the J2EE application can access any resource. For details on changing the security settings, see 13.4.3 Settings for using the exploded archive-format J2EE applications (changing the security settings).
• When you import an exploded archive-format J2EE application, you cannot specify a path containing the UNC name as the application directory path. When a path containing the UNC name is specified, a command execution error occurs.
• Do not add, delete, or overwrite the files or directories beneath the application directory when the J2EE server is being started and when the server management commands are being executed.
• You cannot use the J2EE applications for which the <alt-dd> tag is specified in application.xml, in the exploded archive format. When you import an exploded archive-format J2EE application or when you import the EAR files and ZIP files exported from the J2EE server in an exploded archive format, a command execution error occurs if the <alt-dd> tag is specified in application.xml of the J2EE application.
• In the J2EE server, multiple J2EE applications cannot specify the same directory as the application directory. When you import an exploded archive-format J2EE application or when you import the EAR files and ZIP files exported from the J2EE server in an exploded archive format, a command execution error occurs if the specified directory already exists as the application directory of another J2EE application.
• If the J2EE server already contains J2EE applications with the following directories as the application directory or WAR directory, a command execution error occurs during the import operation:
  
  • Directory above the directory specified in the -a option or -d option of the cjimportapp command
  • Directory beneath the directory specified in the -a option or -d option of the cjimportapp command
• When you import an application by specifying the directory immediately beneath the Windows drive (such as C:\) or the UNIX root directory (/) in the -a option of the cjimportapp command, specify the application name in the <display-name> tag of the application.xml file.
• The JAR file name specified when you import the application is used as the directory name in the work directory. Specify the JAR file name such that the work directory path length does not reach the maximum limit for the platform. For details on estimating the work directory path length, see Appendix C.1 Work directory of a J2EE server in the uCosminexus Application Server System Setup and Operation Guide.
• We do not recommend the configuration in which the Java source files are placed under the application directory. If the class files and Java source files placed in the same directory are not synchronized, the application might fail to start or reload.
• Do not specify the following single-byte symbols in the application directory name and module name because these symbols are treated as escape characters:
  ! # % +
  
• The JAR files placed under the application directory are treated as the library JARs. Therefore, do not place stubs and interfaces obtained by the cjgetstubsjar command under the application directory.
• When you import the exploded archive-format J2EE applications, the library JAR is searched in all the directories beneath the application directory excluding the EJB-JAR directory and WAR directory. Therefore, if there are many files under the application directory excluding the EJB-JAR directory and WAR directory, the process of importing the applications might take some time.
• When you start an application, if the post-expansion absolute file path of the entries included in the WAR files, EJB-JAR files, or EAR files, which are expanded when the application is imported, do not exist in the respective root directories, the KDJE42389-E error message is displayed and the file expansion processing is interrupted.