Configuration parameters by environment
- Development
- Test
- Deployment (production)
So that you do not have to change configuration parameters each time you switch between environments, PolicyCenter provides the ability to set configuration parameters for a specific environment or for a specific server or server role.
Setting the env attribute on <param>
Environment-specific parameters can reference environment properties to indicate in which
environment or environments they are valid. You specify the environment or
environments for a configuration parameter in file config.xml
by adding an env attribute to the parameter definition. If you
want a parameter to apply for multiple values of the env attribute,
you can add a comma-separated list of values for the attribute.
-
<param name="..." value="..." env="..."/>
Setting the server attribute on <param>
Although it is possible for the server attribute to specify a server ID
value, the use of a server ID is usually too specific to be meaningful in most
cases. Thus, Guidewire recommends that you set the value of the
server attribute to one or more server roles instead. As
multiple servers can share the same server role, the server
attribute can affect any server with that server role. You can only set a single
value for the server attribute, however.
server attribute:-
server="#server_role"
Thus, #batch specifies the batch server role.
Typically, the only real need to use a server ID for the server
attribute is if there is a host that contains multiple NICs (Network Interface
Cards). In that case, it is possible to specify a URL with an address that is
specific to single NIC on the host machine.
Setting configuration parameters at runtime
-
gwb runServer -Denv=test -
gwb runServer -Dserver=#batch
