You must configure server properties to reflect your environment. You can do this using any of the following:
flashaccess-i15n.properties - Samples included in each of the .war files
AdobeInitial.properties - Sample located in the /shared folder on the DVD
You can use this file to override the properties set in the WAR file as follows:
Adobe recommends that you make use of the AdobeInitial.properties file, since this allows you to update your application WAR files without risking the loss of any previous property configuration setup you may have done in the flashaccess-i15n.properties file.
The Java System property mechanism.
You can apply individual properties to these specific server environments:
With this capability, you can use the same WAR file for all server environments. To apply properties to specific environments, append two underscore characters (’ __
') plus one of the following environment codes to the property name:
* `DEV`
* `STAGE`
* `PROD`
For example, to set the log level to INFO
for your production and staging servers, and to DEBUG
for your development server:
log.Level=INFO
log.Level__DEV=DEBUG
The server employs this search order for properties:
propertyname_environment
in AdobeInitial.properties
propertyname_environment
in flashaccess-15n.properties
propertyname_environment
in Java System properties
propertyname
in AdobeInitial.properties
propertyname
in flashaccess-15n.properties
propertyname
in Java System properties
You must specify the server’s environment name as a Java System property when starting the server. For example, when starting Tomcat with catalina.bat, set the CATALINA_OPTS
environment variable as follows:
-DENVIRONMENT_NAME=[ DEV | STAGE | PROD ]