About the database element

File database-config.xml stores connection and configuration parameters for the PolicyCenter database. Set database connections by uncommenting and modifying the appropriate sample <database> element in database-config.xml, accessible within Guidewire Studio under configuration > config.

The <database> element in database-config.xml has the following basic structure:

<database name="string" env="string" dbtype="oracle|sqlserver" 
      checker="true|false" addforeignkeys="true|false" printcommands="true|false">

   // If using database connection pool managed by PolicyCenter
  <dbcp-connection-pool jdbc-url="jdbc url" password-file="file name"> 
    <reset-tool-params collation="collation"
     oracle.tnsnames="Oracle TNS name" system.username="system username"
     system.password="system.password"/>
  </dbcp-connection-pool> 

   // If using a JNDI data source
  <jndi-connection-pool datasource-name="JNDI data source name" />

   // Oracle only
  <oracle-settings query-rewrite="true|false" statistics-level-all="true|false"
  stored-outline-category db-resource-mgr-cancel-sql >
  <upgrade>
    <ora-db-ddl> 
      <tablespaces admin="admin tablespace" index="index tablespace" op="op tablespace"
       staging="staging tablespace" typelist="typelist tablespace" lob="lob tablespace" />
    </ora-db-ddl>
  </upgrade>

   // SQL Server only
  <sqlserver-settings jdbc-trace-level="JDBC trace level" jdbc-trace-file="JDBC trace file"
   unicode-columns="true|false" />
  <upgrade>
    <mssql-db-ddl> 
      <mssql-filegroups admin="admin filegroup" index="index filegroup" op="op filegroup"
       staging="staging filegroup" typelist="typelist filegroup" lob="lob filegroup" />
    </mssql-db-ddl>
  <upgrade>

   <databasestatistics />
</database>

Some elements and attributes are not shown. These elements and attributes are described in other sections.

File database-config.xml contains a single root-level <database> element that takes the following attributes.

Attribute

Required

Default

Sets

addforeignkey

No

true

Used only for development and testing. Do not use this attribute in production.

checker

No

false

Important: Guidewire deprecates this attribute and recommends that you not use it.
Boolean value that specifies whether PolicyCenter runs consistency checks before it starts.
  • Development environments – For development environments with small data sets, you can enable consistency checks to run each time the PolicyCenter server starts. Set the value of checker in the database block to true to enable checks on server startup.
  • Production environments – Running consistency checks upon server startup can take a long time, impact performance severely, and possibly time out on very large datasets. Set the value of checker in the database block to false to disable checks on server startup.

Recommendations:

  • True – Guidewire recommends that you only set checker to true in development environments with small test data sets.
  • False – Guidewire recommends that you set checker to false under most circumstances.

See also

dbtype

Yes

...

Database type, either h2 (for the QuickStart database), oracle or sqlserver.

env

No

...

Optional environment variable. Use of the env attribute to set a server environment enables you to provide different database configurations for different server environments. For example, you can set up different database configurations for a production environment and a test environment.

See Example syntax for the <server> element for more information.

name

Yes

...

A string identifying the database for which PolicyCenter uses this connection specification.

printcommands

No

true

Boolean value that specifies whether the server prints database upgrade messages to the console upon startup.

By default, Guidewire sets the value of printcommands to true in the base configuration. Do not set printcommands to false in a production environment.

versionchecksonly

No

false

Boolean value that specifies whether the PolicyCenter server runs only database version checks at startup, without performing any actual database upgrade steps.

See also

Checking the database before upgrade in the Upgrade Guide

See also