Difference between revisions of "Overloading policies"

Revision as of 20:31, 3 September 2013

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.

Policy overloads are placed inside the Context element in the deployment file, where the connection strings are placed too.

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.

@@ Line 1: / Line 1: @@
 == 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:
-=== Adding an overloaded policy ===
+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.
-=== Syntax and troubleshooting ===
+=== Protecting the variables ===