![[Contents]](FIGURE/CONTENT.GIF)
uCosminexus Application Server, System Setup and Operation Guide
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
The J2EE server creates directories and files by using server names, display names of applications, and the files in EAR files in a work directory. The directory names, file names, and path length have an upper limit and the J2EE server cannot operate normally if an entire work directory does not fit into the entire path. This section describes a structure of a work directory and formulas to estimate the path length of a work directory.
The work directory of the J2EE server is the work area required for operating the J2EE server. This work area stores information such as user password information, information of imported resource adapters, EAR files, EJB-JAR files, WAR files, and created J2EE applications.
J2EE server has the following work directories:
The following subsection describes the directory structure of each of the above-mentioned work directory. The subsection also describes the directory structure after executing the migration command.
A directory structure is shown in the figure and each directory is described. The numbers mentioned in the figure correspond to the numbers mentioned in the explanation. Also, if the same directory contains various types of files, only the longest file name is listed.
The following figure shows the directory structure of the J2EE application (configuration related).
Figure C-1 Directory structure of the J2EE application (configuration related)
![[Figure]](FIGURE/ZU070500.GIF)
The following figure shows the directory structure of the J2EE application (deployment related).
Figure C-2 Directory structure of the J2EE application (deployment related)
![[Figure]](FIGURE/ZU070600.GIF)
The following figure shows the directory structure of the J2EE resources.
Figure C-3 Directory structure of the J2EE resources
![[Figure]](FIGURE/ZU070700.GIF)
The following figure shows the directory structure of the J2EE resource adapter (configuration related).
Figure C-4 Directory structure of the J2EE resource adapter (configuration related)
![[Figure]](FIGURE/ZU070800.GIF)
The following figure shows the directory structure of the J2EE resource adapter (deployment related). Also, in the figure, if the same directory contains various types of files, only the longest file name is listed.
Figure C-5 Directory structure of the J2EE resource adapter (deployment related)
![[Figure]](FIGURE/ZU070900.GIF)
The following figure shows the directory structure of the Web application (JSP related).
Figure C-6 Directory structure of the Web application (JSP related)
![[Figure]](FIGURE/ZU071000.GIF)
The following figure shows the directory structure of the Web application (others).
Figure C-7 Directory structure of the Web application (others)
![[Figure]](FIGURE/ZU071100.GIF)
When you execute the migration command of the J2EE server or the Web container server, a directory with the name work directory_old is created under the work directory, and the files in the work directory of the earlier version are saved in that created directory. For future upgrade installation, the path length must have a space for work directory_old. The following figure shows the directory structure of the J2EE server or the Web container server, after executing the migration command.
Figure C-8 Directory structure of the J2EE server or the Web container server after executing the migration command
![[Figure]](FIGURE/ZU071200.GIF)
When you execute the migration command of the resource adapter, a directory with the name rarupdate_bk is created, and resource adapter files of each J2EE server are stored here. If the work directory is ...\directory-name, or .../directory-name, the backup RAR directory is set as ...\directory-name\rarupdate_bk, or .../directory-name/rarupdate_bk. The following figure shows the directory structure of the resource adapter after executing the migration command.
Figure C-9 Directory structure of the resource adapter after executing the migration command
![[Figure]](FIGURE/ZU071300.GIF)
If there is no space for adding the path length of rarupdate_bk under the work directory, you can specify a backup destination directory by using the -backupto option when executing the migration command, and store the files to the area having a space for path length. The following figure shows the directory structure of the resource adapter after executing the migration command when using the -backupto option.
Figure C-10 Directory structure of the resource adapter after executing the migration command (when a backup destination directory is specified by using the backupto option)
![[Figure]](FIGURE/ZU071400.GIF)
The following are the formulas for estimating the path length of the work directory (unit: bytes). Adjust various parameters so that all of these formulas are satisfied. Also, the Maximum Path Length used in these formulas is the path length limit that is specified for the OS. For details on the path length limit of the OS, check your OS documents.
Note that the maximum path length in Windows is 259 bytes.
![[Figure]](FIGURE/ZUENG005.GIF)
B+C+D+E+58 ![[Figure]](FIGURE/ZUENG000.GIF)
maximum path length B+C+E'+61 maximum path length B+C+E''+50 maximum path length B+C+D+ (greater value of F+37or M+68)+23 maximum path length (If F 35, convert to 35) B+C+G+22 maximum path length (if G 18, convert to 18) 123maximum path length B+C+J+34 maximum path length maximum path length B+C+L+43 maximum path length (when using Cosminexus RM) maximum path length (when using Cosminexus RM) B+C+H+L+I+N+22 maximum path length B+C+H+L+O+N+39 maximum path length maximum path length maximum path length 3)All Rights Reserved. Copyright (C) 2012, 2013, Hitachi, Ltd.