Varying the inbound integration settings

PolicyCenter provides the following means to vary configuration of inbound integration by system environment.

Inbound integration XML file

In your inbound-integration-config.xml file, each thread pool or integration element has a disabled attribute. If the value of that attribute is true, PolicyCenter does not enable the thread pool or integration.

If the value of that attribute is false, the action that PolicyCenter takes depends on the value of the optional env attribute. If you provide no value for this attribute, PolicyCenter enables the thread pool or integration. You can provide either a single value or list of comma-separated values for the env attribute. If you provide any value for the env attribute, PolicyCenter enables the thread pool or integration element only if a value in that env attribute matches the env system environment configuration setting.

For example, to use different JMS settings for development and for production, list two <jms-integration> elements. For one element, set the env attribute to development. For the other element, set the env attribute to production. For each element, set appropriate JMS configuration settings for that system environment.

Plugin property configuration in Plugins Registry

In the Plugins Registry, you must set the integrationservice plugin property in the user interface in one or more Plugins Registry files. In a single Plugins Registry file, you can optionally define the integrationservice plugin property multiple times with values that vary by system environment or server ID values.

You can use one or both of these techniques to vary the runtime behavior of the server based on the server environment.

To specify more than one environment for a given top-level element, you use comma-separated values for the env attribute. Although Guidewire supports the env attribute within elements of the inbound-integration-config.xml file, you cannot vary the configuration by server ID.