In addition to the properties associated with EGL parts, there are a number of Java™ runtime properties that control access to databases, files, and other resources. To help distinguish them from EGL properties, and to emphasize the fact that they are not properties under JEE, this documentation may refer to these Java runtime properties as settings.
The JEE environment file is created when you have set the j2ee build descriptor option to YES, and you have set the genDirectory build descriptor option instead of the genProject build descriptor option. Alternatively, a JEE environment file is also created when you have set the j2ee build descriptor option to YES, and you have set the genProject build descriptor option to a non-JEE project.
<env-entry> <env-entry-name>vgj.nls.code</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>ENU</env-entry-value> </env-entry>
<env-entry> <env-entry-name>vgj.nls.code</env-entry-name> <env-entry-value>ENU</env-entry-value> <env-entry-type>java.lang.String</env-entry-type> </env-entry>The name-type-value order is needed for all web projects, EJB and application client projects that run in JEE 1.4 and above. For web projects that run in JEE 1.3, the order name-value-type is used instead.
This step can be avoided if you generate directly into a project instead of into a directory. When you generate into a project, EGL can determine the type of project you are using and generate the environment entries in the appropriate order. Also, the serverType build descriptor option can affect the default level of the j2eeLevel build descriptor option.