An EGL-generated Java™ program uses a set of runtime properties that provide information such as how to access the databases and files that are used by the program.
For details on the runtime properties used by a service generated with EGL, see Library part of type ServiceBindingLibrary.
In a J2EE module, every program has the same runtime properties because all code in the module shares the same deployment descriptor.
<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> <env-entry> <env-entry-name>vgj.nls.number.decimal</env-entry-name> <env-entry-value>.</env-entry-value> <env-entry-type>java.lang.String</env-entry-type> </env-entry>
In relation to a generated Java program that runs outside of a J2EE environment, you can generate the runtime properties into a program properties file or code that file by hand. (The program properties file provides the kind of information that is available in the deployment descriptor, but the format of the properties is different.)
programName.properties
Use of user.properties is appropriate when you specify properties that are specific to a user. EGL does not generate content for this file.
None of those files is mandatory, and simple programs do not need any.
In either case, MyProject/JavaSource must be in the classpath.
If you generate output to a Java project, EGL places the properties files (other than user.properties) in the appropriate folders.
If you are generating Java code for use in the same run-unit as Java code generated with an earlier version of EGL or VisualAge® Generator, the rules for deploying properties file depends on whether the first program in the run unit was generated with EGL 6.0 or later (in which case the rules described here apply) or whether the first program was generated with an earlier version of EGL or VisualAge Generator (in which case the properties files can be in any directory in the classpath, and the global file is called vgj.properties).
Finally, if the first program was generated with the earlier software, you can specify an alternate properties file, which is used throughout the run unit in place of any non-global program properties files. For details, see the description of property vgj.properties.file in Java runtime properties (details).
For details on generating properties into a deployment descriptor or into a J2EE environment file, see Setting deployment-descriptor values.
For details on the meaning of the runtime properties, see Java runtime properties (details).
For details on accessing runtime properties in your EGL code, see sysLib.getProperty.
Related concepts
EGL debugger
Generation of Java code into a project
J2EE environment file
Library part of type ServiceBindingLibrary
Program properties file
Run unit
Related tasks
Processing Java code that is generated into a directory
Setting up the J2EE runtime environment for EGL-generated code
Setting deployment-descriptor values
Updating the deployment descriptor manually
Updating the J2EE environment file
Related reference
genProperties
J2EE
Java runtime properties (details)
getProperty()