Overloading policies
Revision as of 19:33, 3 September 2013 by old>Admin (→Example configuration)
Overloading policies
The server policies can be hardcoded into the deployment file for various reasons
- Ensure system values are not subject to change in the designer
- Ease environment replication: Just copy the whole database, and define environmental differences in a file.
Adding an overloaded policy
Policy overloads are placed inside the Context element in the deployment file, where the connection strings are placed too.
- Tomcat: <tomcat root>/conf/Catalina/localhost/<application>.xml
- JBoss:
The policy in question should use the following syntax:
<Parameter name="Policy.XXXXX" value="YYYYY"/>
X = Name of the policy Y = Value of the policy
Please ensure the datatype fits Policy type, or the overloaded value will default to the installation value.
Example configuration
<?xml version="1.0" encoding="UTF-8"?> <Context path="/TempusServa" swallowOutput="true"> <Parameter name="TestPropertyLoading" value="Succes"/> <Parameter name="Policy.applicationDisplayName" value="Killroy was here"/> <Parameter name="Policy.doMainMenuAccordion" value="false"/> <Parameter name="Policy.policyHideValues" value="true"/> <Resource name="jdbc/TempusServaLive" auth="Container" type="javax.sql.DataSource"
...
</Context>