Integration parameters

Guidewire provides the following configuration parameters in the config.xml file that relate to how multiple Guidewire applications integrate with each other.

For information on editing config.xml and setting configuration parameters, see Working with configuration parameters.

BillingSystemArchiveEnabled

Whether or not the archiving is enabled in the billing system. This parameter needs to match billing system settings for archiving.

Default: false

BillingSystemArchivePolicyPeriodDays

The minimum number of days after the term end date before the billing policy period is archived. This value must be less than or equal to the setting in the billing system. Guidewire recommends setting the value to be equal and keeping the value of BillingSystemArchivePolicyPeriodDays synchronized with the value of ArchivePolicyPeriodDays in BillingCenter.

This parameter is used to decide whether to check the billing system for the archiving flag. A negative value disables this check, and PolicyCenter ignores the archiving flag when determining whether to call the billing system API. This parameter is applicable only if the BillingSystemArchiveEnabled parameter is true.

Default: -1

BillingSystemURL

URL to use in ExitPoint PCF pages that view items in the billing system.

  • If integrating Guidewire PolicyCenter with Guidewire BillingCenter, then set this parameter to the ­BillingCenter base URL (for example, http://server/bc). In this case, the exit points add the appropriate BillingCenter entry point.
  • If integrating with a non-Guidewire billing system, then you need to modify the ExitPoint PCF to set up the parameters required by that system.
  • If you omit this parameter or if you set it to an empty string, then PolicyCenter hides the buttons in the interface that take you to the exit points.

Default: Empty string

See also

ClaimSystemURL

URL to use in ExitPoint PCF pages that view items in the claims system.

  • If integrating Guidewire PolicyCenter with Guidewire ClaimCenter, then set this parameter to the ­ClaimCenter base URL (for example, http://server/cc). In this case, the exit points add the appropriate ClaimCenter entry point.
  • If integrating with a non-Guidewire claim system, then you need to modify the ExitPoint PCF to set up the parameters required by that system.
  • If you omit this parameter or if you set it to an empty string, then PolicyCenter hides the buttons in the interface that take you to the exit points.

Default: Empty string

See also

DefaultXmlExportIEncryptionId

The unique encryption ID of an encryption plugin. If archiving is enabled, PolicyCenter uses the encryption plugin to encrypt any encrypted fields during XML serialization.

Default: null (no encryption)

EnableCreditCardCollectionUI

If true, a set of demonstration screens to collect tokenized credit card information is enabled. This inbound payments reference feature includes a solution that simulates a PCI-compliant integration with a payment gateway.

Default: false

Set for server: No

EnableCustomBilling

In PolicyCenter 10.0, Custom Billing Options on the Payment screen has been replaced by Invoicing Overrides. If you implemented Custom Billing Options in a previous release and wish to restore Custom Billing Options and the related functionality, set the EnableCustomBilling parameter to true.

Default: false

KeepCompletedMessagesForDays

Number of days after which PolicyCenter purges old messages in the message history table.

Default: 90

LockDuringDistributedMessageRequestHandling

When processing a distributed message transaction, the parameter determines whether to lock the transaction's message object. The parameter has no effect on non-distributed message transactions.

Default: false

LockPrimaryEntityDuringMessageHandling

While processing a message transaction, PolicyCenter uses this configuration parameter to determine whether to lock the primary entity instance associated with the message. If the message has no primary entity associated with it, setting this parameter to true has no effect.

Regardless of the parameter's setting, PolicyCenter locks the primary entity instance only if the transaction's message object is also locked. For example, a distributed message transaction that does not lock its message object will not lock the primary entity either, even if locking of the entity is enabled by this parameter. Whether a distributed message transaction locks its message object is determined by the LockDuringDistributedMessageRequestHandling configuration parameter.

Considerations for production installations

In the base configuration, PolicyCenter (and ContactManager) do not update the primary entity while acknowledging a message. Therefore, it is possible to set configuration parameter LockPrimaryEntityDuringMessageHandling to false under the following conditions:
  • You are not updating any entity on the acknowledgment of a message.
  • You are only updating a very few fields on non-primary entities that do not cause a lock on a primary entity. The non-primary entities must be mutually exclusive for destinations on the acknowledgment of a message.

Guidewire recommends that you review your integration code for these conditions before you set this configuration parameter to false.

If you do set LockPrimaryEntityDuringMessageHandling to false, be aware that PolicyCenter does not lock the primary entity during the following processes:
  • Sending a message
  • Handling all parts of a message
  • Marking a message as skipped

However, PolicyCenter does lock the primary entity message creation.

Default: true

PaymentSystemURL

URL to use in ExitPoint PCF pages that view items in a payment system.

  • If integrating Guidewire PolicyCenter with Guidewire BillingCenter, then set this parameter to the BillingCenter base URL (for example, http://server/bc). In this case, the exit points add the appropriate BillingCenter entry point.
  • If integrating with a non-Guidewire billing system, then you need to modify the ExitPoint PCF to set up the parameters required by that system.
  • If you omit this parameter or if you set it to an empty string, then PolicyCenter hides the buttons in the interface that take you to the exit points.
Note: Guidewire configures this parameter in the base configuration to work with a demonstration payment system. For more details, see Implementing the billing summary plugin.

Default: pc

See also

PluginStartupTimeout

OSGi plugins startup timeout (in seconds). The PluginConfig component waits for at most this time for all required OSGi plugins to start. The PluginConfig component reports an error for each OSGi plugin that does not start after this timeout has expired.

Default: 60