Guidewire ClaimCenter™

Installation Guide
Release 10.0.0
©2001-2018 Guidewire Software, Inc.
For information about Guidewire trademarks, visit [Link]
Guidewire Proprietary & Confidential — DO NOT DISTRIBUTE

Product Name: Guidewire ClaimCenter

Product Release: 10.0.0
Document Name: Installation Guide
Document Revision: 25-September-2018
 Guidewire ClaimCenter 10.0.0 Installation Guide

Contents

About ClaimCenter documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Conventions in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

1 Introduction to installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Installation topics roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
About installation roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Servers, databases, and installation scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Graphical overview of development and production environments . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

2 Preparing a ClaimCenter environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installation environments overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
About installing ClaimCenter in a development environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
About installing ClaimCenter in a production environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Configuring the application server for Guidewire applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Running ClaimCenter with the appropriate permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Supported uses of the application servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
General guidelines for application server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Special considerations for clustered application server environments . . . . . . . . . . . . . . . . . . . . . . . .17
Guidewire parameters for a clustered environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Disabling IPv6 in a clustered environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Configuring the JVM for environments without graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
JVM heap size considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Heap size and memory in 32-bit and 64-bit applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Operating system limits on heap size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Load balancers and Guidewire applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Optional components installed with Guidewire applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Configuring JBoss for Guidewire applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Remove Stax2 JBoss JAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Install a JBoss instance for free-text search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Configuring Tomcat for Guidewire applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Hide Apache version information on error pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Remove Tomcat examples directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Do not implement the Tomcat native library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Increase the maximum concurrent threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
About session persistence on Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Install Tomcat as a windows service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
About heap size in Tomcat on windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Configuring WebLogic for Guidewire applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Increase heap size for WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Configuring WebSphere for Guidewire applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Increase heap size for WebSphere. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Adjust ping parameters for WebSphere with Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
WebSphere database cluster management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
WebSphere network deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Installing a WebSphere instance for free-text search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Configuring the database server for Guidewire applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Overview of database configuration for Guidewire applications . . . . . . . . . . . . . . . . . . . . . . . . . . .26

3
Guidewire ClaimCenter 10.0.0 Installation Guide

Overview of database permissions used for Guidewire applications . . . . . . . . . . . . . . . . . . . . . . . . .26

About linguistic search collation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
About deferrable indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Configuring database compression. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Configuring compression for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Configuring compression for SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Guidelines for configuring Oracle for ClaimCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Prerequisites to installing ClaimCenter on Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Prepare an Oracle database for ClaimCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Database statistics generation for Oracle databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
About Oracle resource consumer groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
About Oracle SecureFile LOBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
About table partitioning for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
About index partitioning for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
About Oracle date interval partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Guidelines for configuring SQL Server for ClaimCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Prerequisites to installing ClaimCenter on SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Install ClaimCenter on SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Configure SQL Server in management Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Create a ClaimCenter database in SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
About filegroups in SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Create filegroups in SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Grant Guidewire Data Management view permissions to ccUser . . . . . . . . . . . . . . . . . . . . . . . . .44
Disable the SQL Server autogrowth feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Set the READ_COMMITTED_SNAPSHOT option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
About index partitioning for SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Final SQL Server tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Development workstation requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Web client information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Levels of Guidewire support for web browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Enable DOM storage in Internet Explorer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Installing Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Supported Java version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
The Dynamic Code Evolution Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Verify JVM not running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Install the DCEVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Setting environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Check environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Documenting your environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

3 Installing a ClaimCenter development environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Overview of development environment options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Using multiple development instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Installing the QuickStart development environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Advantages to using the QuickStart software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
QuickStart development environment prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
About the QuickStart application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Configuring QuickStart ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
About the QuickStart default database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Install the bundled ClaimCenter QuickStart application server . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
QuickStart commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Troubleshooting the QuickStart application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Using the QuickStart database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Modify the QuickStart database file location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Using SQL Server or Oracle in a development environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

4
 Guidewire ClaimCenter 10.0.0 Installation Guide

Archiving in a development environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

Archive-related configuration files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Enable archiving in Guidewire ClaimCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Disabling Guidewire ClaimCenter archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Install sample data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

4 Installing a ClaimCenter production environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Installing Guidewire ClaimCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Unpack the ClaimCenter configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Configuring a database connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
About the database element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Mapping logical tablespaces to physical tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Configuration options for Oracle tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
Configuration options for SQL Server filegroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
Configuration options for individual database tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Configuration options for database table groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Specifying additional database parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
The JDBC URL format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
JDBC URL format for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
JDBC URL format for SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Obfuscating the database password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Use a password file to obfuscate the database password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
About SQL Server JDBC logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Using a JNDI data source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Configure ClaimCenter to use a direct JNDI data source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Configure ClaimCenter to use an indirect JNDI data source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Create an Oracle JNDI data source on JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Create a SQL Server JNDI data source on JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Create an Oracle JNDI data source on Tomcat. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Create a SQL Server JNDI data source on Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Create an Oracle JNDI data source on WebLogic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Create a SQL Server JNDI data source on WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Create an Oracle JNDI data source on WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Copy the Oracle JDBC driver to WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Create the Oracle JDBC provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Create the Oracle JNDI data source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Configure the Oracle data source properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Test the Oracle JNDI connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Create a SQL Server JNDI data source on WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Copy the SQL Server JDBC driver to WebSphere. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Create the SQL Server JDBC provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Create the SQL Server data source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
Configure the SQL Server data source properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Test the SQL Server JNDI connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Deploying to the application server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Installing ClaimCenter on JBoss in a production environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Set Java options for JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Add a servlet definition for JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Generate the ClaimCenter WAR file for JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Installing ClaimCenter on Tomcat in a production environment . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Add servlet definitions for Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Generate and deploy the ClaimCenter WAR file for Tomcat. . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Installing ClaimCenter on WebLogic in a production environment . . . . . . . . . . . . . . . . . . . . . . . . .81
Add a servlet definition for WebLogic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Enable HTTP authentication on WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

5
Guidewire ClaimCenter 10.0.0 Installation Guide

Generate the ClaimCenter EAR file for WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Install the ClaimCenter EAR file on WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Ways to start ClaimCenter on WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Installing ClaimCenter on WebSphere in a production environment. . . . . . . . . . . . . . . . . . . . . . . . .83
Add a welcome-file-list element to file [Link]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Generate the ClaimCenter EAR file for WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Install the ClaimCenter EAR file on WebSphere. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

5 Additional ClaimCenter setup tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Additional installation information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Change the Superuser password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Generate Java API libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Integrating ClaimCenter and PolicyCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Configure ClaimCenter to retrieve policy information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Configuring ClaimCenter to convert PolicyCenter objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
Configure PolicyCenter to retrieve claim information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Defining authentication between PolicyCenter and ClaimCenter . . . . . . . . . . . . . . . . . . . . . . . . . . .91
Configure ClaimCenter to send large loss notification to PolicyCenter . . . . . . . . . . . . . . . . . . . . . . .92
Test ClaimCenter large loss notification integration with PolicyCenter. . . . . . . . . . . . . . . . . . . . . . .93
Archiving in a production environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Connecting a web client to ClaimCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Configure Microsoft Windows accessibility for Firefox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
About single sign-on authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Configure single sign-on authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Starting ClaimCenter on the application server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
Start ClaimCenter on JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
Start ClaimCenter on Tomcat on windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
Start Tomcat in same command prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Start ClaimCenter on WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Start ClaimCenter on WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Tune memory settings for application processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

6 Configuring free-text search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

About free-text search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Overview of free-text search setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Free-text search options for production and development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Simplified free-text search setup with embedded operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Guidewire Solr extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Guidewire Solr home directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Free-text batch load command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Securing database credentials for free-text batch load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Securing Guidewire Solr Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Requiring authentication in Guidewire Solr Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Configuring Guidewire Solr Extension to run with SSL activated. . . . . . . . . . . . . . . . . . . . . . . . 104
Configure free-text search for embedded operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Set up free-text search for embedded operation on QuickStart. . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Set up free-text search for embedded operation on Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Configure free-text search for external operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
About the free-text batch load command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Configure the free-text batch load command for ClaimCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

7 Command reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Build tool commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Core application tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Configuration upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Application server tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
6
 Guidewire ClaimCenter 10.0.0 Installation Guide

Globalization tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Integration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Change verification tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Documentation generation and other tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Merge command tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Plugin development tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
User interface tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

7
Guidewire ClaimCenter 10.0.0 Installation Guide

8
 Guidewire ClaimCenter 10.0.0 Installation Guide

About ClaimCenter documentation

The following table lists the documents in ClaimCenter documentation:

Document Purpose
InsuranceSuite Guide If you are new to Guidewire InsuranceSuite applications, read the InsuranceSuite Guide for informa‐
tion on the architecture of Guidewire InsuranceSuite and application integrations. The intended read‐
ers are everyone who works with Guidewire applications.
Application Guide If you are new to ClaimCenter or want to understand a feature, read the Application Guide. This guide
describes features from a business perspective and provides links to other books as needed. The in‐
tended readers are everyone who works with ClaimCenter .
Database Upgrade Guide Describes the overall ClaimCenter upgrade process, and describes how to upgrade your ClaimCenter
database from a previous major version. The intended readers are system administrators and imple‐
mentation engineers who must merge base application changes into existing ClaimCenter application
extensions and integrations.
Configuration Upgrade Guide Describes the overall ClaimCenter upgrade process, and describes how to upgrade your ClaimCenter
configuration from a previous major version. The intended readers are system administrators and im‐
plementation engineers who must merge base application changes into existing ClaimCenter applica‐
tion extensions and integrations. The Configuration Upgrade Guide is published with the Upgrade
Tools and is available from the Guidewire Community.
New and Changed Guide Describes new features and changes from prior ClaimCenter versions. Intended readers are business
users and system administrators who want an overview of new features and changes to features. Con‐
sult the “Release Notes Archive” part of this document for changes in prior maintenance releases.
Installation Guide Describes how to install ClaimCenter . The intended readers are everyone who installs the application
for development or for production.
System Administration Guide Describes how to manage a ClaimCenter system. The intended readers are system administrators re‐
sponsible for managing security, backups, logging, importing user data, or application monitoring.
Configuration Guide The primary reference for configuring initial implementation, data model extensions, and user inter‐
face (PCF) files for ClaimCenter . The intended readers are all IT staff and configuration engineers.
PCF Reference Guide Describes ClaimCenter PCF widgets and attributes. The intended readers are configuration engineers.
Data Dictionary Describes the ClaimCenter data model, including configuration extensions. The dictionary can be gen‐
erated at any time to reflect the current ClaimCenter configuration. The intended readers are configu‐
ration engineers.
Security Dictionary Describes all security permissions, roles, and the relationships among them. The dictionary can be
generated at any time to reflect the current ClaimCenter configuration. The intended readers are con‐
figuration engineers.
Globalization Guide Describes how to configure ClaimCenter for a global environment. Covers globalization topics such as
global regions, languages, date and number formats, names, currencies, addresses, and phone num‐
bers. The intended readers are configuration engineers who localize ClaimCenter.
Rules Guide Describes business rule methodology and the rule sets in Guidewire Studio for ClaimCenter . The in‐
tended readers are business analysts who define business processes, as well as programmers who
write business rules in Gosu.
Contact Management Guide Describes how to configure Guidewire InsuranceSuite applications to integrate with ContactManager
and how to manage client and vendor contacts in a single system of record. The intended readers are
ClaimCenter implementation engineers and ContactManager administrators.

About ClaimCenter documentation 9

Guidewire ClaimCenter 10.0.0 Installation Guide

Document Purpose
Best Practices Guide A reference of recommended design patterns for data model extensions, user interface, business
rules, and Gosu programming. The intended readers are configuration engineers.
Integration Guide Describes the integration architecture, concepts, and procedures for integrating ClaimCenter with ex‐
ternal systems and extending application behavior with custom programming code. The intended
readers are system architects and the integration programmers who write web services code or plu‐
gin code in Gosu or Java.
Java API Reference Javadoc‐style reference of ClaimCenter Java plugin interfaces, entity fields, and other utility classes.
The intended readers are system architects and integration programmers.
Gosu Reference Guide Describes the Gosu programming language. The intended readers are anyone who uses the Gosu lan‐
guage, including for rules and PCF configuration.
Gosu API Reference Javadoc‐style reference of ClaimCenter Gosu classes and properties. The reference can be generated
at any time to reflect the current ClaimCenter configuration. The intended readers are configuration
engineers, system architects, and integration programmers.
Glossary Defines industry terminology and technical terms in Guidewire documentation. The intended readers
are everyone who works with Guidewire applications.

Conventions in this document

Text style Meaning Examples
italic Indicates a term that is being defined, added A destination sends messages to an external system.
emphasis, and book titles. In monospace text, Navigate to the ClaimCenter installation directory by running the follow‐
italics indicate a variable to be replaced. ing command:

cd installDir

bold Highlights important sections of code in for (i=0, i<[Link](), i++) {

examples. newArray[i] = someArray[i].getName()
}

narrow bold The name of a user interface element, such as Click Submit.
a button name, a menu item name, or a tab
name.
monospace Code examples, computer output, class and The getName method of the IDoStuff API returns the name of the
method names, URLs, parameter names, string object.
literals, and other objects that might appear in
programming code.
monospace Variable placeholder text within code Run the startServer server_name command.
italic examples, command examples, file paths, and Navigate to [Link]
URLs.

Support
For assistance, visit the Guidewire Community.

Guidewire customers
[Link]

Guidewire partners
[Link]

10 About ClaimCenter documentation

chapter 1

Introduction to installation

Installing ClaimCenter starts with understanding the installation options that are available and which option to
choose.

Installation topics roadmap

The following topics describe how to install ClaimCenter.

Topic Description
“About installation roles” on page 11 Overview that discusses the different ways to install
ClaimCenter.
“Graphical overview of development and production environ‐ Diagram that shows how the ClaimCenter development
ments” on page 13 and production environment interact
“Preparing a ClaimCenter environment” on page 15 Steps to prepare a development or production environ‐
ment for ClaimCenter.
“Installing a ClaimCenter development environment” on page How to install a ClaimCenter development environment
51 using the QuickStart server and database or Tomcat.
“Installing a ClaimCenter production environment” on page 59 How to deploy ClaimCenter to an application server and
database server production environment.
“Additional ClaimCenter setup tasks” on page 87 Optional installation tasks you may want to perform after
you complete the installation and deployment of a
ClaimCenter development or production environment.
“Command reference” on page 111 Descriptions of the QuickStart and build commands.
Topic the System Administration Guide describes
ClaimCenter command utilities used by system administra‐
tors.

About installation roles

The people that install and develop Guidewire ClaimCenter have various roles. The following list describes these
roles.

Introduction to installation 11
Guidewire ClaimCenter 10.0.0 Installation Guide

Role Description
Demonstrator or Trainer Starts up the application quickly, loads sample data and demonstrates features.
Application Developer Changes the behavior of the application including the user interface, rules, and applica‐
tion logic.
Integration Developer Develops software to connect ClaimCenter to external systems.
Conversion Developer Performs analysis and mapping of legacy data structures to Guidewire application data
model.
Build master deploying to testing Deploys finished application to test and production environments.
and production

Note: For information about supported servers and databases and the installation scenarios they
support, see “Servers, databases, and installation scenarios” on page 12.

See also
• “Installation environments overview” on page 15
• “Installing a ClaimCenter development environment” on page 51
• “Installing a ClaimCenter production environment” on page 59

Servers, databases, and installation scenarios

To help you choose an installation scenario, the following table describes the uses of servers and databases that you
can install with ClaimCenter.

Install ele‐ Type Good to know More information

ment
QuickStart application Bun‐ You can immediately use the QuickStart server • “Advantages to using the QuickStart
server dled without configuring it. It does not build a WAR software” on page 52
or EAR file, which it is necessary to do before • “Installing the QuickStart
deployment with other servers. development environment” on page
Use the QuickStart application server for dem‐ 52
onstration or development (dev) environ‐ • “About the QuickStart application
ments. server” on page 52
It is not possible to run ClaimCenter in produc‐
• System Administration Guide
tion (prod) mode on the QuickStart server.
JBoss application server Op‐ Suitable for production environments. • “Configuring the application server
tional for Guidewire applications” on page
16
• “Installing ClaimCenter on JBoss in a
production environment” on page
78
Tomcat application server Op‐ Suitable for production environments. • “Configuring the application server
tional for Guidewire applications” on page
16
• “Installing ClaimCenter on Tomcat in
a production environment” on page
80
WebSphere application Op‐ Suitable for production environments. • “Configuring the application server
server tional for Guidewire applications” on page
16
• “Installing ClaimCenter on
WebSphere in a production
environment” on page 83

12 chapter 1: Introduction to installation

 Guidewire ClaimCenter 10.0.0 Installation Guide

Install ele‐ Type Good to know More information

ment
WebLogic application Op‐ Suitable for production environments. • “Configuring the application server
server tional for Guidewire applications” on page
16
• “Installing ClaimCenter on WebLogic
in a production environment” on
page 81
QuickStart database Bun‐ You can immediately use the QuickStart data‐ • “Advantages to using the QuickStart
dled base in file mode. ClaimCenter creates and software” on page 52
stores the database files within the tmp direc‐ • “Using the QuickStart database” on
tory of the local drive. You can customize this page 54
location.
You can use the QuickStart database for dem‐
onstration or development environments.
Guidewire does not support QuickStart for a
production environment.
Guidewire does not support upgrades to the
QuickStart database. Configuring your applica‐
tion sometimes requires extending the data
model, which might require dropping the da‐
tabase.
With QuickStart, it is not possible to have
more than one database connection at a time.
Oracle database Op‐ It is possible to use the Oracle database for • “Configuring the database server for
tional both development and production. Guidewire applications” on page 26
• “Guidelines for configuring Oracle for
ClaimCenter” on page 33
• “Configuring a database connection”
on page 60
SQL Server database Op‐ It is possible to use the Microsoft SQL Server • “Configuring the database server for
tional database for both development and produc‐ Guidewire applications” on page 26
tion. • “Guidelines for configuring SQL
Server for ClaimCenter” on page 40
• “Configuring a database connection”
on page 60

Graphical overview of development and production environments

The following diagram illustrates how the ClaimCenter development and production environment interact.

Introduction to installation 13
Guidewire ClaimCenter 10.0.0 Installation Guide

Local (Development) Environment Production

Application Server

Guidewire
Studio
Debug
Development Debug
QuickStart
Server
Test
Server
ClaimCenter
QuickStart Database Application
and
Check Out/Submit

Configuration
Files
Database
Local
Configuration WAR / EAR
Files

SCM
System

ClaimCenter Database

Dotted lines indicate actions that you perform. For example, you create a WAR or EAR file from your configured
development environment and move it to the production server.
To assist with this development and testing process, Guidewire bundles the following with the ClaimCenter
application:
• A QuickStart development server
• A QuickStart database
• A QuickStart test server that you cannot control
• A QuickStart test database that is separate from the QuickStart database
Guidewire bundles the QuickStart test server and test database for testing. These components are internally
controlled. You can use either the bundled QuickStart development server bundled with ClaimCenter or use an
external application server such as Tomcat. If you use the QuickStart method, then the default development server is
Jetty and the database is H2. Guidewire does not support the QuickStart application server or database for a
production environment.

14 chapter 1: Introduction to installation

chapter 2

Preparing a ClaimCenter environment

You must install and configure necessary system components so that your network can support ClaimCenter.
Additionally, there are preparatory steps to follow to deploy a production instance of ClaimCenter.

IMPORTANT The versions of third-party products that Guidewire supports for this release are subject
to change without notice. See the Supported Software Components knowledge article for current
system and patch level requirements. Visit the Guidewire Community and search for knowledge
article 1005, “Supported Software Components”.

Installation environments overview

ClaimCenter has a typical J2EE three-tier architecture: client, application server, and database server. For the
application to function, install and configure each tier correctly. Before you get started, ensure that you have the
appropriate software versions to support ClaimCenter. Guidewire recommends strongly that you obtain support
contracts with vendors for all tiers of your application infrastructure.
Although production environments can run on operating systems other than Microsoft Windows, all development
environments must run on the Windows operating system. However, you can build ClaimCenter on a non-
development Unix system prior to deploying the ClaimCenter application.

About installing ClaimCenter in a development environment

Guidewire supports the bundled QuickStart application server for development environments.

IMPORTANT For ClaimCenter development, all application builds must use the appropriate Oracle
JDK. See the Supported Software Components knowledge article for current system and patch level
requirements. Visit the Guidewire Community and search for knowledge article 1005, “Supported
Software Components”.

For all development environments, review the following topics:

• “Development workstation requirements” on page 46
• “Web client information” on page 46
• “Running ClaimCenter with the appropriate permissions” on page 16 (Windows information only)
• “Installing Java” on page 47
• “Setting environment variables” on page 49
• “Documenting your environment” on page 50
Preparing a ClaimCenter environment 15
Guidewire ClaimCenter 10.0.0 Installation Guide

If using an Oracle or SQL Server database server in a development environment, review also:
• “Configuring the database server for Guidewire applications” on page 26
After reviewing the relevant development environment information, proceed to “Installing a ClaimCenter
development environment” on page 51.

See also
• “Development workstation requirements” on page 46

About installing ClaimCenter in a production environment

In production environments, Guidewire strongly recommends that you allocate separate dedicated hardware for the
application server and database server tiers. Reserve this hardware solely for use with Guidewire ClaimCenter.
Using dedicated hardware is best for performance and for isolating the cause of any issues that arise.
Although production environments can run on operating systems other than Windows, you must develop
ClaimCenter on a Windows system prior to deploying ClaimCenter.
ClaimCenter requires a 64-bit operating system and JVM for a production installation.
For production environments, review the following material:
• “Preparing a ClaimCenter environment” on page 15
• “Installing a ClaimCenter production environment” on page 59

Configuring the application server for Guidewire applications

The ClaimCenter application server relies on a third-party servlet container for execution and connection services.
There are some adjustments you must make to the supported application servers.

Running ClaimCenter with the appropriate permissions

It is important that the software processes that support your ClaimCenter application run with the appropriate
permissions. How you set up these accounts depends on whether the application server environment is UNIX-based
or Windows:

Micro‐ If your network servers are Microsoft Windows systems, create a user with the Log on as a service right. Ensure that
soft this user is not a member of any group. Then, start the application server process as this user to ensure that
Win‐ ClaimCenter is run with the correct rights.
dows If you run Tomcat on Microsoft Windows, install the ClaimCenter server as a Windows service. See “Install Tomcat as
a windows service” on page 22 for more information.
UNIX For a UNIX‐based operating system, the ClaimCenter‐related processes must run in non‐privileged (user) mode. A
process in non‐privileged mode can access only its own memory. To ensure that the ClaimCenter processes run in
the correct mode, create a specific user account on each server and run the corresponding applications under these
accounts.

Supported uses of the application servers

Guidewire supports the following servers for production or development environments:

Production envi‐ Guidewire supports JBoss, Tomcat, WebLogic, and WebSphere application servers.
ronments
Development envi‐ Guidewire provides the best support for the bundled QuickStart application server.
ronments Guidewire also supports JBoss, Tomcat, WebLogic, and WebSphere application servers for development
use. However, because these application servers do not reload resources modified in Studio without a
rebuild and redeploy, they are not ideal for development work.

16 chapter 2: Preparing a ClaimCenter environment

 Guidewire ClaimCenter 10.0.0 Installation Guide

See also
• For information about the specific application server versions Guidewire supports for ClaimCenter 10.0.0, visit
the Guidewire Community and search for knowledge article 1005, “Supported Software Components”.
• For information on configuring the QuickStart application server, see “About the QuickStart application server”
on page 52.

General guidelines for application server installation

Do not include spaces in the installation path of the application server.
Run the application server on hardware supported by the application server provider. Guidewire can provide
assistance with hardware requirements for your production implementation.
Use only the JDK or JRE specified in the Supported Software Components, or a higher maintenance release. Tomcat
requires the JRE only.
Do not run multiple Guidewire applications or multiple instances of a single Guidewire application under a single
JVM in a production environment. Guidewire does not support this configuration. Each Guidewire application in a
production environment must run in a JVM reserved for that application.
ClaimCenter synchronizes with the database clock. The application server and database server must be in the same
time zone. The maximum difference allowed between the application server and database server is 29 minutes.

See also
• For information about the specific JDK or JRE versions that Guidewire supports for ClaimCenter 10.0.0, visit the
Guidewire Community and search for knowledge article 1005, “Supported Software Components”.

Special considerations for clustered application server environments

There are special considerations for running Guidewire applications in clustered environments.

See also
• System Administration Guide

Guidewire parameters for a clustered environment

File [Link] includes parameters to configure a clustered environment, including:
• ClusteringEnabled
• ClusterMemberPurgeDaysOld
• ClusterMemberRecordUpdateIntervalSecs
• ClusterStatisticsMonitorIntervalMins
• ConfigVerificationEnabled
• PDFMergeHandlerLicenseKey

See also
• See the Configuration Guide for parameter descriptions and suggested values.

Disabling IPv6 in a clustered environment

Some JDKs do not function correctly with IPv6. Disable IPv6 on any application server hosting Guidewire
applications.
To disable IPv6, set the following java option for your application server JVM:

[Link].preferIPv4Stack=true

See the following table for the exact implementation details.

Preparing a ClaimCenter environment 17
Guidewire ClaimCenter 10.0.0 Installation Guide

Tomcat Add the specified option to the CATALINA_OPTS environment variable.

WebLogic Either add this option to the JAVA_OPTIONS environment variable or directly modify the [Link] file for
the domain hosting ClaimCenter:
• If you modify JAVA_OPTIONS, the option applies to all WebLogic instances on that server.
• If you modify [Link], the option only applies to that domain.
If you modify [Link], add the option to the following line:
JAVA_OPTIONS="${JAVA_OPTIONS} ${JAVA_PROPERTIES}
-[Link]=${iterativeDevFlag}
-[Link]=${testConsoleFlag}
-[Link]=${logErrorsToConsoleFlag}"

Web‐ Add the option by using the Administrative Console:

Sphere 1. Navigate to Servers→Application servers→server.
2. In the Server Infrastructure section, navigate to the following location:
Java and process management→Process definition→Java virtual machine
3. Click Custom Properties.
4. Add the following option:
[Link].preferIPv4Stack=true

For more information on setting JVM options, see the documentation provided with your application server.

Configuring the JVM for environments without graphics

For Unix and Linux environments that do not have graphics support, such as an X11 graphics environment, set the
Java Virtual Machine (JVM) to run in headless mode. Specify this mode by setting the JVM parameter
[Link] to true on your application server. Setting [Link] to true prevents the JVM
from attempting to access a native graphics environment that does not exist.

JVM heap size considerations

The heap size determines how much memory the Java Virtual Machine (JVM) allocates to store an executing Java
program. Guidewire applications are memory intensive. Optimize performance by using large heaps.

See also
• “About heap size in Tomcat on windows” on page 22
• “Increase heap size for WebLogic” on page 23
• “Increase heap size for WebSphere” on page 24
Refer to the documentation provided with your application server for more information.

Heap size and memory in 32‐bit and 64‐bit applications

Production environments must use a 64-bit operating system and a 64-bit JVM. 64-bit JVMs inherently use more
memory to host the same number of objects. 32-bit JVMs have an inherent memory scalability limit that differs
significantly across platforms. This scalability limit makes those platforms unsuitable production platforms. 64-bit
JVMs are a more scalable option.
Note: The terms 32-bit and 64-bit refer to the size of the pointer used to reference an address.
Typically, a 64-bit JVM has an approximately 80% heap size overhead. For example, a 1024 MB heap for a 32-bit
JVM would host the same amount of objects as a 1843 MB heap for a 64-bit JVM. Generally, non-production
systems work correctly with heap sizes of 1024MB for a 32-bit JVM and 2048 MB for a 64-bit JVM.
For more information on heap size and tuning your production application to optimal performance, contact
Guidewire Support.

Operating system limits on heap size

The following tables group operating system heap size limitations by application server.
18 chapter 2: Preparing a ClaimCenter environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

Note: The following tables that list limits on heap size serve only as a starting point for tuning optimal
JVM settings for your configuration. They are useful if you are installing ClaimCenter and want to
start development work. Since each deployment needs to be tuned for its dataset, the heap sizes
depend on your usage and configuration. Production systems require careful sizing. Consult
Guidewire Services for assistance.

Heap sizing for jboss, tomcat, and WebLogic

Operating system 32‐bit heap size scales to: 64‐bit heap size scales to:
Linux 2.7GB Very large
Windows 1.5 GB Very large

Heap sizing for WebSphere

Operating system 32‐bit heap size scales to: 64‐bit heap size scales to:
AIX 2 GB Very large
Linux 2.56 GB Very large
Windows 1.5 GB Very large

Although IBM recommends that the initial Java heap size for WebSphere not be set to the maximum Java heap size,
Guidewire recommends otherwise. The IBM recommendations are not optimal for ClaimCenter. With a fixed heap,
you avoid performance penalties from resizing the heap on the rising edge as the system load rises, or on the falling
edge as load drops off. WebSphere provides several garbage collection policies. Guidewire recommends using the
generational concurrent (gencon) garbage collection policy with equal minimum and maximum heap size.
There is some variance across JVM technology with regard to memory allocation. Guidewire supports WebSphere
on the IBM JVM only. The IBM JVM manages the permanent space without the use of a permanent size setting.

Heap sizing for testing

To avoid performance degradation caused by forcing the JVM to adjust between two heap size values at runtime, set
the initial and maximum values to be the same. The following table provides recommended heap settings for
testing, determined with single user scenarios in mind. For production, consult Guidewire Services.

JVM parameter Variable name 32‐bit value 64‐bit value

inital heap size Xms 1 GB 2 GB
maximum heap size Xmx 1 GB 2 GB

Load balancers and Guidewire applications

In general, Guidewire supports load balancing of user interface server requests, to the extent that load balancers
support session affinity. It is more difficult to load balance SOAP calls because the SOAP standard does not provide
a standard way to track session state across requests. However, some load balancers support IP affinity, which
allows for very coarse load balancing of SOAP requests on a per-system basis. ClaimCenter supports both
sessionless and sessioned SOAP calls, the latter of which require IP affinity.

See also
• System Administration Guide

Preparing a ClaimCenter environment 19

Guidewire ClaimCenter 10.0.0 Installation Guide

Optional components installed with Guidewire applications

If you plan to have ClaimCenter send email through business logic, have an SMTP-compatible email server
available, such as Microsoft Exchange or UNIX Sendmail. It is also helpful to have access to an SNMP-compatible
system monitoring tool, such as IBM Tivoli or HP OpenView.
Some internal monitoring tools are built into ClaimCenter. Beyond that, you can use any SNMP-compatible system
monitoring tool, such as IBM Tivoli or HP OpenView, if you are running on an x86/Tomcat platform.

Configuring JBoss for Guidewire applications

JBoss requires special configurations to run it as the application server for ClaimCenter.

Remove Stax2 JBoss JAR

About this task
Remove the following JAR file from your JBoss installation, if present:

modules/system/layers/base/org/codehaus/woodstox/main/[Link]

The [Link] conflicts with ClaimCenter in the JBoss class loader. Not all JBoss versions
include this JAR file.

Install a JBoss instance for free‐text search

About this task
Enabling Guidewire free-text search requires that you install a different instance of JBoss than the instance that runs
your ClaimCenter application. In a production environment, Guidewire requires that you set up the separate JBoss
instance on a host that is separate from the one that hosts ClaimCenter. This separate instance of the application
server runs a full-text search engine, Apache Solr.
Whenever you install a separate JBoss instance for Guidewire free-text search, change the HTTP port to 8983. The
standard Solr port is 8983. You configure ports on JBoss in the following file:

JBOSS_HOME/server/default/conf/[Link]/META-INF/[Link]

Edit the file, and change the port property for the WebServer service from 8080 to 8983, as the following example
shows.

<bean class="[Link]">
<property name="serviceName">[Link]:service=WebServer</property>
<property name="port">8983</property>

See also
• “Install a Tomcat instance for free-text search ” on page 23
• “Installing a WebSphere instance for free-text search” on page 25

Configuring Tomcat for Guidewire applications

This topic provides notes on installing Tomcat to run ClaimCenter. Log in as a system administrator to install
Tomcat.

Hide Apache version information on error pages

About this task
By default, Apache HTTP server discloses the Apache version number in HTTP response headers and Apache error
pages. This information can reveal valuable details to an attacker about possible vulnerabilities in the software. If
20 chapter 2: Preparing a ClaimCenter environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

you are using Apache HTTP Server, Guidewire recommends that you customize your installation to not return this
information.

Procedure
1. Open the Apache HTTP server [Link] file, located in the conf directory.
2. Change ServerSignature to Off.
3. Change ServerTokens to Prod.
4. Save [Link].
5. Restart the Apache HTTP Server.

Remove Tomcat examples directory

About this task

Guidewire recommends that you remove the following directory from any Guidewire production implementation
that uses Tomcat:

TOMCAT_HOME/webapps/examples

There have been security vulnerabilities reported for some versions of the example scripts shipped with Tomcat.

Do not implement the Tomcat native library

Guidewire recommends that you do not implement the Tomcat Native Library. The major pitfall of using the library
is that it mixes Java code and C/C++ code in the same process. This mixture of coding languages requires the use of
the Java Native Interface (JNI), which is not optimal for performance. Guidewire has observed performance
degradation in tests with the Tomcat Native Library implemented.
The primary intent of the Tomcat Native Library is to execute some capabilities in native code versus Java. One
such capability is encryption, which is calculation intensive and not optimally suited for Java. If you want to use
encryption, consider offloading the encryption task to a dedicated component such as a hardware appliance, Apache
Web Server, or Microsoft Internet Information Server. These components are designed for such capabilities and are
therefore more secure. Additionally, having a dedicated component enables you to build a more secure network
organization with a DMZ.
The Tomcat server reports a message similar to the following upon startup if the Tomcat Native Library is not
implemented:

INFO: The Apache Tomcat Native library which allows optimal performance in production
environments was not found on the [Link]:

You can safely ignore this message.

Increase the maximum concurrent threads

About this task

By default, a Tomcat connector allows a maximum of 40 concurrent threads. Guidewire recommends that you set
the maximum number of concurrent threads to 200 instead.

Procedure
1. In the Tomcat installation directory, find and open file conf/[Link].
2. Find the definition for the http connector. It looks similar to the following:

<Connector port="8080" protocol="HTTP/1.1"

connectionTimeout="20000"
redirectPort="8443" />

Preparing a ClaimCenter environment 21

Guidewire ClaimCenter 10.0.0 Installation Guide

3. Add the maxThreads="200" setting to the Connector definition as follows:

<Connector port="8080" protocol="HTTP/1.1"

connectionTimeout="20000"
redirectPort="8443"
maxThreads="200" />

4. Save [Link].
5. Restart Tomcat to make these changes effective.

About session persistence on Tomcat

By default, Tomcat is configured with persistent sessions, which means Tomcat will write to disk all HTTP sessions
which are in memory at the time the server is shut down.
Whenever you restart the Tomcat server, it tries to restore the sessions. However, the session contents are
meaningful only to the old instance of ClaimCenter, so ClaimCenter throws an exception such as the following:

SEVERE: IOException while loading persisted sessions: [Link]: Error

deserializing Key of "[Link]":null
[Link]: Error deserializing Key of
"[Link]":null
at [Link]([Link])
...

Guidewire recommends that you configure Tomcat to disable session persistence.

Disable session persistence on Tomcat

Procedure
1. Open the Tomcat conf/[Link] file in a text editor.
2. Uncomment the <Manager> element:

<Manager pathname="" />

3. Save [Link].

Install Tomcat as a windows service

About this task

If you plan on installing only one application that uses Tomcat, you can use the Microsoft Window Service Installer.
The Windows Service Installer automatically configures Tomcat to run as a Windows Service. If you configure
ClaimCenter to run in Tomcat, Tomcat automatically runs as a Windows service. You can then set the server to start
automatically as Windows starts and use the standard Windows service management tools to manage the
ClaimCenter server.
Before the ClaimCenter application starts, the database server must already be up and running. Keep this order issue
in mind as you develop startup procedures and scripts.

About heap size in Tomcat on windows

You can increase the Tomcat heap size in one of two ways, depending whether you have installed Tomcat as a
Windows service or not. If you have Tomcat installed, and Tomcat is not run as a Windows Service, you set the heap
size for Tomcat by setting a Windows environment variable.
22 chapter 2: Preparing a ClaimCenter environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

Increase Tomcat service heap size on windows

Procedure
1. Start the Tomcat Windows service.
2. From the Start menu, click Control Panel.
3. Click Administrative Tools.
4. Click Services.
5. Right-click the Tomcat service and click Properties.
6. Add the following to Start parameters:
-Xms1024m -Xmx1024m

Increase Tomcat heap size on windows if Tomcat is not a service

Procedure
1. From the Windows desktop, right-click My Computer.
2. Select Properties and click the Advanced tab.
3. Click the Environment Variables button.
4. Under System Variables, click New.
5. Set the Variable Name to CATALINA_OPTS.
6. Set the Variable Value to -Xms1024m -Xmx1024m.
For values to set in this step, see “JVM heap size considerations” on page 18.
7. Click OK until the properties settings dialog closes.

Install a Tomcat instance for free‐text search

About this task

Guidewire free-text search requires that you set up a different instance of Tomcat than the instance that runs your
ClaimCenter application. In a production environment, Guidewire requires that you set up the separate Tomcat
instance on a host separate from the one that hosts your ClaimCenter application. This separate instance of the
application server runs a full-text search engine, Apache Solr.
Whenever you install a separate Tomcat instance for Guidewire free-text search, change the port for the HTTP/1.1
protocol to 8983. The standard Solr port is 8983. Edit the file TOMCAT_HOME/conf/[Link], and change the
connector port for the HTTP/1.1 protocol from 8080 to 8983, as the following example shows.

Connector port="8983" protocol="HTTP/1.1"

connectionTimeout="20000"
redirectPort="8443" />

See also
• “Install a JBoss instance for free-text search” on page 20
• “Installing a WebSphere instance for free-text search” on page 25

Configuring WebLogic for Guidewire applications

There are special considerations for WebLogic if you install it as the application server for a Guidewire application.

Increase heap size for WebLogic

About this task

Use the USER_MEM_ARGS environment variable to specify arguments to WebLogic during application server startup.
Preparing a ClaimCenter environment 23
Guidewire ClaimCenter 10.0.0 Installation Guide

Procedure
1. Create an environment variable on your system named USER_MEM_ARGS.
2. For the value of USER_MEM_ARGS, enter:
-Xms256m -Xmx1024m -[Link]=dev
The server mode entry is needed for reloading PCF pages.
3. (Optional) To run the server in production mode, remove the -[Link] argument listed in “Increase
heap size for WebLogic” on page 23.
By default, ClaimCenter starts in production mode on all application servers except the bundled QuickStart
server.

Configuring WebSphere for Guidewire applications

There are special considerations for WebSphere whenever you install it as the application server for a Guidewire
application.

Increase heap size for WebSphere

About this task

To support Guidewire applications in WebSphere, increase minimum heap size to 256 and maximum heap size to
1024.

Procedure
1. Open the WebSphere Administrative Console.
2. From the left menu, select Servers→Server Types→WebSphere application servers.
3. Select your server from the list on the right.
4. Under Server Infrastructure select Java and Process Management→Process Definition.
5. Under Additional Properties, select Java Virtual Machine.
6. Enter the following heap sizes, then click OK:
Initial heap size – 256
Maximum heap size – 1024
7. Click OK.
WebSphere displays a confirmation dialog that shows that changes have been made.
8. Click Save.

Adjust ping parameters for WebSphere with Oracle

About this task

If WebSphere times out while communicating with Oracle, Guidewire recommends that you set the following
values:

Server Parameter Value

ping interval 2000
ping timeout 6000

WebSphere database cluster management

Guidewire supports using WebSphere database cluster management, provided that you use the JDBC JAR file
bundled with ClaimCenter.
24 chapter 2: Preparing a ClaimCenter environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

WebSphere network deployment

Guidewire certifies the base version of WebSphere, but supports WebSphere Network Deployment (ND). Guidewire
products do not require any ND functionality to run. Some IBM terminology conflicts with Guidewire terminology,
for example:

Guidewire Cache Coherency for Clustering

ClaimCenter provides cache coherency to support clustering by maintaining an internal cache of objects for
performance reasons. The Guidewire implementation of clustering for cache coherency is completely
independent of the application server.

WebSphere ND Clustering
Clustering provided by WebSphere ND is different from ClaimCenter cache coherency. WebSphere ND
clustering is mostly about session replication, which is the capability to constantly maintain a user’s session state
across multiple computers in a cluster. Maintaining session state information is useful in the event of failover, in
which WebSphere transfers a user from one server to another. This functionality was intended to support
lightweight session objects such as those found in online shopping carts. Because Guidewire designed
ClaimCenter for enterprise users, each session must preserve a large volume of data. As a result, session
replication is prohibitively performance intensive and Guidewire does not support it.
WebSphere ND provides the following features that you can use in conjunction with ClaimCenter:

Deployment
WebSphere ND includes tools for automatically deploying configurations to servers in a cluster. Guidewire
supports these tools if used in conjunction with Guidewire Environment Specific Configuration settings.

Load balancing
WebSphere ND provides load balancing capabilities. See “Load balancers and Guidewire applications” on page
19.

See also
• System Administration Guide

Installing a WebSphere instance for free‐text search

Guidewire free-text search requires that you install a different instance of WebSphere than the instance that runs
your ClaimCenter application. In a production environment, Guidewire requires that you set up the separate
WebSphere instance on a host that is separate from the one that hosts ClaimCenter. This separate instance of the
application server runs a full-text search engine, Apache Solr.
Whenever you install a separate WebSphere instance for Guidewire free-text search, change the HTTP port for the
default host and its virtual host to 8983. The standard Solr port is 8983. You configure ports on WebSphere through
the administrative console.

See also
• “Change the port number in WebSphere for free-text search” on page 25

Change the port number in WebSphere for free‐text search

Procedure
1. Start the ClaimCenter application server.
2. Change the port for the default host in your WebSphere application server.
a. From the Administrative Console, navigate to Servers→Server Types→WebSphere application servers and
select your application server from the list of resources that you can administer.
The console displays the configuration page for your application server.
b. On the right, underneath Communications, click Ports.
Preparing a ClaimCenter environment 25
Guidewire ClaimCenter 10.0.0 Installation Guide

c. In the list of TCP/IP ports, click WC_defaulthost.

d. In the Port field, change the value from 9080 to 8983.
e. Click Apply.
f. In the Messages box, Click Save to apply the changes to the master configuration.
3. Change the port number for the virtual host in your WebSphere application server.
a. From the Administrative Console, navigate to Environment→Virtual hosts and click the name of your
physical host name. The default name of your physical host is default_host.
The console displays the configuration page for your physical host.
b. On the right, underneath Additional Properties, click Host Aliases.
c. Click New.
d. Enter the following values.

Field name Enter

Host Name Asterisk (*)
Port 8983

e. Click OK.
f. In the Messages box, click Save to apply the changes to the master configuration.
4. Stop and start the application server.

Configuring the database server for Guidewire applications

Guidewire recommends that you implement the guidelines contained in this topic as you install and configure the
database server.

Overview of database configuration for Guidewire applications

ClaimCenter 10.0.0 supports Oracle and SQL Server for production environments. See the Supported Software
Components knowledge article for information about which specific database server versions Guidewire supports for
ClaimCenter 10.0.0. Visit the Guidewire Community and search for knowledge article 1005, “Supported Software
Components”.
Run the database server on hardware supported by the database server provider. Guidewire can provide assistance
with hardware requirements for your production implementation. ClaimCenter depends heavily on back-end
database performance, which in turn depends on storage performance. Optimize the performance of your database
server.
For production systems, Guidewire recommends using a database server dedicated to ClaimCenter. Production
environments must use a 64-bit operating system and 64-bit database engine on the database server.
ClaimCenter synchronizes with the database clock. The application server and database server must be in the same
time zone and same physical location. The maximum time difference allowed between the application server and
database server is 29 minutes. If you use database clustering, synchronize all nodes in the database cluster with each
other.

Overview of database permissions used for Guidewire applications

ClaimCenter must be able to connect to your database through a user. Create a user called ccUser in your database.
ClaimCenter connects to the user named ccUser. The ccUser must have the correct permissions. The following
tables lists the permissions required for each database:

26 chapter 2: Preparing a ClaimCenter environment

 Guidewire ClaimCenter 10.0.0 Installation Guide

Data‐ Permissions Required

base
Oracle The ccUser must have the following permissions on the ClaimCenter Oracle database:
• Alter session
• Create operator
• Create procedure
• Create sequence
• Create session
• Create table
• Create trigger
• Create view
• Query rewrite
• Select any dictionary
If your users want to see statspack data on the Server Tools Info Pages→Oracle Statspack screen, grant the ccUser
access to the ClaimCenter performance statistics (perfstat) tables.
SQL The ccUser must have the public and db_owner roles on the ClaimCenter SQL Server database.
Server ClaimCenter supports several different data management pages for performance analysis of the application. To use
these pages, the ccUser must be granted view server state in ClaimCenter. The server login account must also
have view database state permission on each ClaimCenter data management view. The data management views
all start with a sys.dm_ prefix.

See also
• System Administration Guide

About linguistic search collation

It is possible to configure how ClaimCenter searches and sorts search results. For example, you can configure
whether searching is accent-sensitive or accent-insensitive, or if it is case-sensitive or case-insensitive.

See also
• Globalization Guide

About deferrable indexes

Guidewire defines performance-only indexes as those that are not unique and that do not include a table ID. During
staging table load, it is possible to configure ClaimCenter to drop performance-only indexes before loading data into
the staging table. Then, at completion of the data load, ClaimCenter recreates the indexes.
As it is possible to drop and then recreate these types of indexes, they are also known as deferrable indexes.
Dropping deferrable indexes can improve performance while loading data into staging tables.
It is possible to enable or disable the dropping of deferable indexes:
• For all tables – At the database (global) level, by using the <loader> element in [Link].
• For a named table– For one or more specified indexes on that table, by using the <loader-table> and <loader-
index> subelements on the <loader> element.
Configuration settings at the table level override any configuration set at the database (global) level.
Both the <loader> element and its subelement <loader-table> contain a drop-deferrable-indexes attribute.
This attribute, for each element, takes one of the following values:
• disable
• enable
• enable_all
Although similar, the attribute behavior is slightly different depending on the level at which you set the attribute.
Preparing a ClaimCenter environment 27
Guidewire ClaimCenter 10.0.0 Installation Guide

Element drop-deferrable-indexes

<loader> The drop-deferrable-indexes attribute on <loader> has the following meaning:

• disable – Disables the dropping of deferrable indexes at the global, database level for all staging tables.
• enable – Enables the dropping of the deferrable indexes for one or more specified staging tables. If set,
then you must also specify one or more <loader-table> subelements on <loader>.
• enable_all – Enables the dropping of deferrable indexes at the global, database level for all staging tables.
<loader- The drop-deferrable-indexes attribute on <loader-table> has the following meaning:
table> • disable – Disables the dropping of deferrable indexes for the named staging table. Use to override a
drop-deferrable-indexes attribute value of enable_all on <loader>, which enables the dropping of
deferrable indexes for all tables in the database.
• enable – Enables the dropping of deferrable indexes for this specific, named staging table. Use the
<loader-index> element on <loader-table> to specify one or more named indexes to drop.
• enable_all – Enables the dropping of all deferrable indexes for this specific, named staging table.

The following example illustrates a possible configuration.

<loader before-gen-ids-callback-degree-of-parallelism="6"
before-insert-select-callback-degree-of-parallelism="6"
after-insert-select-callback-degree-of-parallelism="6"
insert-select-degree-of-parallelism="6"
fk-enable-degree-of-parallelism="6" row-counts-degree-of-parallelism="6"
drop-deferrable-indexes="enable">
<loader-table name="cc_transactionid" drop-deferrable-indexes="enable">
<loader-index keycolumns="TID"/>
</loader-table>
</loader>

Notice that for the configuration shown in the code sample:

• ClaimCenter disables drop-deferrable-indexes for all staging tables at the global <loader> configuration
level.
• ClaimCenter enables drop-deferrable-indexes for a specific table (cc_transactionid) at the <table-
loader> configuration level, for the specified index (TID).

See also
• System Administration Guide

Configuring database compression

It is possible to configure compression for the databases that you use with your Guidewire applications.
Compression reduces the size of the database.
• The advantage of compression is reduced cost for storage and backups. Compression can also increase
performance by effectively making the database buffer caches larger.
• The disadvantage of compression is that the database requires more CPU time to compress and decompress data.
However, queries that require either a table scan or a full index scan require fewer physical and logical reads
because more rows fit on a single data page.
Consult with Guidewire Support about whether database compression can improve the overall performance of your
ClaimCenter implementation.
Note: A full discussion of table and index compression is beyond the scope of this document. Refer to
documentation from your database vendor for details about compression options.

Configuring compression for Oracle

You can configure Oracle compression options for ClaimCenter by using the <ora-db-ddl> element of database-
[Link]. Compression options can apply to the entire database, to specific tables, or to specific indexes of a
table.
28 chapter 2: Preparing a ClaimCenter environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

Note: The compression settings examples in the following topics merely demonstrate the syntax to use
to configure compression. Do not use these examples as formal guidelines for compression settings for
your environment.

Oracle database compression

You can specify Oracle database compression options for ClaimCenter by using the <ora-compression> element of
<ora-db-ddl> in [Link]. The <ora-compression> element has the following syntax:

<database>
...
<upgrade>
<ora-db-ddl>
<ora-compression table-compression="NONE|BASIC|ADVANCED" index-compression="true|false">
</ora-db-ddl>
</upgrade>
</database>

The <ora-compression> element accepts the attributes table-compression and index-compression. You can
specify one or both attributes. Attributes that you specify for <ora-compression> apply to all tables and indexes in
the database.
The values that you can set for these two attributes are described in the topics that follow.

See also
• System Administration Guide

Oracle table compression

You can override options for all tables in the database by setting the table-compression attribute of the <ora-
compression> element to NONE, BASIC or ADVANCED. For general syntax, see the preceding topic.
You can override options for a specific table by adding an <ora-table-compression> element and setting the
table-compression attribute to NONE, BASIC or ADVANCED. The <ora-table-compression> element is contained in
an <ora-table-ddl> element within the <ora-db-ddl> element. For example:

<database>
...
<upgrade>
<ora-db-ddl>
<ora-table-ddl table-name="cc_tableName">
<ora-table-compression table-compression="NONE|BASIC|ADVANCED" />
</ora-table-ddl>
</ora-db-ddl>
</upgrade>
</database>

For the ora-table-compression table-compression attribute:

• A value of NONE specifies that the database or table is not compressed.
• A value of BASIC specifies that the database or table uses Oracle basic compression.
• A value of ADVANCED specifies that the database or table uses Oracle advanced compression.
Note: Oracle advanced compression is part of the Oracle Advanced Compression Option, which
requires a separate license. Refer to Oracle documentation for more information about compression.
The following example specifies advanced compression for the entire database and no compression for the
cc_Activity and cc_Workflow tables.

<database name="ClaimCenterDatabase" dbtype="oracle">

...
<upgrade>
<ora-db-ddl>
<ora-compression table-compression="ADVANCED" />
<ora-table-ddl table-name="cc_Activity">
<ora-table-compression table-compression="NONE" />
</ora-table-ddl>

Preparing a ClaimCenter environment 29

Guidewire ClaimCenter 10.0.0 Installation Guide

<ora-table-ddl table-name="cc_Workflow">
<ora-table-compression table-compression="NONE" />
</ora-table-ddl>
</ora-db-ddl>
</upgrade>
</database>

See also
• System Administration Guide

Oracle index compression

You can set the index-compression attribute of the <ora-compression> and <ora-index-ddl> elements to true
or false.
An index-compression value of true specifies:
• Compression for all columns but the last for unique indexes
• Compression for all columns for non-unique indexes
Depending on which element you set, you can override compression for all indexes in a database, for all indexes on
a specific table, or for specific indexes.
• You can override compression options for all indexes in a database by specifying the index-compression
attribute of the <ora-compression> element. For general syntax, see the example in the preceding topic, “Oracle
database compression” on page 29.
• You can override compression options for all indexes on a specific table by including the index-compression
attribute on the <ora-table-compression> element. For example:

<database>
...
<upgrade>
<ora-db-ddl>
<ora-table-ddl table-name="cc_tableName">
<ora-table-compression index-compression="true|false" />
</ora-table-ddl>
</ora-db-ddl>
</upgrade>
</database>

• You can override options for a specific index by adding an <ora-index-ddl> element within the <ora-table-
ddl> element for the table that has the index. For example:

<database>
...
<upgrade>
<ora-db-ddl>
<ora-table-ddl table-name="cc_tableName">
<ora-index-ddl index-compression="true|false" key-columns="column1,column2" />
</ora-table-ddl>
</ora-db-ddl>
</upgrade>
</database>

Specify an index by setting the key-columns attribute of the <ora-index-ddl> element to a comma-delimited
list of key columns in order. Specify DESC after a column name for descending sort order on that column.
The following example specifies the following overrides:
• Index compression for the entire database
• No compression for the cc_Activity index that contains key columns PublicID and Retired in key positions
one and two, respectively.
• No compression for any indexes on the cc_Workflow table.

<database>
...
<upgrade>
<ora-db-ddl>

30 chapter 2: Preparing a ClaimCenter environment

 Guidewire ClaimCenter 10.0.0 Installation Guide

<ora-compression index-compression="true">
<ora-table-ddl table-name="xx_Activity">
<ora-index-ddl key-columns="PublicID,Retired" index-compression="false" />
</ora-table-ddl>
<ora-table-ddl table-name="xx_Workflow">
<ora-table-compression index-compression="false" />
</ora-table-ddl>
</ora-db-ddl>
</upgrade>
</database>

IMPORTANT Oracle spatial indexes are not compressible. If you use the key-columns attribute to
specify a spatial index to compress, ClaimCenter reports an error. If the index is implied to be
compressed by the compression configuration of the database or table, ClaimCenter ignores the
compression setting for a spatial index.

See also
• System Administration Guide

Configuring compression for SQL Server

You can configure Microsoft SQL Server compression options for ClaimCenter by using the <mssql-db-ddl>
element of [Link]. Compression options can apply to the entire database, to specific tables, or to
specific indexes of a table.
Note: You must have the Enterprise edition of SQL Server to have the SQL Server compression
feature.
Refer to Microsoft SQL Server documentation for more information about SQL Server compression options.

SQL Server database compression

You can specify SQL Server database compression options for ClaimCenter by using the <mssql-compression>
element of <mssql-db-ddl> in [Link]:

<database>
...
<upgrade>
<mssql-db-ddl>
<mssql-compression table-compression="NONE|PAGE|ROW" index-compression="NONE|PAGE|ROW">
</mssql-db-ddl>
</upgrade>
</database>

The <mssql-compression> element accepts the attributes table-compression and index-compression. You can
specify one or both attributes. Attributes that you specify for <mssql-compression> apply to all tables and indexes
in the database.
Settings for table-compression and index-compression can apply to the entire database, a table, or an index,
depending on the XML element to which the attribute is applied. In general, these values mean the following:
• A value of NONE specifies that the database or table is not compressed.
• A value of PAGE specifies that the database or table uses page-level compression. SQL Server applies page
compression only if the page becomes full. For page compression, the following operations happen in the listed
order:
◦ Row compression
◦ Prefix compression
◦ Dictionary compression
• A value of ROW specifies that the database or table uses row compression. Row compression drastically reduces
the metadata needed for variable-length columns.
Preparing a ClaimCenter environment 31
Guidewire ClaimCenter 10.0.0 Installation Guide

See also
• System Administration Guide

SQL Server table compression

You can override options for a all tables in the database by setting the table-compression attribute of the <mssql-
compression> element to NONE, PAGE, or ROW.
For syntax and a description of the options for table-compression, see the preceding topic.
You can override options for a specific table by adding an <mssql-table-compression> element and setting the
table-compression attribute to NONE, PAGE, or ROW. The <mssql-table-compression> element is contained in an
<mssql-table-ddl> element within the <mssql-db-ddl> element. For example:

<database>
...
<upgrade>
<mssql-db-ddl>
<mssql-table-ddl table-name="cc_tableName">
<mssql-table-compression table-compression="NONE|PAGE|ROW" />
</mssql-table-ddl>
</mssql-db-ddl>
</upgrade>
</database>

The following example specifies row table compression for the entire database, page compression for the
cc_Activity table, and no compression for the cc_Workflow table.

<database name="ClaimCenterDatabase" dbtype="sqlserver">

...
<upgrade>
<mssql-db-ddl>
<mssql-compression table-compression="ROW" />
<mssql-table-ddl table-name="cc_Activity">
<mssql-table-compression table-compression="PAGE" />
</mssql-table-ddl>
<mssql-table-ddl table-name="cc_Workflow">
<mssql-table-compression table-compression="NONE" />
</mssql-table-ddl>
</mssql-db-ddl>
</upgrade>
</database>

See also
• System Administration Guide

SQL Server index compression

ClaimCenter uses a clustered primary key index. Since this index is actually the table data itself, ClaimCenter uses
the compression setting for the table for the primary key index.
The compression setting of a table is not automatically applied to its non-clustered indexes. You must configure
compression settings for indexes separately or in bulk.
• You can override compression options for all indexes in the database by setting the index-compression attribute
on the <mssql-compression> element to NONE, PAGE, or ROW.
For this syntax and a general description of the options for index-compression, see “SQL Server database
compression” on page 31.
• You can override compression options for all indexes on a specific table by setting the index-compression
attribute on the <mssql-table-compression> element. For example:

<database>
...
<upgrade>
<mssql-db-ddl>
<mssql-table-ddl table-name="cc_tableName">

32 chapter 2: Preparing a ClaimCenter environment

 Guidewire ClaimCenter 10.0.0 Installation Guide

<mssql-table-compression index-compression="NONE|PAGE|ROW" />

</mssql-table-ddl>
</mssql-db-ddl>
</upgrade>
</database>

• You can override options for a specific index by adding an <mssql-index-ddl> element within the <mssql-
table-ddl> element for the table that has the index.
◦ Specify an index by setting the key-columns attribute of the <mssql-index-ddl> element to a comma-
delimited list of key columns in order.
◦ Specify DESC after a column name for descending sort order on that column.
For example:

<database>
...
<upgrade>
<mssql-db-ddl>
<mssql-table-ddl table-name="cc_tableName">
<mssql-index-ddl key-columns="column1,column2" index-compression="true|false" />
</mssql-table-ddl>
</mssql-db-ddl>
</upgrade>
</database>

The following example specifies the following:

• Row index compression for the entire database.
• No compression for the cc_Activity index that contains key columns PublicID and Retired in key positions
one and two, respectively.
• Page compression for any indexes on the cc_Workflow table.

<database>
...
<upgrade>
<mssql-db-ddl>
<mssql-compression index-compression="ROW">
<mssql-table-ddl table-name="cc_Activity">
<mssql-index-ddl key-columns="PublicID,Retired" index-compression="NONE" />
</mssql-table-ddl>
<mssql-table-ddl table-name="cc_Workflow">
<mssql-table-compression index-compression="PAGE" />
</mssql-table-ddl>
</mssql-db-ddl>
</upgrade>
</database>

See also
• System Administration Guide

Guidelines for configuring Oracle for ClaimCenter

Guidewire recommends that you implement the guidelines in this topic as you install and configure the Oracle
database server to work with ClaimCenter.
Note: See the Supported Software Components knowledge article for information about which
specific Oracle versions Guidewire supports for ClaimCenter 10.0.0. Visit the Guidewire Community
and search for knowledge article 1005, “Supported Software Components”.
ClaimCenter requires Oracle Locator, which is included with Oracle Multimedia. Refer to Oracle MOS (My Oracle
Support) note How To Verify That Oracle Locator Is Installed (Doc ID 357943.1). Note that ClaimCenter does not
require Oracle Spatial, an extra-cost option that includes all Oracle Locator features plus advanced features for
spatial data.
Preparing a ClaimCenter environment 33
Guidewire ClaimCenter 10.0.0 Installation Guide

Prerequisites to installing ClaimCenter on Oracle

Create a separate user and schema for each Guidewire application. Sharing a schema can result in naming conflicts
for primary key constraints and indexes.
Ensure that your Oracle database is running in an environment that optimizes storage performance while
maintaining storage maintainability. Oracle recommends you use the SAME (Stripe and Mirror Everywhere)
strategy. To learn more about the SAME strategy, consult the following document:
[Link]
You must install an Oracle Java Virtual Machine (JVM) on all Oracle databases hosting ClaimCenter. The only
exception is if the ClaimCenter application locale is English and you only require case-insensitive searches. Ensure
that Oracle initialization parameter java_pool_size is set to a value of above 50 MB.
Configure Oracle to use asynchronous IO. Asynchronous IO significantly simplifies a database’s IO management
while increasing its performance. For performance reasons, tune your operating system to Oracle database
requirements. Oracle provides guidance on tuning your database based on:
• Operating system
• Available memory
• Database release
Consult Oracle documentation and support web site for information on how to tune your database.
The Oracle database supports server-side caching that can help increase ClaimCenter performance. The size of the
Oracle database cache is critical to supporting server-side caching. For internal tests, Guidewire uses a database
cache size of 3.6 GB or more. Consult the Oracle documentation for information on selecting a cache size
appropriate to your server computer’s architecture.
After your database is in production, you cannot easily modify the storage architecture. Guidewire recommends that
you test and tune your database’s storage performance prior to installing ClaimCenter. There are many tools
available for optimizing database performance, including open source tool, IOzone ([Link]).

Prepare an Oracle database for ClaimCenter

About this task

IMPORTANT
Guidewire supports only single-byte character sets that are a strict superset of ASCII, and AL32UTF8 or
UTF8 for Unicode. Use only a supported character set with ClaimCenter. Refer to your Oracle
documentation for a complete list of supported character sets. WE8ISO8859P1 is a single-byte character
set that supports both Western European languages and American English. AL32UTF8 and UTF8 are
Oracle character sets supported for the storage of Unicode data, such as Asian characters.
If using the AL32UTF8 or UTF8 character set, configure the Oracle instance to set
nls_length_semantics to char. Otherwise, the application server will not start.
Note: Oracle recommends that you do not set the nls_length_semantics parameter to
char (due to concerns about third party applications relying on the value being set to
byte), but Guidewire specifically relies on having it set to char. For more details, see
Oracle support MOS Doc ID 144808.1.
Guidewire does not support non-ASCII characters in database schema object names and qualifiers.
Without limitation, these names and qualifiers include table names and column names. If you do not
restrict schema object names and qualifiers to ASCII characters, an exception will result.

Procedure
1. Create a new database instance for ClaimCenter.
Guidewire recommends that you not share the ClaimCenter database with other data or applications.
2. Create one or more tablespaces to support the ClaimCenter logical tablespaces. Guidewire recommends that
you create a separate tablespace for each logical tablespace:
34 chapter 2: Preparing a ClaimCenter environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

Logical Name Usage

ADMIN Stores system parameters.
OP Stores the main ClaimCenter data tables.
TYPELIST Stores system code tables.
INDEX Stores system indexes.
STAGING Stores inbound staging data tables.
LOB Stores off‐row LOB (large object) data. The LOB tablespace is optional. If you do not specify a physical
tablespace for the LOB logical tablespace, then LOB data is stored in the tablespace mapped to the OP
logical tablespace.
ClaimCenter uses the LOB tablespace for new tables only. For an existing configuration in which the
ClaimCenter schema has been created, if you designate an LOB tablespace, ClaimCenter does not move
existing LOB columns to the LOB tablespace. If you add an LOB column to an existing table, ClaimCenter
does not put the column in the LOB tablespace. If you define a new table with LOB data, ClaimCenter
stores the LOB data in the designated LOB tablespace.
See “About Oracle SecureFile LOBs” on page 37.

3. Create a single database user, ccUser, in the ClaimCenter database.

4. Grant ccUser the following permissions:
• alter session
• create procedure
• create sequence
• create session
• create table
• create trigger
• create view
• query rewrite
• select any dictionary
If your users want to view statspack data on the ClaimCenter Info Pages interface, you also need to grant the
ccUser access to Statspack's (perfstat user) tables.
5. Grant quota on all the tablespaces listed in step 2 to the ccUser.
6. Set default tablespace for ccUser to the one being mapped to the OP logical tablespace.
7. (Optional) In a production environment, edit the PATH environment variable and move any Oracle directories
to the end of the variable, after the ClaimCenter directories.
This action prevents potential conflicts with ClaimCenter files as Oracle adds directories to the PATH
environment variable if you run the database and application servers on the same computer.
Note: Guidewire recommends that you do not run database and application servers on the same
computer in a production environment.
8. Test a connection to the database from a database client and verify that all the tablespaces are visible.
9. Define the method you will use to gather Oracle database statistics. Select and configure your choice as
outlined in “Database statistics generation for Oracle databases” on page 35.

Database statistics generation for Oracle databases

There are several different ways in which to generate database statistics in Guidewire ClaimCenter if using an
Oracle database:
• Use the Oracle Autotask infrastructure to manage the task of gathering database table statistics.
• Run ClaimCenter batch processing DBStats periodically to collect database table statics.
You enable the use of each method by setting the value of the useoraclestatspreferences attribute on the
<tablestatistics> element in file [Link].
Preparing a ClaimCenter environment 35
Guidewire ClaimCenter 10.0.0 Installation Guide

Statistics gathering useoraclestatspreferences Description For more

information
Oracle AutoTask true Disable DBStats batch processing and use Oracle
AutoTask to manage the collection of database
statistics.
DBStats batch false (Default) Disable Oracle AutoTask and use DBStats to
processing manage the collection of database statistics.

Note: A change in the value of useoraclestatspreferences takes effect only during an application
upgrade.
If using DBStats batch processing to manage the collection of database statistics:
• Do not execute Oracle dbms_stats manually.
• Manually execute, or schedule, DBStats batch processing.
• Disable the automatic generation of database statistics using Oracle by doing one of the following:
◦ Disable the Oracle AutoTask “auto optimizer stats collection” automated task.
◦ Set the AUTOSTATS_TARGET preference to ORACLE. This action ensures that the automated task gathers
statistics for the Oracle Dictionary only.

Guidewire recommendations for Oracle database installations

• Guidewire recommends that Oracle implementations only update database statistics during quiet periods, such as
weekends or nights, so that these updates do not occur while ClaimCenter is under heavy load. By default,
updating statistics on a table or index invalidates existing query plans related to that table or index.
• Guidewire recommends that Oracle implementations use the NO_INVALIDATE => AUTO_INVALIDATE option
while updating database statistics. This is the default option. This option is also what the Guidewire Database
Statistics batch process uses, unless the configuration parameter DiscardQueryPlansDuringStatsUpdateBatch
is set to true.
Setting NO_INVALIDATE => FALSE to force immediate invalidation of query plans has a high likelihood of
causing issues with concurrent batch updates. Using AUTO_INVALIDATE greatly reduces this risk. Ideally, set the
_optimizer_invalidation_period parameter to a low value (a few minutes) to reduce the time window during
which Oracle might invalidate a plan.

Flush monitoring information after table import

For Oracle, if you want to run the incremental database statistics process after running the table_import -
integritycheckandload command, first flush the monitoring information using the procedure
DBMS_STATS.FLUSH_DATABASE_MONITORING_INFO.

About Oracle resource consumer groups

Note: Use the information in this topic only if you experience slow claim queries. If you do not
experience slow claim queries, you do not need to define a resource consumer group for claim queries.
Oracle provides resource plans and consumer groups to handle resources in the database. One useful feature is to
cancel a query based on the execution time. You can configure ClaimCenter to switch to a resource consumer group
that you define to perform claim searches. You can set this resource consumer group to have a time limit and cancel
SQL operations for claim searches that exceed the time limit.
ClaimCenter saves the initial resource consumer group that it detects during server start up and reverts to that group
following the claim query.
The requirements for using Oracle resource consumer groups for claim queries are:
• The db-resource-mgr-cancel-sql attribute is set on element <oracle-settings> in [Link]
to a resource consumer group defined in Oracle, for example:

<database name="ClaimCenterDatabase" dbtype="oracle">

...

36 chapter 2: Preparing a ClaimCenter environment

 Guidewire ClaimCenter 10.0.0 Installation Guide

<oracle-settings db-resource-mgr-cancel-sql="" />

...
</database>

• The Oracle resource manager plan is set at the system level.

• User ccUser has privileges to switch between the two resource groups.
ClaimCenter checks these conditions at server start up.

See also
• System Administration Guide

About Oracle SecureFile LOBs

ClaimCenter supports Oracle SecureFile LOBs for unstructured data. To configure ClaimCenter to use SecureFile
LOBs, modify the <database> block in [Link]. You can specify to use SecureFile LOBs for all
LOBs in the database or for specific tables. You can also configure whether to use caching and the LOB type. The
LOB type can be BASIC, SECURE, or SECURE_COMPRESSED. If not specified otherwise ClaimCenter uses SecureFile
LOBs.
To specify to use basic file LOBs for all LOBs in the database, add the following to the <database> block.

<ora-db-ddl>
<ora-lobs type="BASIC" caching="true|false"/>
</ora-db-ddl>

Use the following syntax in the <database> block to specify the use of compressed SecureFile LOBs for all LOBs
in the database.

<ora-db-ddl>
<ora-lobs type="SECURE_COMPRESSED" caching="true|false"/>
</ora-db-ddl>

Use the following syntax in the <database> block to specify the use of compressed SecureFile LOBs for all LOBs
on a particular table.

<ora-db-ddl>
<ora-table-ddl name="cc_tablename">
<ora-lobs type="BASIC" />
</ora-table-ddl>
</ora-db-ddl>

If you configure any LOBS to be SecureFile LOBs, and:

• You configure the LOB tablespace, you must manage the LOB tablespace with Automatic Segment Space
Management.
• You do not configure the LOB tablespace, you must manage the ADMIN, OP and STAGING tablespaces with
Automatic Segment Space Management.
Use the following syntax in the <database> block to specify the use of caching for LOBs

<ora-db-ddl>
<ora-lobs caching="true" .../>
</ora-db-ddl>

ClaimCenter does not automatically convert LOBs if you change the configuration. You can convert the tables in
Oracle and then update the ClaimCenter configuration. ClaimCenter then uses the updated configuration for new
objects.
Refer to Oracle documentation for information about basic file, SecureFile, and compressed SecureFile LOBs.
Preparing a ClaimCenter environment 37
Guidewire ClaimCenter 10.0.0 Installation Guide

See also
• System Administration Guide

About table partitioning for Oracle

Table hash partitioning can improve performance of queries on large tables. To enable hash partitioning on a table,
add the <ora-table-hash-partitioning> element to the <ora-table-ddl> block of <ora-db-ddl> in database-
[Link]. For example:

<database name="ClaimCenterDatabase" dbtype="oracle">

...
<upgrade>
...
<ora-db-ddl>
<ora-table-ddl name="Table Name">
<ora-table-hash-partitioning hash-column="column name" num-partitions="number"/>
</ora-table-ddl>
</ora-db-ddl>
</upgrade>
</database>

If a keyable table is partitioned, by default, ClaimCenter uses the ID column as the hash column. You can specify a
different column by using the hash-column attribute on <ora-table-hash-partitioning>. For non-keyable
tables, the hash-column attribute is required.
If a keyable table is partitioned, ClaimCenter also partitions the primary key index and the index on PublicID. This
index is on PublicID and Retired if the table is for a retireable entity.
By default, ClaimCenter uses 128 partitions. You can override this number by defining a num-partitions attribute
on <ora-table-hash-partitioning>.
Note: ClaimCenter creates partitions only if creating a table or index. ClaimCenter does not modify
existing tables or indexes. If an upgrade process drops and rebuilds a table, ClaimCenter partitions the
table if the table is configured to be partitioned. The schema verifier detects and flags the table if a
table is configured as partitioned but is not, or if it is not configured as partitioned but is partitioned.

See also
• System Administration Guide

About index partitioning for Oracle

Index partitioning can improve performance of queries in large tables. You can use the DDL configuration element
<ora-index-partitioning> in [Link] to specify Oracle index partitioning.
The <ora-index-partitioning> element is a subelement of <ora-index-ddl>, which is itself a subelement of
<ora-table-ddl>. For example:

<database name="ClaimCenterDatabase" dbtype="oracle">

...
<upgrade>
...
<ora-db-ddl>
<ora-table-ddl name="Table Name">
<ora-index-ddl key-columns="column1,column2,...">
<ora-index-partitioning
partitioning-type="LOCAL|HASH|RANGE"
// The next two elements apply only to the RANGE partitioning type.
range-partitioning-column-list="column1,column2,...">
<ora-index-range-partition value-list=
"number1|’string1’,number2|’string2’,..."/>
<ora-index-range-partition value-list=
"number1a|’string1a’,number2a|’string2a’,..."/>
...
</ora-index-partitioning
</ora-index-ddl>
</ora-table-ddl>

38 chapter 2: Preparing a ClaimCenter environment

 Guidewire ClaimCenter 10.0.0 Installation Guide

</ora-db-ddl>
</upgrade>
</database>

The use of the partitioning-type attribute is mandatory. This attribute takes one of the following values.

LOCAL The only allowed attribute is the partitioning-type attribute. ClaimCenter partitions the index as the table is parti‐
tioned.
HASH ClaimCenter hash‐partitions the index globally on the leading key of the index by using the number of partitions speci‐
fied or the default number 128.
RANGE ClaimCenter range‐partitions the index by using the range-partitioning-column-list columns and the values speci‐
fied in the ora-index-range-partition elements under this element.
The range-partitioning-column-list element takes a comma‐delimited list of columns to use for range‐
partitioning this index. This element requires the definition of one or more ora-index-range-partition elements.
The ora-index-range-partition defines the value range for each partition in value-list. It defines a comma‐
delimited, ordered list of literal values corresponding to the column list defined in range-partitioning-column-list.
Place any single String value inside single quotation marks. Surround the entire list of values by double quotation
marks.
ClaimCenter uses these defined values in the SQL clause VALUES LESS THAN(value_list). Do not specify the last
range, which is always VALUES LESS THAN (MAXVALUE[, MAXVALUE, ...]).
Note: ClaimCenter does not support the use of a date column for range‐partitioning of indexes.

For example, the following database block defines an index range partitioning that uses five partitions and two
column values per partition. The final partition, created automatically by ClaimCenter, uses the following values for
the two columns defined in range-partitioning-column-list:
• ADDRESSBOOKUID – At least 'ab:830' and less than MAXVALUE
• RETIRED – At least 0 and less than MAXVALUE

<database name="ccDatabase" dbtype="oracle">

...
<upgrade degree-parallel-ddl="1" verifyschema="true">
<ora-db-ddl>
<tablespaces admin="cc_ADMIN" index="cc_INDEX" op="cc_OP"
staging="cc_STAGING" typelist="cc_TYPELIST"/>
<ora-table-ddl table-name="cc_CLAIM">
<ora-index-ddl key-columns="ADDRESSBOOKUID, RETIRED, SUBTYPE, ID">
<ora-index-partitioning partitioning-type="RANGE"
range-partitioning-column-list="ADDRESSBOOKUID, RETIRED">
<ora-index-range-partition value-list="'ab:20', 0"/>
<ora-index-range-partition value-list="'ab:40', 0"/>
<ora-index-range-partition value-list="'ab:60', 0"/>
<ora-index-range-partition value-list="'ab:830', 0"/>
</ora-index-partitioning>
</ora-index-ddl>
</ora-table-ddl>
</ora-db-ddl>
</upgrade>
</database>

ClaimCenter Example
The following definition under <ora-db-ddl> enables you to create partitioned indexes for claim searches that
specify a ClaimContact as a search criterion and are taking too long:

<ora-table-ddl table-name="CC_CLAIMCONTACT">
<ora-index-ddl key-columns="ClaimantFlag, PersonLastNameDenorm, PersonFirstNameDenorm,
Retired, ClaimID, ID">
<ora-index-partitioning partitioning-type="RANGE"
range-partitioning-column-list="ClaimantFlag">
<ora-index-range-partition value-list="1"/>
</ora-index-partitioning>
</ora-index-ddl>
</ora-table-ddl>

Preparing a ClaimCenter environment 39

Guidewire ClaimCenter 10.0.0 Installation Guide

There would be two range partitions. One partition would be for values of ClaimantFlag that are less than 1, and
the other for values of ClaimantFlag that are at least 1 and less than MAXVALUE.
This example would support indexes like the following index added to [Link], which supports search
by Claimant claim role:

<index desc="Covering index for search by person last name"

expectedtobecovering="true"
name="ClmConLastFirstNCl"
trackUsage="true" unique="true">
<indexcol keyposition="1" name="ClaimantFlag"/>
<indexcol keyposition="2" name="PersonLastNameDenorm"/>
<indexcol keyposition="3" name="PersonFirstNameDenorm"/>
<indexcol keyposition="4" name="Retired"/>
<indexcol keyposition="5" name="ClaimID"/>
<indexcol keyposition="6" name="ID"/>
</index>

See also
• System Administration Guide

About Oracle date interval partitioning

It is possible to configure ClaimCenter to use Oracle partitioning by date intervals.
To configure date interval partitioning on a table, add an <ora-table-date-interval-partitioning> element
within <ora-table-ddl>. The <ora-table-ddl> element is a subelement of <ora-table-ddl> in the <database>
element of [Link]. The <ora-table-date-interval-partitioning> element has following
attributes:
• Use the datecolumn attribute to specify a non-nullable timestamp column for ClaimCenter to use to determine
partition boundaries.
• Use the interval attribute to specify the period of time for each partition. You can set interval to DAILY,
WEEKLY, MONTHLY, QUARTERLY, or YEARLY.
For example:

<database>
...
<ora-db-ddl>
<ora-table-ddl table-name="cc_table">
<ora-table-date-interval-partitioning datecolumn="updateTime" interval="MONTHLY">
</ora-table-ddl>
</ora-db-ddl>
</database>

ClaimCenter stores partitioned data in the operational tablespace.

See also
• System Administration Guide

Guidelines for configuring SQL Server for ClaimCenter

Guidewire recommends that you implement the guidelines in this topic as you install and configure the SQL Server
database server to work with ClaimCenter.
Guidewire does not support Windows Integrated Security as an option while connecting to SQL Server.

40 chapter 2: Preparing a ClaimCenter environment

 Guidewire ClaimCenter 10.0.0 Installation Guide

Note: See the Supported Software Components knowledge article for information about which
specific SQL Server versions Guidewire supports for ClaimCenter 10.0.0. Visit the Guidewire
Community and search for knowledge article 1005, “Supported Software Components”.

Prerequisites to installing ClaimCenter on SQL Server

Create a separate SQL Server database for each Guidewire application. Sharing a database can result in naming
conflicts for primary key constraints and indexes.
ClaimCenter requires that the collation of the SQL Server database specifies CI, or case-insensitive. The case-
sensitivity setting affects table and column names, and ClaimCenter requires these names to be case-insensitive.
During startup, ClaimCenter checks that the SQL Server database is case-insensitive.
ClaimCenter does not support non-ASCII characters in table names, column names, or other schema object names
and qualifiers. Restrict SQL Server database schema object names and qualifiers to ASCII characters.
Decide whether to store other character data in single-byte format in varchar columns, or Unicode multi-byte
format stored in nvarchar columns. If using Unicode, such as for Japanese or Chinese, set the unicodecolumns
attribute to true on the <sqlserver-settings> subelement of the <database> element in [Link].
Then, during the creation of database tables while starting the application server for the first time, ClaimCenter
creates all character columns with the nvarchar datatype.
The collation setting specifies sorting and comparison rules, and also the code page to use for single-byte data.
Microsoft still supports SQL Server collations (those that start with SQL_) in addition to Windows collations, but
recommends using a Windows collation. Guidewire also recommends that you use a Windows collation. Choose the
collation setting carefully. Refer to Collation and International Terminology at the following location for a full
discussion:
[Link]
The version of Windows being used for the database and application server is a factor. Some newer collations, such
as Japanese_Bushu_Kakusu_100, are only available on Windows 2007 or later and not on Windows 2003.
Creating a SQL Server database with files of sufficient size and parameters is important to future performance and
maintenance. A basic discussion can be found online in a Microsoft SQL Server topic “Designing Databases” at the
following location:
[Link]
For production systems, Guidewire strongly recommends that you pre-allocate disk space rather than using the SQL
Server autogrowth feature. As a general guideline, estimate how big your database might grow in one year and add
20%. Then, allocate enough total file space for this size. Monitor the size of the database and add space during
scheduled periods of lower activity. Set the maximum file size to be less than the size of the disk, so that the disk
does not fill up.
For your production database, work with your SAN (Storage Area Network) engineers early in implementation to
deliver production-realistic performance.
Guidewire recommends that you not share the SQL Server instance on which you are running ClaimCenter with
other data or applications.

See also
• System Administration Guide

Install ClaimCenter on SQL Server

Procedure
1. Configure SQL Server.
See “Configure SQL Server in management Studio” on page 42.
2. Create a database for ClaimCenter.
See “Create a ClaimCenter database in SQL Server” on page 42.
3. Modify the [Link] file so that the ClaimCenter application correctly points to the database.

Preparing a ClaimCenter environment 41

Guidewire ClaimCenter 10.0.0 Installation Guide

4. Restart the application server and test by opening ClaimCenter in a browser window.
See “Configuring a database connection” on page 60.
See “Deploying to the application server” on page 78.

Configure SQL Server in management Studio

Procedure
1. Open SQL Server Management Studio.
2. In the Object Explorer, right-click the server node you plan to use for ClaimCenter and choose Properties.
Typically, the node is the same as computer name.
The Server Properties dialog opens.
3. Select the Security page and check SQL Server and Windows Authentication Mode.

WARNING ClaimCenter does not run if authentication is set to Windows Authentication Mode
only.

4. Select the Memory page.

5. Adjust the Maximum Server Memory to use at least 200 MB.
6. With a dedicated host computer running SQL Server, Microsoft recommends that you use the default settings
and use SQL Server to manage memory.
Consult the following Microsoft documentation or an in-depth discussion of memory options.
[Link]
Note: Setting the maximum server memory to a specific value can cause performance problems.
7. Click OK to close the dialog.
8. Right-click the SQL Server Agent node and select Properties.
9. Select the General page.
10. Check Autostart SQL Server if it stops unexpectedly.
11. Click OK to close the dialog.

Create a ClaimCenter database in SQL Server

About this task

Guidewire requires that you follow these guidelines to create and configure an instance of a SQL Server database for
ClaimCenter.

IMPORTANT If you plan to create additional database instances to support multiple ClaimCenter
environments or other Guidewire products, consider applying the changes in the following procedure
to the model database. Use the model database as a template for the additional database instances.
Before you edit the model database, create a backup of the database.

Note: Guidewire recommends that you not share the ClaimCenter database with other applications.
Note: It is possible for a database administrator to write a CREATE DATABASE SQL statement to create
the database also.

Procedure
1. If not already open, open SQL Server Management Studio.
2. If creating a new database, do the following. Otherwise, skip to step 3:
a. Right-click the Databases node and select New Database.
b. Enter a database name in the New Database dialog.
c. Click OK.
d. Skip to step 4.
42 chapter 2: Preparing a ClaimCenter environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

3. If modifying the model database, do the following:

[Link] Databases→System Databases,
b. Right-click model and select Properties,
c. Continue to step 4.
4. Optionally, create one or more filegroups to support the ClaimCenter logical tablespaces from the Filegroups
page.
See “Create filegroups in SQL Server” on page 44 for details.
5. Select the Options page.
a. Choose your database collation if not using the SQL Server server default. The only requirement is that it
is a CI (case-insensitive) collation.
b. Verify that the values for Auto Create Statistics and Auto Update Statistics are both set to True.
During start up, ClaimCenter checks that these properties are set to True and validates that the SQL
Server database is case-insensitive.
c. Verify that the value of Auto Shrink is set to False.
Note: If the value of this options is set to True, poor performance can result.
d. Click OK.
6. Right-click Security and select New→Login.
a. On the Login - New dialog, select SQL Server Authentication if not already selected.
b. Specify a password and password policy options.
c. Click OK.
7. In Object Explorer, expand the database and open Security→Users.
a. Right-click Users and select New User.
b. Enter ccUser for the User name.
c. Enter the Login name that you created earlier.
d. Select db_owner in both Schemes owned by this user and Database role membership panels.
This action grants ownership of the ClaimCenter database to ccUser.
e. Click OK.
8. Grant the ccUser the following permissions on each ClaimCenter data management view:
• view server state
• view database state
See “Grant Guidewire Data Management view permissions to ccUser” on page 44 for details.
9. Disable the SQL Server autogrowth feature in a production system.
See “Disable the SQL Server autogrowth feature” on page 45 for details.
10. Set the READ_COMMITTED_SNAPSHOT option to on.
ClaimCenter checks for this condition during application start up.
See “Set the READ_COMMITTED_SNAPSHOT option” on page 45 for details.
Note: There is no need to save the READ_COMMITTED_SNAPSHOT query that sets this value.
11. Close SQL Server Management Studio.

About filegroups in SQL Server

You can optionally create one or more filegroups to support the ClaimCenter logical tablespaces. If you choose to
use filegroups, create a separate filegroup for each logical tablespace. As you configure the ClaimCenter database
connection, you can map the filegroups you create to the ClaimCenter internal logical tablespaces.
For the filegroups, it is possible to use either the same names as the logical tablespace names (with one exception) or
to use entirely different names. However, do not use INDEX as a filegroup name. INDEX is a reserved name on SQL
Server, so it is not possible to map the logical tablespace INDEX to a physical filegroup of the same name.
Preparing a ClaimCenter environment 43
Guidewire ClaimCenter 10.0.0 Installation Guide

See also
• “Configuration options for SQL Server filegroups” on page 62
• “Create filegroups in SQL Server” on page 44

Create filegroups in SQL Server

Before you begin

Review the information in “About filegroups in SQL Server” on page 43 before proceeding with this task.

Procedure
1. If not already open, open SQL Server Management Studio.
2. Select the Filegroups page.
3. Create the following file groups:

Logical Name Usage

ADMIN Stores system parameters.
OP Stores the main ClaimCenter data tables.
TYPELIST Stores system code tables.
INDEX Stores system indexes.
STAGING Stores inbound staging data tables.
LOB Stores off‐row LOB (large object) data. The LOB filegroup is optional. If you do not specify a filegroup for
the LOB logical tablespace, then ClaimCenter stores the LOB data in the filegroup mapped to the OP logi‐
cal tablespace.
ClaimCenter uses the LOB filegroup for new tables only. For an existing configuration in which the
ClaimCenter schema already exists:
• If you designate an LOB filegroup, ClaimCenter does not move existing LOB columns to the LOB
filegroup.
• If you add an LOB column to an existing table, ClaimCenter does not put the column in the LOB
filegroup.
• If you define a new table with LOB data, ClaimCenter stores the LOB data in the designated LOB
filegroup.

Grant Guidewire Data Management view permissions to ccUser

About this task

ClaimCenter supports several different data management pages for performance analysis of the application. To use
these pages, you must grant the ccUser the following permissions on each ClaimCenter data management view:
• view server state
• view database state
The data management views all start with a sys.dm_ prefix.

Procedure
1. If not already open, open SQL Server Management Studio.
2. In Object Explorer, right-click the database and select Properties.
3. Select the Permissions page.
4. Select ccUser.
5. Select the check box to grant view database state permission.
6. Click OK.
44 chapter 2: Preparing a ClaimCenter environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

7. Right-click the server and select Properties.

8. Select the Permissions page.
9. Select the login associated with ccUser.
10. Select the check box to grant view server state permission.
11. Select the check box to grant create any database permission.
This permission allows the gwb dropDb command to recreate the database.
12. Click OK.

Disable the SQL Server autogrowth feature

About this task

Guidewire recommends that you do not use the SQL Server autogrowth feature in a production system. Instead,
monitor the size of your database and increase the size of the database files as needed during periods of lower
activity. SQL Server enables the autogrowth feature by default. You need to disable this feature manually.

Procedure
1. If not already open, open SQL Server Management Studio.
2. Right-click the database and select Properties.
3. Select the Files page.
a. For each database file, click … in the Autogrowth column.
b. Click the check box for Enable Autogrowth to deselect it.
c. Click OK.
4. Repeat the previous step for each database file.
5. Click OK on the Database Properties screen.

Set the READ_COMMITTED_SNAPSHOT option

About this task

ClaimCenter requires that the READ_COMMITTED_SNAPSHOT option be set to ON. ClaimCenter checks for this
condition during application start up.

IMPORTANT The use of READ_COMMITTED_SNAPSHOT greatly increases resource requirements on the

tempdb database. Set tempdb to grow in 10% increments, and provide sufficient disk space for tempdb
to grow substantially. You can improve performance if you dedicate separate I/O resources to tempdb.

Procedure
1. In SQL Server Management Studio, click New Query.
2. In the query pane, enter:

ALTER DATABASE dbname

SET READ_COMMITTED_SNAPSHOT ON
WITH ROLLBACK IMMEDIATE
GO

3. Click Execute.
SQL Server Management Studio shows you that the command completed successfully.

About index partitioning for SQL Server

Index partitioning can improve performance of queries in large tables. The partition-scheme attribute of the
<mssql-index-ddl> element defines the partition scheme to use for the index. For example:
Preparing a ClaimCenter environment 45
Guidewire ClaimCenter 10.0.0 Installation Guide

<database name="ClaimCenterDatabase" dbtype="sqlserver">

...
<upgrade>
...
<mssql-db-ddl>
<mssql-table-ddl name="Table Name">
<mssql-index-ddl partition-scheme="partition scheme" />
</mssql-table-ddl>
</mssql-db-ddl>
</upgrade>
</database>

Define the partition scheme before starting ClaimCenter with the partition scheme attribute set. The referenced
partition scheme in the configuration must exist, or ClaimCenter reports a configuration error during startup.
Whenever you partition a SQL Server index, that index is the clustering index for the table. Without a partition
scheme defined, the clustering index for a ClaimCenter table is the primary key index.
The partition scheme is treated as a filegroup during index creation, and the SQL Server data space system catalog
reports it almost the same as a filegroup.
The ClaimCenter database schema verifier checks that an index and the associated table are stored in the partition
scheme configured in [Link].
Refer to Microsoft documentation for information about how to create SQL Server partition schemes.

See also
• System Administration Guide

Final SQL Server tests

Before continuing with other installation tasks, perform the following tests on your SQL Server installation:
• Check that your SQL Server environment is correct.
• Test that you can connect to the database using the ccUser credentials.
• Ensure that SQL Server starts automatically as the server starts.
• To test if your database is starting automatically, reboot your server and attempt to access the database from a
client.

Development workstation requirements

Each developer workstation is a contained environment that includes your company’s Guidewire applications and
the components needed to configure it. Guidewire recommends that the development workstation and environment
meet requirements beyond end-user workstations.
Guidewire recommends high-performance I/O systems for development, such as RAID-0 and SCSI or SSD disks.
Studio is a high I/O application. Installation of software that slows the I/O system, such as encryption or continuous
virus scans, can handicap development productivity.
Note: See the Supported Software Components knowledge article for development workstation system
requirements for ClaimCenter 10.0.0. Visit the Guidewire Community and search for knowledge
article 1005, “Supported Software Components”.

Web client information

ClaimCenter is a web application accessed through a web browser.

46 chapter 2: Preparing a ClaimCenter environment

 Guidewire ClaimCenter 10.0.0 Installation Guide

Note: See the Supported Software Components knowledge article for client system requirements for
ClaimCenter 10.0.0. Visit the Guidewire Community and search for knowledge article 1005,
“Supported Software Components”.

Levels of Guidewire support for web browsers

Guidewire has graded levels of support for web browsers. The following list describes the various grades of support.

Full Guidewire successfully completed functional testing and performance tuning for the browser and fully supports
it.
Partial Guidewire completed some testing for the browser and found significant functional or performance issues that
Guidewire could not resolve. The browser might have a known issue that the browser vendor has not
committed to resolving. Browsers with partial support also include browsers that have not yet made it past
quality assurance but that Guidewire determines might be fine to use. For example, a newer version of a fully
supported browser could be partially supported until Guidewire can fully test the new version. The partial
support grade functions largely as a staging area while Guidewire verifies all facets of support.
Unsupported These are browsers that have significant functional or performance issues. Guidewire does not support any
browser that does not fully support HTML5 and CSS3. Other less commonly used browsers, such as Opera or
Dolphin, could be unsupported because Guidewire has not tested them due to a lack of demand. The
unsupported grade functions as a collection of browsers that are unlikely to get any support in the medium to
long term.

Enable DOM storage in Internet Explorer

About this task

To preserve ClaimCenter user preferences between browser sessions, Guidewire requires that DOM storage be
enabled in Internet Explorer. Microsoft enables DOM storage by default. However, if DOM storage is disabled,
ClaimCenter displays the following message after you log into ClaimCenter:
Browser DOM Storage disabled: User preferences will not be persistent after page refresh in this browser version.

Procedure
1. In Internet Explorer, press Alt to open the menu.
2. Click Tools→Internet options.
3. Click Advanced.
4. Under Security, select the Enable DOM Storage check box.
5. Click OK.

Installing Java
The ClaimCenter application server and Guidewire Studio require the use of a JVM (Java Virtual Machine).

Supported Java version

The version of the JVM depends on the servlet container and operating system on which the application server runs.
See the Supported Software Components knowledge article for information on specific version requirements. Visit
the Guidewire Community and search for knowledge article 1005, “Supported Software Components”.

IMPORTANT Production environments must use a 64-bit operating system and 64-bit JVM.

To use a 64-bit Oracle JDK for development, add the startup parameter -XX:+UseCompressedOops to the JVM.
Preparing a ClaimCenter environment 47
Guidewire ClaimCenter 10.0.0 Installation Guide

By default, Oracle JVMs provide both a client and a server mode. Guidewire supports only the server mode as it
yields much higher performance. How you set server mode depends on your application server:
• If using Oracle JVM with Tomcat, then add the -server flag to CATALINA_OPTS.
• If using Oracle JVM with WebLogic, then add the -server flag as an argument while launching the WebLogic
start script.
• If using the IBM JVM with WebSphere, the server mode is enabled by default. You probably do not need to
change any settings.
Refer to the following web site for information on downloading the JDK:

[Link]

The Dynamic Code Evolution Virtual Machine

The Dynamic Code Evolution Virtual Machine (DCEVM) is a modified version of the Java HotSpot Virtual
Machine (VM). The DCEVM supports any redefinition of loaded classes at runtime. You can add and remove fields
and methods and make changes to the super types of a class using the DCEVM. The DCEVM is an improvement to
the HotSpot VM, which only supports updates to method bodies.
Guidewire strongly recommends the use of the DCEVM for development in the QuickStart environment. Guidewire
does not support the DCEVM for other application servers or in a production environment. Performance of the Java
Virtual Machine (JVM) might be impacted by the addition of the DCEVM.
See the Supported Software Components knowledge article for information about which specific DCEVM version
Guidewire supports for ClaimCenter 10.0.0. Visit the Guidewire Community and search for knowledge article 1005,
“Supported Software Components”.

See also
• [Link]

Verify JVM not running

About this task

Shut down any applications or processes that might be using the JVM before you run the DCEVM installer. Ensure
that there are no [Link] processes running.

Procedure
1. On Windows, press Ctrl+Alt+Delete.
2. Click Start Task Manager.
3. Click the Processes tab.
4. Check to see that the list of processes does not include [Link]. If it does, close any programs that might be
using the JVM.

Install the DCEVM

Before you begin

Perform the steps listed in “Verify JVM not running” on page 48.

Procedure
1. Download the DCEVM installer from [Link]
See the Supported Software Components knowledge article for information about which specific DCEVM
version Guidewire supports for BillingCenter 9.0.5. Visit the Guidewire Community and search for knowledge
article 1005, “Supported Software Components”.
48 chapter 2: Preparing a ClaimCenter environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

2. Note: You must have administrator priviledges for this step. In Windows, Right-click [Link]
and click Run as administrator to open a command window with administrator priviledges.
In the directory that holds the DCEVM installer you downloaded, run the following command: java -jar
[Link].
The Dynamic Code Evolution VM Installer starts.
3. In the Dynamic Code Evolution VM Installer window, select the JDK that you are using for ClaimCenter
development.
4. Click Replace by DCEVM.
The the Dynamic Code Evolution VM Installer does the following:
• It replaces %JAVA_HOME%/jre/bin/client/[Link] and %JAVA_HOME%/jre/bin/server/[Link].
• It copies the original [Link] files and names these files [Link].
• The entry in the Replaced by DCEVM? column changes to Yes.
5. Click the X to close the the Dynamic Code Evolution VM Installer.
6. After completing the DCEVM installation, confirm the installation by running the following command:
java -version
The output lists the Java HotSpot(TM) 64-Bit Server VM (version) after the Java version information.

Setting environment variables

After you install Java, set environment variables so that ClaimCenter can locate them. You might also need to set an
environment variable for your application server.
Make these environment variables available in the user environment in which you plan to run ClaimCenter. The
following table lists the variables to set for the different systems:

System Variable Example Values and Notes

Application server JAVA_HOME C:\Program Files\Java\jdk1.8.0_92
(all) The Java installer sets JAVA_HOME automatically, but Guidewire recommends that you
verify that the installer set the value correctly.
Application server CATALINA_OPTS Specifies the minimum and maximum memory used by Tomcat. For example, the follow‐
(Tomcat) ing value for CATALINA_OPTS sets the direct JVM memory allocations to 1024 MB (initial‐
ly) and 1024 MB (maximum), and also allocates 128 MB of background processing mem‐
ory:
-server -Xms1024M -Xmx1024M
Make your maximum JVM memory allocation (the –Xmx setting) the maximum likely
available memory on the server. Guidewire tests have shown that performance of gar‐
bage collections are best if the -Xms and -Xmx are set to the same value. See “Operating
system limits on heap size” on page 18 for a detailed discussion.
For more information on configuration options, run the following command to view the
built‐in help for Java command line options:
java –X

Development en‐ JAVA_HOME C:\Program Files\Java\jdk1.8.0_92

vironment, admin‐
istration tools

Check environment variables

About this task

Check that you established your ClaimCenter environment correctly. Open a new command prompt and display your
environment variables to check them.
Preparing a ClaimCenter environment 49
Guidewire ClaimCenter 10.0.0 Installation Guide

Procedure
1. Open a command prompt.
2. Run the following command:
set
The command lists the operating system environment variables

Documenting your environment

After establishing your environment, take some time to document it in preparation for installing ClaimCenter. Enter
your configuration values in the following tables:

Database Configuration Value

Database Name
Server Name
Database server port
ClaimCenter database user name
Cache size
Block size

Application Server Environment Variables Value

The user name application runs under
ANT_HOME

JAVA_HOME

CATALINA_HOME

CATALINA_OPTS

50 chapter 2: Preparing a ClaimCenter environment

chapter 3

Installing a ClaimCenter development

environment

The development environment enables you to customize ClaimCenter and rapidly view and test your
customizations. Do not use a development environment for production.
IMPORTANT This topic only provides information for installing a ClaimCenter development
environment. To install a production environment, first review “Preparing a ClaimCenter
environment” on page 15 and then proceed to “Installing a ClaimCenter production environment” on
page 59.

Overview of development environment options

ClaimCenter supports a variety of development environment options depending on your business needs. You can:
• Perform development work using the default bundled QuickStart application server.
• Work on the local configuration files, repackage the configured application into a WAR or EAR file, and deploy
it to a local or remote application server. Because you must repackage and redeploy a WAR or EAR file after
making configuration changes, Guidewire does not recommend this approach for a development environment.
Use the QuickStart method if you want to install a development or demonstration ClaimCenter environment quickly
using the fewest steps.

See also
• “Installing the QuickStart development environment” on page 52
• “Installing ClaimCenter on JBoss in a production environment” on page 78
• “Installing ClaimCenter on WebSphere in a production environment” on page 83
• “Installing ClaimCenter on WebLogic in a production environment” on page 81

Using multiple development instances

Occasionally, you might want to connect from one machine to multiple ClaimCenter instances running on the same
physical or virtual server. In this case, the port number differs for each instance, but the IP address and domain name
are the same between the two application instances.
Most containers hold the session ID in a cookie. The container gives the cookie a default name and associates the
cookie with a host name or IP address and a path. If you run multiple application servers for the same application,
Installing a ClaimCenter development environment 51
Guidewire ClaimCenter 10.0.0 Installation Guide

each one generates a session cookie with the same host name and path. The session cookie does not include the port
number. Therefore, if you log into one application instance, the browser ends the session with any other application
servers having the same host and path, even if port numbers differ.
Note: This is not an issue if you run two different Guidewire applications on a single machine. The
two different applications run under different webapp paths.
To work around this issue, open the application instance sessions using different paths. For example, use the fully
qualified domain machine name for one application server and localhost for the second application server. The
browser does not associate the same cookie with an IP address and with a machine name.

Installing the QuickStart development environment

This topic describes using the ClaimCenter QuickStart development environment. The QuickStart method uses a
bundled and lightweight application server and database that are suitable for development and demonstration
purposes. Guidewire does not support the QuickStart method for a production environment.

Advantages to using the QuickStart software

The bundled lightweight application server and database provided with ClaimCenter make it possible to accomplish
more work with less effort and in less time. The following are some specific benefits to using the QuickStart
configuration with Guidewire Studio as the IDE (Integrated Development Environment):
• Install and run ClaimCenter rapidly without any configuration.
• Configure ClaimCenter without needing to repackage WAR or EAR files.
• Import sample data and create new data through the user interface.
• View and experiment with the default functionality of ClaimCenter.
• Make changes to ClaimCenter using Guidewire Studio.
The QuickStart application server (Jetty) is a fully certified servlet container that starts faster than production
application servers. It also provides an instantaneous view of configuration changes. The QuickStart server uses the
ClaimCenter configuration files from the file system, rather than requiring a packaged WAR or EAR file. Therefore,
developers can configure ClaimCenter without needing to repackage the application.

QuickStart development environment prerequisites

Your environment must meet the minimum requirements for a development workstation. In particular, ClaimCenter
requires Java, and Guidewire strongly recommends the use of the DCEVM for development in the QuickStart
environment. If you do not install the DCEVM, you will not be able to see dynamic changes to Gosu code.

See also
• See the Supported Software Components knowledge article for current system and patch level requirements. Visit
the Guidewire Community and search for knowledge article 1005, “Supported Software Components”.

About the QuickStart application server

The QuickStart application server is Jetty, a Java-based HTTP Server and Servlet Container. Jetty was released as an
open source project under the Apache 2.0 License and is fully-featured. Refer to [Link] for
details. The QuickStart application server is suitable for demonstration and development environments. The
QuickStart application server is not suitable nor supported for production environments.
ClaimCenter on the QuickStart server always runs in development mode. You cannot run ClaimCenter on the
QuickStart server in production mode.

See also
• System Administration Guide
52 chapter 3: Installing a ClaimCenter development environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

Configuring QuickStart ports

The ClaimCenter /modules/configuration/etc/[Link] file lists the ports used by the QuickStart
server. You can specify the port on which the server listens, a debug port, and the port to use to stop the server.
The ClaimCenter QuickStart application server listens on port 8080 by default.
The ContactManager QuickStart application server listens on port 8280 by default.

IMPORTANT You cannot assign a port number between 8800 and 8900 to the QuickStart server.

About the QuickStart default database

ClaimCenter QuickStart uses an H2 Database Engine by default. However, it is also possible to use an Oracle or
SQL Server database in your development environment.
Note: To integrate ClaimCenter with ContactManager, see the Guidewire Contact Management Guide.

See also
• “Using the QuickStart database” on page 54
• “Using SQL Server or Oracle in a development environment” on page 55
• “Archiving in a development environment” on page 56
• “Install sample data” on page 58
• System Administration Guide

Install the bundled ClaimCenter QuickStart application server

Procedure
1. Create an installation directory for ClaimCenter on the host system.
Do not use spaces in the installation directory path. Studio does not run from a directory with a space in its
name.
2. Extract the contents of the ClaimCenter Zip file into the installation directory.
Using a third-party tool such as 7-Zip may perform better than using the built-in Windows decompression
utility.
3. Open a command prompt to the ClaimCenter installation directory.
4. (Optional) Run the following command:
gwb dropDb
You need to run this command only if you are reinstalling ClaimCenter and using a QuickStart database.
5. From the same command prompt, run the following command:
gwb compile
This command copies module resources and JavaScript files to the bundled QuickStart server.
6. (Optional) Configure the location in which ClaimCenter stores the QuickStart database files.
7. Navigate to the root of the ClaimCenter installation directory and open a command prompt.
8. Run the following command:
gwb runServer
This command starts the ClaimCenter application. After the server starts, you see the following statement in
the command window:

*****ClaimCenter ready*****

9. Open a browser and navigate to the following URL:

[Link]
10. Log into ClaimCenter as the default superuser, using the following default credentials:
Installing a ClaimCenter development environment 53
Guidewire ClaimCenter 10.0.0 Installation Guide

Username - su
Password - gw

See also
• See “Modify the QuickStart database file location” on page 55 for details of how to change the QuickStart
database file location.
• Configuration Guide

QuickStart commands
You launch many ClaimCenter commands by passing arguments to the gwb command, located in the ClaimCenter
installation directory.

See also
• For a list of gwb commands, see “Command reference” on page 111.
• For a list of JVM options that work with the gwb commands, see the System Administration Guide.

Troubleshooting the QuickStart application server

If you have problems with QuickStart, consider the following issues.

Unable to upgrade
Issue
You are unable to upgrade or to see changes after changing database tables.

Solution
First try restarting the server. If that does not work, then drop the database. If the server is running, then stop the
server by opening a command prompt, navigating to the ClaimCenter installation directory and entering the
following command:

gwb stopServer

Then, drop the database with the command gwb dropDb.

Port conflicts
Issue
You experience port conflicts.

Solution
The QuickStart server listens on a default server port. The default server port might already be in use by your
organization. Consult with your IT department to verify which ports to use.

See also
“Configuring QuickStart ports” on page 53

Using the QuickStart database

The QuickStart database is the H2 Database Engine. Guidewire includes the QuickStart database for the
convenience of those who need a lightweight solution for demonstration and configuration purposes. By default,
ClaimCenter uses the QuickStart database.
54 chapter 3: Installing a ClaimCenter development environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

Limitations to the QuickStart database

While the QuickStart database is convenient, Guidewire does not support using it for production. The following are
limitations to using the QuickStart database:
• The QuickStart database only supports one connection at a time. Therefore, you cannot have the server running
and look at the schema at the same time.
• You cannot test your cluster against the QuickStart database.
• The QuickStart database does not support all upgrades. Guidewire does not test upgrades on the QuickStart
database other than the process of creating a database.

How to drop the QuickStart database

Open a command prompt in the ClaimCenter installation directory and enter gwb dropDb.

Additional quickstart references

For more information about the QuickStart database and tools that you can download to view your schema, see the
following web site:

[Link]

For development environment information, see the Configuration Guide.

Modify the QuickStart database file location

About this task
Guidewire uses /tmp/guidewire as the database file location and cc as the file prefix in the default configuration.
You can modify the default database file location and prefix.

Procedure
1. In a command window, navigate to the ClaimCenter installation directory.
2. Launch Guidewire Studio using the following command:

gwb studio

3. In the Project window, expand configuration→config and open [Link].

4. Look for the database block that lists h2 as the dbtype.
5. In this database block, search for the jdbc-url attribute value.
The file path after the colon sets the file location. The value after the location sets the file prefix.
In the following example, tmp/guidewire is the file location and cc is the file prefix.

<!-- H2 (meant for dev/quickstart use only!) -->

<database name="ClaimCenterDatabase" dbtype="h2">
<dbcp-connection-pool jdbc-url="jdbc:h2:mem:/tmp/guidewire/cc"/>
</database>

6. Make changes to the file location and prefix as needed for your business needs.
7. In Studio, click File→Save All.

Using SQL Server or Oracle in a development environment

You can use Oracle or SQL Server with the QuickStart application server instead of the QuickStart database. It is
possible to use this configuration as a development environment only. Guidewire does not support using the
Quickstart server for a production environment.
Installing a ClaimCenter development environment 55
Guidewire ClaimCenter 10.0.0 Installation Guide

See also
• For instructions on creating a SQL Server or Oracle database instance, consult “Configuring the database server
for Guidewire applications” on page 26.
• For instructions on configuring ClaimCenter to connect to the database, consult “Configuring a database
connection” on page 60.

Archiving in a development environment

About this task
If you plan to use archiving in your production environment, Guidewire recommends that you enable archiving in
your development environment in order to design and test your custom implementation.

See also
• Application Guide
• Integration Guide

Archive‐related configuration files

The following ClaimCenter configuration elements implement archiving in Guidewire ClaimCenter.

Configuration element Contains

[Link] Boolean parameter ArchivingEnabled to enable or disable ClaimCenter archiving
[Link] Schedule on which to run archive batch processing
[Link] Number of writers to use in executing archive batch processing
Archive batch processing Batch processing type that manages archive eligibility
Archive plugin Integration points necessary for Claim archiving
Archive Gosu rule sets Rules to manage various aspects of the archiving process

See also
• Configuration Guide
• System Administration Guide
• Integration Guide
• Rules Guide

Enable archiving in Guidewire ClaimCenter

Before you begin
Guidewire strongly recommends that you contact Customer Support before implementing archiving.

Procedure
1. In ClaimCenter Studio, navigate to the following location and open file [Link] for editing:
configuration→config
2. Locate configuration parameter ArchiveEnabled and set its value to true.

<param name="ArchiveEnabled" value="true"/>

56 chapter 3: Installing a ClaimCenter development environment

 Guidewire ClaimCenter 10.0.0 Installation Guide

WARNING After you set ArchiveEnabled to true and start the server, you cannot change
the value of this parameter again. If you reset the value to false, the server does not start.

3. Navigate to the following location and open file [Link] for editing:
configuration→config→scheduler
4. Locate and uncomment the Archive code block.

<ProcessSchedule process="Archive">
<CronSchedule hours="2" minutes="20"/>
</ProcessSchedule>

5. Navigate to the following location and open file [Link] for editing:
configuration→config→workqueue
6. Ensure that the number of writer instances is adequate for your ClaimCenter installation.

<work-queue workQueueClass="[Link]"
progressinterval="600000">
<worker instances="1"/>
</work-queue>

7. Review the default implementation of the following archiving-related rule sets:

configuration→config→Rule Sets→Archive→Default Group Claim Archiving Rule
Modify and update the archive rules to meet your business needs.
8. Review the default implementations of the following archive plugin interfaces:
configuration→config→Plugins→registry→IArchiveSource
Modify and update the plugin implementations to meet your business needs.
9. Save your work.
10. Rebuild and redeploy Guidewire ClaimCenter for your configuration changes to take effect.

See also
• Configuration Guide
• System Administration Guide
• Integration Guide
• Rules Guide

Disabling Guidewire ClaimCenter archiving

The process to disable Claim archiving differs depending on whether you have ever enabled archiving in Guidewire
ClaimCenter:
• Archiving never enabled
• Archiving enabled

Archiving never enabled

If you have never enabled archiving in Guidewire ClaimCenter, then you need to do nothing to disable archiving.
You simply accept the default archiving configuration, which Guidewire disables in the base configuration by
default.

Archiving enabled
After you enable ClaimCenter archiving, you cannot disable archiving entirely unless you drop the application
database. This means that once enabled, even after you disable archiving, you still see references to Claim archiving
within the ClaimCenter user interface.
Do not attempt to disable archiving in a production environment after you have enabled this functionality.
Installing a ClaimCenter development environment 57
Guidewire ClaimCenter 10.0.0 Installation Guide

WARNING Do not attempt to reset the value of ArchiveEnabled from true to false. After you
set ArchiveEnabled to true and start the server, you cannot change the value of this parameter
again. If you reset the value to false, the server does not start. Also, do not remove the archive
work queue. Removing this work queue after enabling archiving prevents that application server
from starting.

You can actively disable the default, but, unused, configuration elements that ClaimCenter uses in processing
archive items. If you choose to disable the unused archiving configuration elements, do the following:

Configuration element To disable

Batch processing schedule Comment out the relevant batch processing types in [Link].
Archiving work queue Set the number of worker instances to 0 in [Link]. Do not attempt to remove or hide
this work queue after you enable ClaimCenter archiving.
Archive plugin implemen‐ Select the Disabled box in the archive plugin editor for the relevant archive plugin implementation.
tation You access the archive plugin editor in Studio in the following location:
configuration→config→Plugins→registry …

Archive rule sets Clear the check box next to the archive rule set to disable the rule set.

Rebuild and redeploy Guidewire ClaimCenter for your configuration changes to take effect.

See also
• Configuration Guide
• System Administration Guide
• Integration Guide
• Rules Guide

Install sample data

About this task
ClaimCenter includes sample data for use in training, configuration and testing. The ClaimCenter server must be in
development mode to be able to load sample data. The QuickStart server is always in development mode.

IMPORTANT Guidewire expressly does not support any attempt to load the default sample data into a
production system.

If you have previously loaded a sample data set, you must drop the ClaimCenter database before it is possible to
load a different sample data set.

Procedure
1. Log into ClaimCenter using an administrative user account.
2. Press Alt+Shift+T to open the Server Tools page.
3. Click Internal Tools.
4. Click CC Sample Data from the menu on the left.
5. Click Load for either the Admin, Demo, or Catastrophe Search data sets.
After ClaimCenter loads the data set, the CC Sample Data screen lists the imported object types.

See also
• For instructions on how to import or export administrative data, see the System Administration Guide.
58 chapter 3: Installing a ClaimCenter development environment
chapter 4

Installing a ClaimCenter production

environment

Installing a ClaimCenter production environment is a multi-step process that requires you to perform several
procedures. The initial installation process can take from two hours to a full day.

See also
• “Installing a ClaimCenter development environment” on page 51

Installing Guidewire ClaimCenter

Guidewire packages the ClaimCenter application as a Zip file. This file contains tools and files necessary to build a
WAR or EAR file to install on an application server. It also contains the developer toolkit and other items.
Unpack the configuration files onto the workstation that you plan to use as the home base for your ClaimCenter
configuration. These directions assume you plan to maintain the configuration files on the administrative
workstation.
Guidewire recommends that you maintain your ClaimCenter configuration files in a change control system such as
Perforce or SVN.

See also
• For an overview of the directories included with ClaimCenter, see the Configuration Guide.

Unpack the ClaimCenter configuration files

Procedure
1. If you have not already done so, create an installation directory for ClaimCenter.
Do not use spaces in the installation directory path. Studio does not run from a directory with a space in its
name.
2. Extract the contents of the ClaimCenter Zip file into the installation directory.
Using a third-party tool such as 7-Zip may perform better than using the built-in Windows decompression
utility.
Installing a ClaimCenter production environment 59
Guidewire ClaimCenter 10.0.0 Installation Guide

3. Do one of the following:

• If using a change control system such as Perforce or SVN to manage ClaimCenter configuration files, add
the files in the ClaimCenter modules\configuration directory to change control at this point.
• If not using a version control system, make a read-only copy of the ClaimCenter directory. The use of back-
up copy enables you to recover quickly from accidental changes that can prevent ClaimCenter from starting.

Result
At this point, you have a full set of ClaimCenter configuration files.

Configuring a database connection

The topics in this section discuss how to configure a database connection.
After you complete the configuration of the database connection, proceed to “Deploying to the application server”
on page 78.

About the database element

File [Link] stores connection and configuration parameters for the ClaimCenter database. Set
database connections by uncommenting and modifying the appropriate sample <database> element in database-
[Link], accessible within Guidewire Studio under configuration→config.
The <database> element in [Link] 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 ClaimCenter

<dbcp-connection-pool jdbc-url="jdbc url" password-file="file name">
<reset-tool-params collation="collation"
[Link]="Oracle TNS name" [Link]="system username"
[Link]="[Link]"/>
</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 [Link] contains a single root-level <database> element that takes the following attributes.
60 chapter 4: Installing a ClaimCenter production environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

Attribute Re‐ Default Sets

quired
addforeignkey No true Used only for development and testing. Do not use this attribute in production.
checker No false Boolean value that specifies whether ClaimCenter 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 ClaimCenter 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
• System Administration Guide
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 environ‐
ments. For example, you can set up different database configurations for a produc‐
tion environment and a test environment.
See the System Administration Guide for more information.
name Yes ... A string identifying the database for which ClaimCenter uses this connection specifi‐
cation.
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 configura‐
tion. Do not set printcommands to false in a production environment.
versionchecksonly No false Boolean value that specifies whether the ClaimCenter server runs only database ver‐
sion checks at startup, without performing any actual database upgrade steps.
See also
Upgrade Guide

See also
• “Configuring the database server for Guidewire applications” on page 26
• System Administration Guide

Mapping logical tablespaces to physical tablespaces

It is possible to map the logical tablespaces required by ClaimCenter to either Oracle tablespaces or SQL Server
filegroups using database configuration file [Link]:
• For Oracle, Guidewire requires that you map the Guidewire logical tablespaces to the Oracle tablespaces.
• For SQL Server, mapping the Guidewire logical tablespaces to filegroups is optional. Create these physical
tablespaces or filegroups while you set up your database.

See also
• See “Configuring the database server for Guidewire applications” on page 26 for information on creating
physical tablespaces or filegroups for your database.
Installing a ClaimCenter production environment 61
Guidewire ClaimCenter 10.0.0 Installation Guide

Configuration options for Oracle tablespaces

To specify tablespaces for Oracle, use the following syntax in your database configuration in database-
[Link]:

<database>
...
<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>
</database>

To specify tablespaces for a particular table in Oracle, use the following syntax in your database configuration in
[Link]:

<database>
...
<upgrade>
<ora-db-ddl>
<tablespaces admin="admin tablespace" index="index tablespace" op="op tablespace"
staging="staging tablespace" typelist="typelist tablespace" lob="lob tablespace" />
<ora-table-ddl table-name="table name">
<ora-table-tablespaces table-tablespace="table tablespace" lob-tablespace="LOB tablespace"
index-tablespace="index tablespace"/>
</ora-table-ddl>
</ora-db-ddl>
</upgrade>
</database>

Configuration options for SQL Server filegroups

To specify filegroups for SQL Server, use the following syntax in your database configuration in database-
[Link].

<database>
...
<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>
</database>

To specify filegroups for a particular table in SQL Server, use the following syntax in your database configuration in
[Link].

<database>
...
<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-table-ddl table-name="table name">
<mssql-table-filegroups table-filegroup="table filegroup" lob-filegroup="LOB filegroup"
index-filegroup="index filegroup"/>
</mssql-table-ddl>
</mssql-db-ddl>
</upgrade>
</database>

62 chapter 4: Installing a ClaimCenter production environment

 Guidewire ClaimCenter 10.0.0 Installation Guide

Configuration options for individual database tables

You can configure DDL options for individual tables and indexes in the database configuration file, database-
[Link]. It is not possible, however, to specify the DDL attributes of the primary key backing index (on column
named with suffix ID) in the configuration file. These attributes use the DBMS default values.
This topic shows valid syntax in [Link] for configuring DDL options for each database type. All
options are shown for reference.

Oracle

<database>
...
<upgrade>
<ora-db-ddl>
<tablespaces admin="admin tablespace" index="index tablespace" op="op tablespace"
staging="staging tablespace" typelist="typelist tablespace" lob="lob tablespace" />
<ora-compression table-compression="ADVANCED|BASIC|NONE" index-compression="true|false">
<ora-lobs type="BASIC|SECURE|SECURE_COMPRESSED" caching="true|false" />
<ora-table-ddl table-name="cc_tableName">
<ora-index-ddl key-columns="column1,column2" index-compression="true|false"
index-tablespace="index tablespace">
<ora-index-hash-partitioning locality="GLOBAL|LOCAL" num-partitions="number"/>
</ora-index-ddl>
<ora-lobs type="BASIC|SECURE|SECURE_COMPRESSED" caching="true|false" />
<ora-table-compression table-compression="NONE|OLTP" />
<ora-table-hash-partitioning hash-column="column name" num-partitions="number"/>
<ora-table-tablespaces table-tablespace="table tablespace" lob-tablespace="LOB tablespace"
index-tablespace="index tablespace"/>
</ora-table-ddl>
</ora-db-ddl>
</upgrade>
</database>

SQL Server

<database>
...
<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-table-ddl table-name="table name">
<mssql-index-ddl key-columns="column1,column2" index-compression="true|false"
index-filegroup="index filegroup"/>
<mssql-table-compression table-compression="NONE|PAGE|ROW"
index-compression="NONE|PAGE|ROW" />
<mssql-table-filegroups table-filegroup="table filegroup" lob-filegroup="LOB filegroup"
index-filegroup="index filegroup"/>
</mssql-table-ddl>
</mssql-db-ddl>
</upgrade>
</database>

See also
• “Configuring database compression” on page 28
• “Guidelines for configuring Oracle for ClaimCenter” on page 33
• “Guidelines for configuring SQL Server for ClaimCenter” on page 40

Configuration options for database table groups

Table groups specify a set of tables on which to run database consistency checks. There use is optional. Thus, you
can define zero or more table groups.
Installing a ClaimCenter production environment 63
Guidewire ClaimCenter 10.0.0 Installation Guide

As the ClaimCenter server starts, it checks that no table is listed more than once in a single table group definition
and that each table listed exists. If a table is listed more than once in a group or does not exist, the ClaimCenter
server logs an error and stops.
To define a table group, add a <tablegroup> element to the database element in [Link]. The
<tablegroup> element has the following attributes:

env Specifies the environment for the table group. You can have different table groups set up for different environments.
name Identifies the table group.
tables Defines which tables are in the table group. Use a comma‐separated list to specify the tables, for example:

<database>
...
<tablegroup name="MyTables" tables="cc_1, cc_2, cc_3"/>
...
</database>

See also
• System Administration Guide

Specifying additional database parameters

To pass additional parameters required for your database connection, specify one or more name-value <param>
elements in database configuration file [Link]. Several parameters configure the connection pool, if
you are using ClaimCenter to manage the connection pool rather than a JNDI data source managed by the
application server.

See also
• See the System Administration Guide for a description the database configuration parameters that control the
connection pool.

The JDBC URL format

In database configuration file [Link], the jdbc-url attribute of the <dbcp-connection-pool>
element stores connection information for the database. Define a jdbc-url attribute unless you use a JNDI data
source managed by the application server.
If you want to use a JNDI data source managed by the application server, skip to “Configure ClaimCenter to use a
direct JNDI data source” on page 67.

JDBC URL format for Oracle

In database configuration file [Link], the JDBC URL for a standalone Oracle instance uses one of
the following formats:

<dbcp-connection-pool jdbc-url="jdbc:oracle:thin:userName/password@serverName:port/OracleSID" />

or

<dbcp-connection-pool jdbc-url="jdbc:oracle:thin:userName/password@
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=serverName)(PORT=port))
(CONNECT_DATA=(SERVICE_NAME=OracleSID)))"/>

For Oracle Real Application Cluster (RAC) implementations, use an expanded form of the latter jdbcURL format.
For example, for a two-node Oracle cluster:

<dbcp-connection-pool jdbc-url="jdbc:oracle:thin:userName/password@
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=serverName1)(PORT=port))

64 chapter 4: Installing a ClaimCenter production environment

 Guidewire ClaimCenter 10.0.0 Installation Guide

(ADDRESS=(PROTOCOL=TCP)(HOST=serverName2)(PORT=port))(LOAD_BALANCE=yes)
(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=OracleSID)))"/>

The server name can be specified using the computer name or IP address.

JDBC URL format for SQL Server

In database configuration file [Link], the JDBC URL for SQL Server uses the following format:

<dbcp-connection-pool jdbc-url="jdbc:sqlserver://serverName[:port];
databaseName=cc;user=ccUser;password=password
[;applicationName=applicationName]"/>

The example code shows optional parameters in brackets.

If your SQL Server instance listens on the default port, 1433, you can omit the port and preceding colon from the
JDBC URL. However, Microsoft recommends that you always specify the port value for security reasons. If you
specify the port number, the JDBC driver connects directly to SQL Server and does not make a request to
[Link]. If your SQL Server instance is listening to a different port than the default 1433, specify that port
number in the JDBC URL.
You can include an applicationName property on the JDBC URL connection string. If you set this value, the server
logs and Activity Monitor include it in the thread identification information. If you do not specify an
applicationName, the ClaimCenter server creates one by concatenating cc, followed by the application version,
including build number. Finally, if you defined the SQL Server ADDL_CONN_DESCR system property, ClaimCenter
appends this value to the generated applicationName value.
ClaimCenter requires that the selectMethod on the JDBC URL connection be set to direct. This is the default
value, so you do not need to include this value in your JDBC URL. If you include selectMethod and set it to
cursor, the server does not start.
ClaimCenter defaults the value of the sendStringParametersAsUnicode property to be the correct, appropriate
value in the SQL Server JDBC URL connection. ClaimCenter does not override an existing value. If you set
sendStringParametersAsUnicode in [Link], the server will validate the value to be correct.

Obfuscating the database password

It is likely that you do not want to expose the password in the JDBC URL in database configuration file database-
[Link]. For this reason, Guidewire provides the following alternatives for hiding the database password:

Use a pass‐ See “Use a password file to obfuscate the database password” on page 66
word file
Implement the To hide the password in the JDBC URL in [Link], Guidewire provides a default implementa‐
Database Au‐ tion of the DBAuthenticationPlugin authentication plugin. The use of this plugin implementation provides
thentication a higher level of security than the use of an external file to store the password.
Plugin Use this plugin to define a custom method that returns the user name and password in a format that the
database system recognizes.
For information on implementing the DBAuthenticationPlugin plugin in your environment, see the
Integration Guide.
Use a JNDI da‐ You can configure ClaimCenter to use a JNDI data source for your database connection on any of the follow‐
ta source ing application servers:
• JBoss
• WebLogic
• WebSphere
The JNDI data source uses a Java 2 Connector (J2C) authentication alias to store the user name and password.
See also “Configure ClaimCenter to use a direct JNDI data source” on page 67.

Installing a ClaimCenter production environment 65

Guidewire ClaimCenter 10.0.0 Installation Guide

Use a password file to obfuscate the database password

About this task

To hide the password in the JDBC URL, you can place the password in an external file and reference this file from
the [Link] file.

Procedure
1. Add the password-file attribute to the <dbcp-connection-pool> element within the <database> element.
2. Set the value of password-file to the absolute path of the password file.
3. Replace the password value in the jdbc-url connection specification with a ${password} placeholder.
At run time, ClaimCenter reads the password from the file.

Result
After you complete this process, your database specification looks similar to the following:
Oracle

<database name="BillingCenterDatabase" driver="dbcp" dbtype="oracle">

<dbcp-connection-pool jdbc-url="jdbc:oracle:thin:USER/${password}@ORACLEDB:PORT:INSTANCE"
password-file="c:\secure\[Link]" />
</database>

SQL Server

<database name="ClaimCenterDatabase" driver="dbcp"

dbtype="sqlserver">
<dbcp-connection-pool jdbc-url="jdbc:sqlserver://HOSTNAME:1433;databaseName=cc;user=ccUser;
password="${password}" password-file="c:\secure\[Link]" />
</database>

About SQL Server JDBC logging

During troubleshooting, Guidewire might request a trace log from the Microsoft JDBC driver. Do not turn on trace
logging in other circumstances as it places a heavy overhead on the system, and the files created can quickly become
very large.
It is possible to turn on Microsoft JDBC driver logging at ClaimCenter startup by specifying the jdbc-trace-file
and jdbc-trace-level attributes on the <sqlserver-settings> element:

<database ...>
<sqlserver-settings jdbc-trace-file="file name" jdbc-trace-level="trace level" />
...
</database>

The trace level is a string that corresponds to a valid trace level as documented at the following Microsoft site:
[Link]
If you do not specify the location of the trace file, it defaults to the following location:
C:\temp\msjdbctrace%[Link]
Refer to the following web site for documentation on the trace file specification:
[Link]
Using %h and %t puts the file in the Documents and Settings directory under the name which is running the
application server.
Guidewire provides a means to manage JDBC Driver logging in the ClaimCenter Server Tools Info Pages→Microsoft
JDBC Driver Logging screen. Use this screen to start and stop Microsoft driver logging on a running application server.
Using this screen is a better option if tracing a particular operation, in order to minimize system impact and size of
the trace file.
66 chapter 4: Installing a ClaimCenter production environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

See also
• System Administration Guide

Using a JNDI data source

It is possible for ClaimCenter to use a Java Naming and Directory Interface (JNDI) data source managed by any of
the following application servers:
• JBoss
• Tomcat
• WebLogic
• WebSphere
The use of JNDI data source enables you to configure database parameters, including connection pool size, using the
application server. Using a JNDI data source also provides you with another secure alternative to placing the user
name and password in the [Link] file.
During startup, ClaimCenter records the connection made through JNDI with an entry similar to the following in the
log:

INFO Looking up JNDI datasource 'jdbc/ccDataSource'...

Important caveats
1. Guidewire supports JNDI using the drivers bundled with ClaimCenter only. Guidewire does not support the
XA versions of a data source.
2. If using a JNDI data source, create the JNDI data source on the application server before deploying
ClaimCenter to the application server.

See also
• “Configure ClaimCenter to use a direct JNDI data source” on page 67
• “Configure ClaimCenter to use an indirect JNDI data source” on page 68
• “Create an Oracle JNDI data source on JBoss” on page 68
• “Create a SQL Server JNDI data source on JBoss” on page 69
• “Create an Oracle JNDI data source on Tomcat” on page 69
• “Create a SQL Server JNDI data source on Tomcat” on page 70
• “Create an Oracle JNDI data source on WebLogic” on page 71
• “Create a SQL Server JNDI data source on WebLogic” on page 71
• “Create an Oracle JNDI data source on WebSphere” on page 72
• “Create a SQL Server JNDI data source on WebSphere” on page 75

Configure ClaimCenter to use a direct JNDI data source

Procedure
1. Open Guidewire Studio™ for ClaimCenter.
2. In the Project window, expand configuration→config.
3. Open file [Link].
4. Remove the <dbcp-connection-pool> element.
5. Add a <jndi-connection-pool> element and specify the JNDI name you assign to the data source as a
datasource-name attribute.
After you complete this process, the <database> element looks similar to the following:

<database name="ClaimCenterDatabase" dbtype="oracle|sqlserver">

<jndi-connection-pool datasource-name="jdbc/ccDataSource" />

Installing a ClaimCenter production environment 67

Guidewire ClaimCenter 10.0.0 Installation Guide

...
</database>

6. Close and save the [Link] file.

7. Rebuild and install the ClaimCenter application EAR or WAR file.

Configure ClaimCenter to use an indirect JNDI data source

Procedure
1. In the ClaimCenter Studio Project window, expand configuration→config:
2. Open file [Link].
3. Remove the <dbcp-connection-pool> element.
4. Add a <jndi-connection-pool> element and specify the JNDI name you assign to the data source as a
datasource-name attribute.
After you complete this process, the <database> element looks similar to the following:

<database name="ClaimCenterDatabase" dbtype="oracle|sqlserver">

<jndi-connection-pool datasource-name="java:comp/env/jdbc/DataSourceName"/>
...
</database>

5. Close and save the [Link] file.

6. Rebuild and install the ClaimCenter application EAR or WAR file.

Create an Oracle JNDI data source on JBoss

Procedure
1. Start the JBoss application server.
2. Log in to the JBoss Admin Console.
3. Click the Deployments tab for the domain hosting ClaimCenter.
JBoss does not show a domain for standalone installations.
4. Click the Add button.
The New Deployment wizard starts.
5. Select Upload a new deployment and click Next.
6. Click Choose File.
7. Browse to the ClaimCenter admin/lib directory.
8. Select the ojdbc<version>-[Link] file and click Next.
9. Check the Enable check box (if not checked) and click Finish.
A confirmation message box confirms that you deployed ojdbc<version>.jar successfully.
10. Click the Configuration tab.
11. Click Subsystems→Datasources→Non-XA.
12. Click Add.
The Create Datasource wizard starts.
13. Click Subsystems→Connector→Datasources.
14. Select Oracle Datasource and click Next.
15. Enter a Name for the data source.
16. Enter a JNDI Name. The JNDI name must use the pattern java:jboss/datasources/name, where name is the
name of the data source from the previous step.
The JNDI name must match the value of the data source-name attribute of the <jndi-connection-pool>
element in the [Link] file.
17. Click Next.
68 chapter 4: Installing a ClaimCenter production environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

18. Select the Oracle JDBC driver, (exactly as in step Step 8). Keep default values for other fields and click Next.
19. Enter the Connection URL, Username, and Password and click Next.
20. Confirm information provided on the Summary page and click Finish.
Message "Added datasource name" is shown. In case of error, the new data source was not added, and you
must repeat steps starting from step Step 12.
21. Select the newly added data source and click Test Connection.
If you receive a message that the JDBC connection failed, check your connection settings.

Create a SQL Server JNDI data source on JBoss

Procedure
1. Start the JBoss application server.
2. Log in to the JBoss Admin Console.
3. Click Deployments for the domain hosting ClaimCenter.
JBoss does not show a domain for standalone installations.
4. Click the Add button.
The New Deployment wizard starts.
5. Select Upload a new deployment and click Next.
6. Click the Choose File button.
7. Browse to the ClaimCenter admin/lib directory.
8. Select the sqljdbc<version>.jar file and click Next.
9. Check the Enable check box (if not checked) and click Finish.
A confirmation message box confirms that you deployed sqljdbc<version>.jar successfully.
10. Click the Configuration tab.
11. Click Subsystems→Datasources→Non-XA.
12. Click Add.
The Create Datasource wizard starts.
13. Select Microsoft SQLServer Datasource and click Next.
14. Enter a Name for the data source.
15. Enter a JNDI Name. The JNDI name must use the pattern java:jboss/datasources/name, where name is the
name of the data source from the previous step.
The JNDI name must match the value of the data source-name attribute of the <jndi-connection-pool>
element in the [Link] file.
16. Click Next.
17. Select the SQL Server JDBC driver, (exactly as in step Step 8). Keep default values for other fields, and click
Next.
18. Enter the Connection URL, Username, and Password and click Next.
19. Confirm information provided on the Summary page and click Finish.
Message "Added datasource name" is shown. In case of error, the new data source was not added and you
must repeat steps starting from step Step 12.
20. Select the newly added data source and click Test Connection.
If you receive a message that the JDBC connection failed, check your connection settings.

Create an Oracle JNDI data source on Tomcat

About this task
Guidewire bundles the supported version of the Oracle JDBC Thin Driver in the [Link] JAR file.
Refer to the following web site for more information about configuring the data source:
Installing a ClaimCenter production environment 69
Guidewire ClaimCenter 10.0.0 Installation Guide

[Link]

Procedure
1. Copy the [Link] JAR file from the ClaimCenter installation admin/lib directory to the
lib directory within the Tomcat home.
This JAR file contains the APIs for connecting to the ClaimCenter database.
2. Add a Resource entry to the [Link] file in the conf directory of the Tomcat instance. If the
[Link] file does not exist, create it.
The Resource element must be a child of the top-level Context element. The resource name must match the
datasource-name attribute of the jndi-connection-pool element in [Link], for example:

<Resource name="jdbc/ccDataSource" auth="Container" type="[Link]"

driverClassName="[Link]"
url="jdbc:oracle:thin:database user/database password@database server name:port/OracleSID"
username="database user" password="database password" maxTotal="20" maxIdle="10" maxWaitMillis="-1"/>

3. Add a resource-ref entry to the [Link] file in the conf directory of the Tomcat instance.
For example:

<resource-ref>
<description>Oracle Datasource</description>
<res-ref-name>jdbc/Datasource name</res-ref-name>
<res-type>[Link]</res-type>
<res-auth>Container</res-auth>
</resource-ref>

4. Restart the Tomcat instance.

Create a SQL Server JNDI data source on Tomcat

Procedure
1. Copy the sqljdbc<version>.jar JAR file from the ClaimCenter installation admin/lib directory to the lib
directory within the Tomcat home.
This JAR file contains the APIs for connecting to the ClaimCenter database.
2. Add a Resource entry to the [Link] file in the conf directory of the Tomcat instance. If the
[Link] file does not exist, create it.
The Resource element must be a child of the top-level Context element. The resource name attribute must
match the datasource-name attribute of the jndi-connection-pool element in [Link], for
example:

<Resource name="jdbc/ccDataSource" auth="Container" type="[Link]"

driverClassName="[Link]"
url="jdbc:sqlserver://database server name:database server port;selectMethod=direct;
databaseName=database name;sendStringParametersAsUnicode=false;user=database user;
password=database password"
username="database user" password="database password" maxTotal="20" maxIdle="10"
maxWaitMillis="-1"/>

3. Add a resource-ref entry to the [Link] file in the conf directory of the Tomcat instance, for example:

<resource-ref>
<description>SQL Server Datasource</description>
<res-ref-name>jdbc/Datasource name</res-ref-name>
<res-type>[Link]</res-type>
<res-auth>Container</res-auth>
</resource-ref>

4. Restart the Tomcat instance.

70 chapter 4: Installing a ClaimCenter production environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

Create an Oracle JNDI data source on WebLogic

About this task
Guidewire bundles the supported version of the Oracle JDBC Thin Driver in the [Link] JAR file.

IMPORTANT You must use this Guidewire bundled version of the Oracle JDBC Thin Driver and not
the default driver provided by WebLogic

To verify the Oracle driver used by WebLogic matches the one bundled with ClaimCenter

Procedure
1. Copy the [Link] file from your ClaimCenter installation admin/lib directory to the WebLogic
$DOMAIN/lib directory.
Copy c:/ClaimCenter/admin/lib/ojdbc7-[Link].0-prod to c:/example/weblogic-12.2.1/
user_projects/domains/gw8081/lib.
2. Backup and remove the three ojdbc7*.jar drivers from the $WLS_INSTALL/oracle_common/modules/
[Link] folder. (You can ignore the ojdbc6 drivers.)
Delete [Link], ojdbc7_g.jar, and [Link] from the c:/example/weblogic-12.2.1/
oracle_common/modules/oraclejdbc directory.
3. Ensure that [Link] is not in any part of the CLASSPATH.
4. Open the WebLogic Server Administration Console.
5. Choose Service→Data Source.
6. Click Lock & Edit.
7. Click New to create a Generic Data Source.
8. Enter a name and JNDI name for the data source.
The JNDI name must match the value of the datasource-name attribute of the <jndi-connection-pool>
element in the [Link] file. The JNDI name typically begins with jdbc/.
9. Select Oracle as the Database Type.
10. Select Oracle's Driver (Thin) for Service Connections.
11. Select Versions:Any for Database Driver and click Next.
12. Fill in connection properties for your environment and click Next.
13. Uncheck Supports Global Transactions, click Next and complete the data source creation.
14. Deploy the EAR file for ClaimCenter which has appropriate JNDI setting in [Link].
15. Start ClaimCenter.
A log similar to the following example demonstrates that the created JNDI is being used:

example-t46 2018-08-28 13:58:03,608 INFO Finished security config

example-t46 2018-08-28 13:58:03,608 INFO Starting database ClaimCenterDatabase on env null
example-t46 2018-08-28 13:58:03,608 INFO Using JNDI data source
example-t46 2018-08-28 13:58:03,608 INFO Looking up JNDI datasource 'jdbc/cliCCDatasource'...
example-t46 2018-08-28 13:58:03,608 INFO Using JNDI datasource jdbc/cliCCDatasource

Create a SQL Server JNDI data source on WebLogic

Procedure
1. Copy the sqljdbc<version>.jar JAR file from the ClaimCenter installation admin/lib directory to the
server/lib directory within the WebLogic home.
This JAR file contains the APIs for connecting to the ClaimCenter database.
2. Add the sqljdbc<version>.jar file to the classpath of the WebLogic domain by doing one of the following:
Installing a ClaimCenter production environment 71
Guidewire ClaimCenter 10.0.0 Installation Guide

Modify classpath for sin‐ • Open the WL_HOME/common/bin/commEnv script appropriate to your operating system in a
gle domain text editor.
• Prepend the absolute path to the sqljdbc<version>.jar file, including the file name, to
the WEBLOGIC_CLASSPATH environment variable.
Modify classpath for • Open the setDomainEnv script appropriate to your operating system in a text editor.
multiple domains • Prepend the absolute path to the sqljdbc<version>.jar file to the PRE_CLASSPATH
environment variable.
3. Restart the WebLogic server for the change to take effect.
4. Open the WebLogic Server Administration Console.
5. Click Service→Data Source.
6. Click New to create a Generic Data Source.
7. Enter a Name and JNDI Name for the data source.
The JNDI name must match the value of the datasource-name attribute of the <jndi-connection-pool>
element in the [Link] file.
8. Select MS SQL Server as the Database Type.
9. Select Other as the Database Driver, and click Next.
10. Uncheck Supports Global Transactions, and click Next.
11. Specify connection properties for the SQL Server database, and click Next.
12. Enter [Link] for the Driver Class Name.
13. Specify the URL using the following format:

jdbc:sqlserver://servername:port;databasename=dbname;user=username

14. Fill in the connection properties for your environment:

• Unicode database – Set the value of sendStringParametersAsUnicode to true.
• Single-byte database – Set the value of sendStringParametersAsUnicode to false.
15. Click Test Configuration.
If you configured the connection properly and the database is running, WebLogic displays the message
“Connection test succeeded.”
16. Click Next.
17. Select the targets that use the data source.
18. Click Finish.
The WebLogic Server Administration Console returns you to the Summary of JDBC Data Sources screen.
19. Click Activate Changes.
WebLogic displays the message “All changes have been activated. No restarts are necessary.”

Create an Oracle JNDI data source on WebSphere

About this task
Creating an Oracle JNDI data source on WebSphere is a multistep process.

Copy the Oracle JDBC driver to WebSphere

Before you begin

Before starting this procedure, review “Create a SQL Server JNDI data source on WebSphere” on page 75.

About this task

Guidewire bundles the supported version of the Oracle JDBC Thin Driver in the [Link] JAR file.
Copy file [Link] from the ClaimCenter installation admin/lib directory to the WebSphere
WAS_HOME/lib/ext directory. This JAR file contains the APIs for connecting to the ClaimCenter database.
72 chapter 4: Installing a ClaimCenter production environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

Next steps
After completing this procedure, proceed to “Create the Oracle JDBC provider” on page 73.

Create the Oracle JDBC provider

Before you begin

Before starting this procedure, complete “Copy the Oracle JDBC driver to WebSphere” on page 72.

Procedure
1. Open the WebSphere Administrative Console if not already open.
2. Choose Resources→JDBC→JDBC Providers.
3. Set the Scope to Cell.
4. Click New to create a new JDBC provider.
5. Select Oracle for the Database type.
6. Select Oracle JDBC Driver for the Provider type.
7. Select Connection pool data source for the Implementation type.
8. Supply a new Name for the JDBC provider, for example ccOracle.
9. Enter a Description for the JDBC provider if you want.
10. Click Next.
11. Specify the directory location of [Link].
Set the value to the WAS_HOME/lib/ext path in which you copied [Link] earlier.
12. Click Next.
13. Review the Summary screen and do one of the following:
• Click Previous if you need to make changes.
• Otherwise, click Finish.
14. Click Save to apply your changes to the master configuration.
WebSphere returns you to the JDBC Providers screen. At this point, you have completed the creation of the new
provider.

Next steps
After completing this procedure, proceed to “Create the Oracle JNDI data source” on page 73.

Create the Oracle JNDI data source

Before you begin

Before proceeding, complete “Create the Oracle JDBC provider” on page 73.

Procedure
1. Open the WebSphere Administrative Console if not already open.
2. If you do not yet have a J2C (Java 2 Connector) authentication alias, create a new one.
a. Click Security→Global security.
b. Under Authentication click Java Authentication and Authorization→J2C authentication data.
c. Click New.
d. Enter the following:

Parameter Value
Alias A string specifying the alias name. The alias can be anything you like, for example ccAlias.

Installing a ClaimCenter production environment 73

Guidewire ClaimCenter 10.0.0 Installation Guide

Parameter Value
User ID A string specifying the user name.
Password A string specifying the password.
e. Click OK.
f. Click Save to apply your changes to the master configuration.
3. Choose Resources→JDBC→JDBC Providers.
4. Set the Scope to Cell.
5. Select the JDBC provider that you defined for Oracle.
WebSphere displays the Configuration tab.
6. Select Data Sources in the Additional Properties section.
WebSphere displays the Data sources screen.
7. Click New to create a new data source.
8. Enter a JNDI name for the data source.
The JNDI name must match the value of the datasource-name attribute of the <jndi-connection-pool>
element in file [Link]. See “Using a JNDI data source” on page 67.
9. Click Next.
10. Set the URL value using the jdbc:oracle:thin:@hostname:port:ORACLE_SID format.
11. Select Oracle11g data store helper for the Data store helper class name.
12. Click Next.
13. Select an authentication alias for the Component-managed authentication alias.
14. Select an authentication alias for the Container-managed authentication alias.
15. Click Next.
16. Review the information on the Summary screen and do one of the following:
• Click Previous if you need to make changes.
• Otherwise, click Finish.
17. Click Save to apply your changes to the master configuration.

Next steps
After completing this procedure, proceed to “Configure the Oracle data source properties” on page 74.

Configure the Oracle data source properties

Before you begin

Before proceeding, complete “Create the Oracle JNDI data source” on page 73.

Procedure
1. Open the WebSphere Administrative Console if it is not already open.
2. Choose Resources→JDBC→Data sources.
3. Click the data source that you just defined.
WebSphere displays the Configuration tab.
4. Click WebSphere Application Server data source properties.
5. Set Statement cache size to 0.
6. Select Non-transactional data source.
7. Click OK.
8. Under Additional Properties, click Custom Properties.
9. At the top of the Custom properties screen, click New.
10. Enter the Name commitOrRollbackOnCleanup.
74 chapter 4: Installing a ClaimCenter production environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

11. Enter the Value rollback.

12. Click OK.
13. Click Save to apply your changes to the master configuration.

Next steps
After completing this procedure, proceed to “Test the Oracle JNDI connection” on page 75.

Test the Oracle JNDI connection

Before you begin

Before proceeding, complete “Configure the Oracle data source properties” on page 74.

Procedure
1. Open the WebSphere Administrative Console if it is not already open.
2. Select Resources→JDBC→Data sources.
3. Select the check box next to the ClaimCenter data source.
4. Click Test Connection to verify that the connection works.

Create a SQL Server JNDI data source on WebSphere

About this task
Creating a SQL Server JNDI data source on WebSphere is a multistep process.

Copy the SQL Server JDBC driver to WebSphere

Before you begin

Before proceeding, review “Create a SQL Server JNDI data source on WebSphere” on page 75.

About this task

Copy the sqljdbc<version>.jar JAR file from the ClaimCenter installation admin/lib directory to the
WebSphere lib/ext directory. This JAR file contains the APIs for connecting to the ClaimCenter database.

Next steps
After completing this procedure, proceed to “Create the SQL Server JDBC provider” on page 75.

Create the SQL Server JDBC provider

Before you begin

Before proceeding, complete “Copy the SQL Server JDBC driver to WebSphere” on page 75.

Procedure
1. Open the WebSphere Administrative Console if not already open.
2. Choose Resources→JDBC→JDBC Providers.
3. Set the Scope to Cell.
4. Click New to create a new JDBC provider.
5. Select SQL Server for the Database type.
6. Select Microsoft SQL Server JDBC Driver for the Provider type drop down and click OK.
7. Select Connection pool data source for the Implementation type.
Installing a ClaimCenter production environment 75
Guidewire ClaimCenter 10.0.0 Installation Guide

8. Supply a new Name for the JDBC provider, for example ccSQLServer.
9. Enter a Description for the JDBC provider if you want.
10. Click Next.
11. Specify the directory location of sqljdbc<version>.jar.
Set the value to the WebSphere lib/ext directory, for example:

C:\Program Files\IBM\WebSphere\AppServer\lib\ext

You can ignore the greyed out Class path box that lists the JAR name as [Link] instead of
sqljdbc<version>.jar.
You do not need to enter a value for Native library path.
12. Click Next.
13. Review the Summary screen and do one of the following:
• Click Previous if you need to make changes.
• Otherwise, click Finish.
14. Click Save to apply your changes to the master configuration.
WebSphere returns you to the JDBC Providers screen. At this point, you have completed the creation of the new
provider.
15. Select the JDBC provider you just created.
16. Edit the value of Class path and change it from ${MICROSOFT_JDBC_DRIVER_PATH}/[Link] to $
{MICROSOFT_JDBC_DRIVER_PATH}/sqljdbc<version>.jar.
17. Click OK.
18. Click Save to apply your changes to the master configuration.

Next steps
After completing this procedure, proceed to “Create the SQL Server data source” on page 76

Create the SQL Server data source

Before you begin

Before proceeding, complete “Create the SQL Server JDBC provider” on page 75.

Procedure
1. Open the WebSphere Administrative Console if it is not already open.
2. If you do not yet have a J2C (Java 2 Connector) authentication alias, create a new one.
a. Click Global J2C authentication alias.
b. Click New.
c. Enter the following.

Parameter Value
Alias A string specifying the alias name, for example ccAlias.
User ID A string specifying the user name.
Password A string specifying the password.
d. Click OK.
e. Click Save to apply your changes to the master configuration.
3. Choose Resources→JDBC→JDBC Providers.
4. Set the Scope to Cell.
5. Select the JDBC provider that you created for SQL Server.
76 chapter 4: Installing a ClaimCenter production environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

WebSphere displays the Configuration tab.

6. Select Data Sources in the Additional Properties section.
WebSphere displays the Data sources screen.
7. Click New to create a new data source and enter a value for JNDI name.
For example, enter something such as jdbc/ccDataSource.
The JNDI name must match the value of the datasource-name attribute of the <jndi-connection-pool>
element in the [Link] file. See “Configure ClaimCenter to use a direct JNDI data source” on
page 67.
8. Click Next.
9. Enter the Database name.
10. If using a different port to connect to the database than the default of 1433, change the Port number value.
11. Enter the Server name for the server hosting SQL Server.
12. Uncheck the box for Use this data source in container managed persistence (CMP).
13. Click Next.
14. Select an authentication alias for Component-managed authentication alias.
15. Select an authentication alias for Container-managed authentication alias.
16. Click Next.
17. Review the information on the Summary screen. Do one of the following:
• Click Previous if you need to make changes.
• Otherwise, click Finish.
18. Click Save to apply your changes to the master configuration.

Next steps
After completing this procedure, proceed to “Configure the SQL Server data source properties” on page 77.

Configure the SQL Server data source properties

Before you begin

Before proceeding, complete “Create the SQL Server data source” on page 76.

Procedure
1. Open the WebSphere Administrative Console if it is not already open.
2. Choose Resources→JDBC→Data sources.
3. Click the data source you created for SQL Server.
4. Under Additional Properties, click WebSphere Application Server data source properties.
5. Set the value of Statement cache size to 0.
6. Select the Non-transactional data source checkbox.
7. Click OK.
8. Click Save to apply your changes to the master configuration.
9. Click the data source you created for SQL Server.
10. Under Additional Properties, click Custom Properties.
11. Verify the value of property sendStringParametersAsUnicode.
To change the value, click the property name:
• If you are using unicode columns (nvarchar), set this value to true.
• If you are not using nvarchar, but single byte varchar columns, set this value to false.
Your application server will not start up if this setting is incorrect.
12. At the top of the Custom properties screen, click New.
a. Enter commitOrRollbackOnCleanup in the Name field.
Installing a ClaimCenter production environment 77
Guidewire ClaimCenter 10.0.0 Installation Guide

b. Enter rollback in the Value field.

c. Click OK.
13. Click Save to apply your changes to the master configuration.

Next steps
After completing this procedure, proceed to “Test the SQL Server JNDI connection” on page 78.

Test the SQL Server JNDI connection

Before you begin

Before proceeding, complete “Configure the SQL Server data source properties” on page 77.

Procedure
1. Open the WebSphere Administrative Console if it is not already open.
2. Select Resources→JDBC→Data sources.
3. Select the check box next to the ClaimCenter data source.
4. Click Test Connection to verify that the connection works.

Deploying to the application server

Deploying ClaimCenter to an application server requires creating a WAR or EAR file and installing the package on
an application server.
These instructions are for creating a production ClaimCenter environment. For instructions on how to create a
development ClaimCenter environment, see “Installing a ClaimCenter development environment” on page 51.

Installing ClaimCenter on JBoss in a production environment

To use JBoss as the ClaimCenter application server, you must create and deploy a JBoss-specific ClaimCenter WAR
package file to the application server. Generating this WAR file is a multistep process.
Note: For instructions on how to deploy the ClaimCenter WAR file, refer to the JBoss Enterprise
Application Platform Administration and Configuration Guide.

Set Java options for JBoss

Before you begin

Before proceeding, review “Installing ClaimCenter on JBoss in a production environment” on page 78.

About this task

If you are running JBoss in a 64-bit JVM, it is possible that you need to increase the heap size to prevent JBoss from
running out of memory. The specific values used for JAVA_OPTS in this example may not be suitable for your
environment. Contact Guidewire Support if you need assistance.
Note: You can specify Java options in the JBoss [Link] (Windows) or
[Link] (Linux) file in in the EAP_HOME/bin directory, as this procedure describes, or by
creating a JAVA_OPTS environment variable.

Procedure
1. Open the JBoss file for you operating system.

bin/[Link]
bin/[Link]

78 chapter 4: Installing a ClaimCenter production environment

 Guidewire ClaimCenter 10.0.0 Installation Guide

2. Add lines similar to the following:

set JAVA_OPTS=-Xms512M -Xmx1024M -[Link]=3600000 -

[Link]=3600000 -[Link]=true -server

set JAVA_OPTS=%JAVA_OPTS% -Xbootclasspath/a:%JAVA_HOME%\lib\[Link]

3. Save the file.

4. Using Guidewire Studio, add the following entry to [Link] next to the existing
sun/net paths in that file (near line 21): <path name="com/sun/javadoc"/>

Next steps
After completing this procedure, proceed to “Add a servlet definition for JBoss” on page 79.

Add a servlet definition for JBoss

Before you begin

Before proceeding, complete “Set Java options for JBoss” on page 78.

Procedure
1. Launch Guidewire Studio:
a. Open a command prompt and navigate to the ClaimCenter installation directory.
b. Execute the following command:
gwb studio
2. In the Studio Project window, expand configuration→deploy→WEB-INF:
a. Open file [Link]:
b. Add servlet definitions as needed.
c. Add a servlet-mapping definition for each servlet that you add.
Review the defined servlets for examples.
3. Save your changes.

Next steps
Review the post-installation tasks in “Additional ClaimCenter setup tasks” on page 87. After completing this
procedure, proceed to “Generate the ClaimCenter WAR file for JBoss” on page 79.

Generate the ClaimCenter WAR file for JBoss

Before you begin

Before proceeding, complete “Add a servlet definition for JBoss” on page 79.

About this task

You can build the ClaimCenter WAR file for JBoss with or without JDBC drivers by using one of the following
build commands:

warJbossDbcp Builds the WAR file with JDBC drivers. ClaimCenter manages the database connection pool.

warJbossJndi Builds the WAR file without JDBC drivers. JBoss manges a JNDI database connection pool.

Procedure
1. Open a command prompt and navigate to the ClaimCenter installation directory.
Installing a ClaimCenter production environment 79
Guidewire ClaimCenter 10.0.0 Installation Guide

2. Execute one of the following commands:

gwb warJbossDbcp
gwb warJbossJndi
Both commands generate the ClaimCenter WAR file in the ClaimCenter dist/war/JbossJndi or dist/war/
JbossDbcp directory.
3. Deploy the package to JBoss according to the instructions for deploying an application included with JBoss.

Next steps
After completing this procedure, proceed to “Start ClaimCenter on JBoss” on page 98.

Installing ClaimCenter on Tomcat in a production environment

To use Apache Tomcat as the application server, you must create and deploy a2Tomcat-specific WAR package file to
that application. Generating the WAR file is a multistep process.

Add servlet definitions for Tomcat

Before you begin

Before proceeding, review “Installing ClaimCenter on Tomcat in a production environment” on page 80.

About this task

It is possible to add definitions for additional servlets to the ClaimCenter [Link] file.

Procedure
1. In the Studio Project window, expand configuration→deploy→WEB-INF:
a. Open file [Link]:
b. Add a servlet-mapping definition for each servlet that you want to add.
Review the defined servlets for an example.
2. Save [Link].

Next steps
After completing this procedure, proceed to “Generate and deploy the ClaimCenter WAR file for Tomcat” on page
80.

Generate and deploy the ClaimCenter WAR file for Tomcat

Before you begin

Before proceeding, complete “Add servlet definitions for Tomcat” on page 80.

About this task

You can build the ClaimCenter WAR file for Tomcat with or without JDBC drivers by using one of the following
commands:

warTomcatDbcp Builds the WAR file with JDBC drivers. ClaimCenter manages the database connection pool.

warTomcatJndi Builds the WAR file without JDBC drivers. JBoss manges a JNDI database connection pool.

Procedure
1. Open a command prompt and navigate to the ClaimCenter installation directory.
80 chapter 4: Installing a ClaimCenter production environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

2. Execute one of the following commands:

gwb warTomcatDbcp
gwb warTomcatJndi
Both commands generate the ClaimCenter WAR file in the ClaimCenter dist/war directory.
3. Before you deploy ClaimCenter to Tomcat, verify that environment variable CATALINA_OPTS has the following
value:

-Xms1024M -Xmx1024M

4. Deploy the package to Tomcat by copying the [Link] file to the webapps directory in your Tomcat server.

Result
As Tomcat starts up, it automatically recognizes ClaimCenter and unpacks the [Link] into a directory structure
within Tomcat\webapps. For this example, Tomcat creates a Tomcat\webapps\cc directory. Each time you deploy a
new copy of a [Link] file, delete the pre-existing cc directory structure created by the old [Link] file.

Next steps
After completing this procedure, review the post-installation tasks in “Additional ClaimCenter setup tasks” on page
87. Then, proceed to “Start ClaimCenter on Tomcat on windows” on page 98.

Installing ClaimCenter on WebLogic in a production environment

To use WebLogic as the ClaimCenter application server, you must create and deploy a WebLogic-specific EAR
package file. Generating the EAR file is a multistep process.

Add a servlet definition for WebLogic

Before you begin

Before proceeding, review “Installing ClaimCenter on WebLogic in a production environment” on page 81.

About this task

You might want to add definitions for additional servlets to the [Link] file.

Procedure
1. In the Studio Project window, expand configuration→deploy→WEB-INF:
[Link] file [Link]:
b. Add a servlet-mapping definition for each servlet that you want to add.
Review the defined servlets for an example.
2. Save [Link].

Next steps
After completing this procedure, proceed to “Enable HTTP authentication on WebLogic” on page 81.

Enable HTTP authentication on WebLogic

Before you begin

Before proceeding, complete “Add a servlet definition for WebLogic” on page 81.

About this task

To authenticate using HTTP authentication on WebLogic, add the following inside the <security-configuration>
element of the WebLogic [Link]:
Installing a ClaimCenter production environment 81
Guidewire ClaimCenter 10.0.0 Installation Guide

<enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>

Next steps
After completing this procedure, proceed to “Generate the ClaimCenter EAR file for WebLogic” on page 82.

Generate the ClaimCenter EAR file for WebLogic

Before you begin

Before proceeding, complete “Enable HTTP authentication on WebLogic” on page 81.

About this task

You can build the ClaimCenter EAR file for WebLogic with or without JDBC drivers by using one of the following
commands:

earWeblogicDbcp Builds the WAR file with JDBC drivers. ClaimCenter manages the database connection pool.

earWeblogicJndi Builds the WAR file without JDBC drivers. JBoss manges a JNDI database connection pool.

Procedure
1. Open a command prompt and navigate to the ClaimCenter installation directory.
2. Execute one of the following commands:
gwb earWeblogicDbcp
gwb earWebLogicJndi
Both commands generate the ClaimCenter WAR file in the ClaimCenter dist/war directory.

Next steps
After completing this procedure, proceed to “Install the ClaimCenter EAR file on WebLogic” on page 82.

Install the ClaimCenter EAR file on WebLogic

Before you begin

Before proceeding, complete “Generate the ClaimCenter EAR file for WebLogic” on page 82.

Procedure
1. Do one of the following:
• If WebLogic is not already running, start it now.
• If WebLogic is running, restart it.
2. After the server is running, point your browser to [Link]
Port 7001 is the default port for WebLogic. If you configured WebLogic with a different port number, then
change the port number in the address to the correct one.
3. Log in with your user name and password.
The default WebLogic user name and password is weblogic.
4. On the left side of the user interface, under Domain Structure, click Deployments.
5. On the next screen, above Domain Structure, click Lock & Edit.
6. Within the main panel, under Deployments, click Install.
7. Navigate to the EAR file you generated and click Next.
8. Select Install this deployment as an application and click Next.
9. In the Source accessibility section of the next screen, select I will make the deployment accessible from the following
location.
82 chapter 4: Installing a ClaimCenter production environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

10. For the location, enter the path to the ClaimCenter webapps directory and click Next.
11. Click Yes, take me to the deployment’s configuration screen and click Finish.
12. Review your configuration and click Activate Changes located on the left side of the screen, above Domain
Structure.

Next steps
After completing this procedure, proceed to “Ways to start ClaimCenter on WebLogic” on page 83.

Ways to start ClaimCenter on WebLogic

It is possible to configure WebLogic to start applications automatically at startup or at restart. In this way, if the
WebLogic server ever goes down, it is possible to start Guidewire ClaimCenter automatically.
If you do not configure WebLogic to automatically start applications, then you need to start ClaimCenter manually.
See “Start ClaimCenter on WebLogic” on page 99 for details.

Installing ClaimCenter on WebSphere in a production environment

To use WebSphere as the ClaimCenter application server, you create and deploy a WebSphere-specific EAR package
file to that application. Generating the EAR file is a multistep process. See the following:
1. “Add a welcome-file-list element to file [Link]” on page 83
2. “Generate the ClaimCenter EAR file for WebSphere” on page 84
3. “Install the ClaimCenter EAR file on WebSphere” on page 84

Important caveats
• Guidewire supports the JDBC drivers shipped with ClaimCenter only for use with externally managed data
sources. Guidewire does not support any default JDBC drivers installed with the application server.
• It is not possible to access Guidewire ClaimCenter locally on WebSphere by using the following standard URL:

[Link]

Instead, use the following URL:

[Link]

Add a welcome‐file‐list element to file [Link]

Before you begin

Before proceeding, review “Installing ClaimCenter on WebSphere in a production environment” on page 83.

About this task

To ensure that it is possible for WebSphere to access ClaimCenter start file [Link], add a welcome-file-list
element to file [Link].

Procedure
1. Launch Guidewire Studio:
a. Open a command prompt and navigate to the ClaimCenter installation directory.
b. Execute the following command:
gwb Studio
2. In the ClaimCenter Project window, expand configuration→deploy→WEB-INF:
a. Open [Link].
Installing a ClaimCenter production environment 83
Guidewire ClaimCenter 10.0.0 Installation Guide

b. At the bottom of the file, just before the </web-app> tag, add the following text:

<welcome-file-list>
<welcome-file>[Link]</welcome-file>
<welcome-file>[Link]</welcome-file>
<welcome-file>[Link]</welcome-file>
</welcome-file-list>

[Link] servlet definitions as needed.

Review the defined servlets for an example.
d. Add a servlet-mapping definition for each servlet that you add.
Review the defined servlets for an example.
3. Save your changes and close [Link].

Next steps
After completing this procedure, proceed to “Generate the ClaimCenter EAR file for WebSphere” on page 84.

Generate the ClaimCenter EAR file for WebSphere

Before you begin

Before proceeding, complete “Add a welcome-file-list element to file [Link]” on page 83.

About this task

You can build the ClaimCenter EAR file for WebSphere with or without JDBC drivers using the following
commands:

earWeblogicDbcp Builds the WAR file with JDBC drivers. ClaimCenter manages the database connection pool.

earWeblogicJndi Builds the WAR file without JDBC drivers. JBoss manges a JNDI database connection pool.

Procedure
1. Open a command prompt and navigate to the ClaimCenter installation directory.
2. Execute one of the following commands:
gwb earWeblogicDbcp
gwb earWeblogicDbcp

Result
Executing either of these commands does the following:
• It builds the EAR file and place it the ClaimCenter dist/ear directory.
• It packages file modules/configuration/deploy/WEB-INF/[Link] in the EAR file.

Next steps
After completing this procedure, proceed to “Install the ClaimCenter EAR file on WebSphere” on page 84.

Install the ClaimCenter EAR file on WebSphere

Before you begin

Before proceeding, complete “Generate the ClaimCenter EAR file for WebSphere” on page 84.

Procedure
1. If WebSphere is not already running, start the application server.
84 chapter 4: Installing a ClaimCenter production environment
 Guidewire ClaimCenter 10.0.0 Installation Guide

2. Open the WebSphere Administrative Console.

3. Click Applications→New Application.
4. Click New Enterprise Application.
5. Click Browse and select the ClaimCenter EAR file in the ClaimCenter installation dist/ear directory.
6. Click Next.
7. Select Fast Path.
8. Click Next.
9. Accept the default installation options.
10. Click Next.
11. On the Map modules to servers screen, verify that your targeted server or cluster is selected.
12. Click Next.
13. On the Metadata for modules screen, click Next.
14. On the Summary screen, review your selections for accuracy. Click Previous to change any settings.
15. Click Finish.
16. Click Save to apply the changes to the master configuration.
17. Click the cc application.
18. Under Detail properties, click Class loading and update detection.
19. Under Class loader order, verify Classes loaded with local class loader first (parent last) is selected.
20. Under WAR class loader policy, verify Single class loader for application is selected.
21. Click OK.
22. Click Save to apply the changes to the master configuration.
23. (Optional) If using JNDI, remove the JDBC JAR files (such as ojdbc<version>.jar or
sqljdbc<version>.jar) from the exploded deployment in the following directory:

<WAS Profile>/installedApps/DefaultCell/[Link]/[Link]/WEB-INF/lib

Next steps
After completing this procedure, review the post-installation tasks in “Additional ClaimCenter setup tasks” on page
87. Then, proceed to “Start ClaimCenter on WebSphere” on page 99.

Installing a ClaimCenter production environment 85

Guidewire ClaimCenter 10.0.0 Installation Guide

86 chapter 4: Installing a ClaimCenter production environment

chapter 5

Additional ClaimCenter setup tasks

This topic describes optional ClaimCenter setup tasks. You perform these tasks after you complete the initial
installation of your ClaimCenter development or production environment and deploy ClaimCenter to your
application server.

Additional installation information

The following topics link to sources for more information.

Integrating ClaimCenter with ContactManager

To integrate ClaimCenter with ContactManager, see the Guidewire Contact Management Guide.

Running ClaimCenter in a clustered environment

Running ClaimCenter in a clustered environment requires an in-depth understanding of ClaimCenter configuration
files. See the System Administration Guide.

Change the Superuser password

About this task
In the base configuration, ClaimCenter automatically creates an unrestricted superuser named su with full
permissions. The default password for this superuser is gw. You create other users with the superuser account.
Guidewire strongly recommends that after you start ClaimCenter for the first time, log in to ClaimCenter as user su
and change this password.
Note: To change which user is the superuser, see the System Administration Guide.

Procedure
1. Ensure that the ClaimCenter application server is running.
2. Open a browser window.
3. Set the URL to the following:

[Link]

For example, if connecting on your local computer, use:

Additional ClaimCenter setup tasks 87
Guidewire ClaimCenter 10.0.0 Installation Guide

[Link]

4. Log into ClaimCenter as user su with password gw.

5. Click the Preferences link on the Desktop and change the password for user su.

Generate Java API libraries

About this task
ClaimCenter provides Java APIs that you can use to integrate your own applications with ClaimCenter. These APIs
are sometimes collectively referred to as the toolkit.
Guidewire recommends that you generate these APIs after your first initial ClaimCenter installation. Because the
toolkit contains the ClaimCenter APIs, regenerate the toolkit after every data model change as well.

Procedure
1. Ensure that the ClaimCenter application server is running.
2. From a command prompt, navigate to the ClaimCenter installation directory.
3. Execute the following command:
gwb genJavaApi
This command generates the java-api directory within the top-level ClaimCenter directory.

Integrating ClaimCenter and PolicyCenter

You can integrate ClaimCenter and PolicyCenter to support claim search from PolicyCenter, policy search from
ClaimCenter, and large loss notification from ClaimCenter to PolicyCenter.

Configure ClaimCenter to retrieve policy information

You can configure ClaimCenter to retrieve policy information from PolicyCenter. In ClaimCenter, you register a
plugin implementation class that uses a PolicyCenter web service to retrieve policy information for a claim.

Before you begin

Ensure that the PolicyCenter application server is running.

About this task

Note: These instructions describe how to set up ClaimCenter 10 to integrate with either PolicyCenter
9 or PolicyCenter 10. If you are integrating ClaimCenter 10 with PolicyCenter 9, use the instructions
in the PolicyCenter 9 documentation for the PolicyCenter side of the integration.

Procedure
1. Open Guidewire Studio™ for ClaimCenter.
2. Navigate in the Project window to configuration→config→Plugins→registry.
3. Open [Link].
4. Click Remove to remove the demonstration implementation,
[Link].
5. Click Add and select Add Gosu Plugin.
88 chapter 5: Additional ClaimCenter setup tasks
 Guidewire ClaimCenter 10.0.0 Installation Guide

6. Enter one of the following for the Gosu Class field, depending on the version of PolicyCenter that you are
integrating with ClaimCenter:
• [Link] for PolicyCenter 10
• [Link] for PolicyCenter 9
7. Navigate in the Project window to configuration→config→suite.
8. Open [Link].
9. Remove the comment markers <!-- and --> from the line for the PolicyCenter URL:

<!--
<product name="pc" url="[Link]
-->

10. Update the PolicyCenter URL to match your server and port.
11. Navigate in the Project window to configuration→config and open [Link].
12. Find configuration parameter PolicySystemURL.
13. Set the value of this parameter to the PolicyCenter application URL.
For example, add the following line to this file:

<param name="PolicySystemURL" value="[Link]

14. Navigate in the Project window to configuration→gsrc and then to [Link].

15. Open one of the following web service files, depending on the version of PolicyCenter that you are integrating
with ClaimCenter:
• [Link] for PolicyCenter 10
• [Link] for PolicyCenter 9
Guidewire defines the ${pc} variable for each of the defined web services in [Link].
16. Select all the web services in Resources and click Fetch .
You must refresh the web services, even if you have made no changes to them.
17. Select the Settings tab and review the contents of the Configuration Provider class
[Link].
This class defines the user name and password that ClaimCenter uses to connect with PolicyCenter.

IMPORTANT Guidewire strongly recommends that you change the user name and password
from the defaults, su and gw, to new values.

18. To test the integration, restart the ClaimCenter server.

19. Open the New Claim wizard.
20. Search for a Personal Auto or Workers' Compensation policy.

Next steps
“Configuring ClaimCenter to convert PolicyCenter objects” on page 89

Configuring ClaimCenter to convert PolicyCenter objects

You can configure the conversion of the objects that PolicyCenter returns to ClaimCenter in file pc-to-cc-data-
[Link].
Guidewire Studio™ for ClaimCenter provides different versions of this file for the version of PolicyCenter that
ClaimCenter is integrating with.
• To access the ClaimCenter [Link] file for PolicyCenter 10, navigate in the Project
window to configuration→config→datamapping→pc→1000.
• To access the ClaimCenter [Link] file for PolicyCenter 9, navigate in the Project window
to configuration→config→datamapping→pc→900.
Additional ClaimCenter setup tasks 89
Guidewire ClaimCenter 10.0.0 Installation Guide

The only object that ClaimCenter sends to PolicyCenter is a PCClaimSearchCriteria object. The ClaimCenter
search criteria create and populate this object through Gosu code. Any configuration that you do for this object must
be done in Gosu code.
The plugin implementation code does not pick up changes to the [Link] file automatically.
After changing the file, restart the ClaimCenter server to propagate your changes.

See also
• “Configure PolicyCenter to retrieve claim information” on page 90
• “Configure ClaimCenter to retrieve policy information” on page 88

Configure PolicyCenter to retrieve claim information

You can configure PolicyCenter to retrieve claim information from ClaimCenter. In PolicyCenter, you register a
plugin implementation class that uses a ClaimCenter web service to retrieve claim information for a policy or
account.

Before you begin

Complete the ClaimCenter side of the configuration, described at “Configure ClaimCenter to retrieve policy
information” on page 88. Additionally, before starting this procedure, ensure that the ClaimCenter application server
is running.

About this task

These instructions describe how to set up PolicyCenter 10 to integrate with either ClaimCenter 10 or ClaimCenter 9.
If you are integrating PolicyCenter 10 with ClaimCenter 9, use the instructions in the ClaimCenter 9 documentation
for the ClaimCenter side of the integration.

Procedure
1. Open Guidewire Studio™ for PolicyCenter.
2. Navigate in the Project window to configuration→config→suite.
3. Open file [Link].
4. Remove the comment markers <!-- and --> from the line for the ClaimCenter URL:

<!--
<product name="cc" url="[Link]
-->

5. Update the ClaimCenter URL to match your server and port.

6. Navigate in the Project window to configuration→gsrc and then to [Link].
7. Open one of the following web service files, depending on the version of ClaimCenter that you are integrating
with PolicyCenter:
• [Link] for ClaimCenter 10
• [Link] for ClaimCenter 9
File [Link] defines the ${cc} variable for the web service.
8. Ensure that ClaimCenter is running, and then select the web service in Resources and click Fetch .
You must refresh the web service, even if you have made no changes to it.
9. Select the Settings tab and review the contents of the listed Configuration Provider class.
This class defines the user name and password that PolicyCenter uses to connect with ClaimCenter.

IMPORTANT Guidewire strongly recommends that you change the user name and password
from the defaults, su and gw, to new values.

10. Navigate in the Project window to configuration→config→Plugins→registry.

90 chapter 5: Additional ClaimCenter setup tasks
 Guidewire ClaimCenter 10.0.0 Installation Guide

11. Open [Link].

12. Click Remove Plugin to remove the following demonstration implementation:
[Link]
13. Click Add Plugin and select Add Gosu Plugin.
14. Enter one of the following plugin implementation classes in the Gosu Class field, depending on the version of
ClaimCenter that you are integrating with PolicyCenter:
• [Link] for ClaimCenter 10
• [Link] for ClaimCenter 9
15. Navigate in the Project window to configuration→config and open [Link].
16. Set the ClaimSystemURL parameter to the ClaimCenter URL.
For example, the base configuration URL in a local ClaimCenter installation is the following:

[Link]

17. Restart the PolicyCenter server to pick up these changes.

Next steps
“Defining authentication between PolicyCenter and ClaimCenter” on page 91

Defining authentication between PolicyCenter and ClaimCenter

PolicyCenter and ClaimCenter define the user name and password used to communicate with the other application
in configuration provider classes.
• PolicyCenter provides the following class that defines the user name and password that PolicyCenter uses to
connect with ClaimCenter:
[Link]
In the base configuration, PolicyCenter defines the user name su and password gw in this class.
• ClaimCenter provides the following class that defines the user name and password that ClaimCenter uses to
connect with PolicyCenter:
[Link]
In the base configuration, ClaimCenter defines the user name su and password gw in this class.

IMPORTANT Guidewire strongly recommends that, as a matter of security, you change the user name
and password that each application defines. You must also supply a corresponding user in the other
application. That new user must have the soapadmin permission, and, at a minimum, the permissions
needed to view claims and policies.

For example:
1. In Studio for PolicyCenter, define a user name and password in CCConfigurationProvider.
2. Log in to the ClaimCenter server and define a user that has the same user name and password that you specify
in CCConfigurationProvider.
3. Assign the user a role that has the soapadmin permission, and, at a minimum, the permissions needed to view
policies and accounts.
4. In Studio for ClaimCenter, define a user name and password in PCConfigurationProvider.
5. Log in to the PolicyCenter server and define a user that has the same user name and password that you specify
in PCConfigurationProvider.
6. Assign the user a role that has the soapadmin permission, and, at a minimum, the permissions needed to view
claims and policies .

See also
• Guidewire Contact Management Guide
Additional ClaimCenter setup tasks 91
Guidewire ClaimCenter 10.0.0 Installation Guide

Configure ClaimCenter to send large loss notification to PolicyCenter

You can configure ClaimCenter to send PolicyCenter a large loss notification whenever the value of the Gross Total
Incurred amount on a claim exceeds a defined threshold.

Before you begin

• “Configure ClaimCenter to retrieve policy information” on page 88
• “Configure PolicyCenter to retrieve claim information” on page 90

About this task

Ensure that the PolicyCenter application server is running. It is not necessary for the ClaimCenter server to be
running.

Procedure
1. Open Guidewire Studio™ for ClaimCenter.
2. Navigate in the Project window to configuration→config→Rule Sets and then:
a. Navigate to Preupdate→TransactionSetPreupdate and select the check box that enables the rule TPU05000 -
Large Loss Notification.
b. Navigate to EventMessage→EventFired and select the check box that enables the rule EFR06000 - Policy
System Notification.
3. Expand configuration→config→Messaging.
4. Open [Link] in the Messaging editor.
5. Select the following messaging destination:

ID-69, Name=[Link]

6. Clear the Disable destination check box at the top right of the editor to enable this message destination.
7. In the Project window, expand configuration→config→Plugins→registry.
8. Open [Link] in the plugin editor.
9. Clear the Disabled check box under the Server: field.
10. Open [Link].
The editor for this plugin opens with the default plugin implementation selected.
11. Remove the demonstration implementation by clicking the Remove Plugin icon.
12. Click Add Plugin and select Add Gosu Plugin.
13. Enter the following for the Gosu Class field:

[Link]

14. If you have not done so already, update [Link] to enable ClaimCenter to work with PolicyCenter.
a. Navigate in the Project window to configuration→config→suite.
b. Open [Link].
c. If present, remove the comment markers <!-- and --> from the line defining the PolicyCenter URL:

<!--
<product name="pc" url="[Link]
-->

d. If necessary, change the URL for the PolicyCenter server to the URL used in your configuration.
15. If you have not done so already, set the PolicyCenter URL in the PolicySystemURL configuration parameter:
a. In the Studio Project window, expand configuration→config.
b. Open [Link].
c. Set the PolicyCenter URL in the PolicySystemURL configuration parameter.
92 chapter 5: Additional ClaimCenter setup tasks
 Guidewire ClaimCenter 10.0.0 Installation Guide

For example, add the following line to this file:

<param name="PolicySystemURL" value="[Link]

16. Navigate in the Project window to configuration→gsrc and then to [Link].

17. Double-click [Link] to open this web service collection in the editor.
18. Select the following web service in Resources:
${pc}/ws/gw/webservice/pc/pc1000/ccintegration/ClaimToPolicySystemNotificationAPI?wsdl
File [Link] defines the ${pc} variable for the web service.
19. Ensure that the PolicyCenter server is running, and then click Fetch to refresh the web service.
You must refresh the web service, even if you have made no changes to it.
20. Click the Settings tab and review the contents of the Configuration Provider class
[Link].
This class defines the user name and password that ClaimCenter uses to connect with PolicyCenter.

IMPORTANT Guidewire strongly recommends that you change these values from their default
su and gw values.

21. Restart the ClaimCenter server so these changes take effect.

Next steps
“Test ClaimCenter large loss notification integration with PolicyCenter” on page 93

Test ClaimCenter large loss notification integration with PolicyCenter

Before you begin
“Configure ClaimCenter to send large loss notification to PolicyCenter” on page 92

About this task

In a development system, it is possible to test the large loss notification integration between ClaimCenter 10 and
PolicyCenter 10.

Procedure
1. Log into Guidewire ClaimCenter.
2. Add a claim in ClaimCenter with a loss that exceeds the threshold for that type of claim.
3. Log into Guidewire PolicyCenter.
4. Review the activities for the policy associated with the claim and verify that ClaimCenter successfully created
a large loss notification.

Result
If the integration works correctly, PolicyCenter adds a referral reason and an activity for that policy.

Archiving in a production environment

After you enable ClaimCenter archiving, you cannot disable archiving entirely unless you drop the application
database. Additionally, after enabling archiving, even if you then disable archiving, you still see references to Claim
archiving.
Do not attempt to disable archiving in a production environment after you have enabled this functionality.
Additional ClaimCenter setup tasks 93
Guidewire ClaimCenter 10.0.0 Installation Guide

WARNING Do not attempt to reset the value of ArchiveEnabled from true to false. After you
set ArchiveEnabled to true and start the server, you cannot change the value of this parameter
again. If you reset the value to false, the server does not start. Also, do not remove the archive
work queue. Removing this work queue after enabling archiving prevents that application server
from starting.

Implementing claim archiving

If you intend to implement Claim archiving in your production ClaimCenter environment, first test the end-to-end
archiving process in a development environment.

Disabling claim archiving

If you do not intend to implement Claim archiving in your production ClaimCenter environment, do the following:
• Accept the default archiving configuration, which Guidewire disables by default.
• Manually disable all unused archiving configuration elements.

See also
• “Archiving in a development environment” on page 56
• “Enable archiving in Guidewire ClaimCenter” on page 56
• “Disabling Guidewire ClaimCenter archiving” on page 57
• Application Guide

Connecting a web client to ClaimCenter

Users connect to ClaimCenter through a web browser. The URL for ClaimCenter or ContactManager includes the
server name, port, and application name. For example:

[Link]

[Link]

The following list shows default port numbers used by the application servers supported by ClaimCenter. You can
configure the application server to listen on a different port than the default.

QuickStart • 8080 – ClaimCenter

• 8180 – PolicyCenter
• 8280 – ContactManager
• 8580 – BillingCenter
JBoss 8080
Tomcat 8080
WebLogic 7001
WebSphere 9080

Supply users with a user name and password along with the URL for your installation.

See also
• See “Web client information” on page 46 for a list of required software and hardware for client computers
accessing ClaimCenter.
94 chapter 5: Additional ClaimCenter setup tasks
 Guidewire ClaimCenter 10.0.0 Installation Guide

Configure Microsoft Windows accessibility for Firefox

About this task
If a user clicks a cell in an editable list view, the dotted border around action elements, such as links, cells, and radio
buttons, is not visible. However, if the user tabs into the same list view, the dotted border is visible. Firefox uses a
Windows accessibility setting to determine this behavior.

Procedure
1. Click Start→Control Panel→Ease of Access Center→Make the keyboard easier to use.
2. Click Underline keyboard shortcuts and access keys.
3. Click OK.
4. Restart Firefox.

About single sign‐on authentication

It is possible to configure ClaimCenter to use single sign-on (SSO) authentication. In single sign-on operation, as the
user logs into ClaimCenter:
• ClaimCenter generates a unique Cross-Site Request Forgery (CSRF) token for the user session.
• ClaimCenter forwards user information, including the CSRF token, to the authentication provider.
• The authentication provider checks the credentials for the user.
• The authentication provider returns an authentication confirmation back to ClaimCenter if the credentials are
valid.
ClaimCenter includes the CSRF token in each authentication request and uses the CSRF token to verify the
legitimacy of the user request.

See also
• Integration Guide

Configure single sign‐on authentication

About this task
Guidewire provides the following configuration as a basic example. Use this example to develop more complicated
authentication features, such as redirecting users to different failure pages depending on the failure reason and so
forth.

Procedure
1. Create custom Gosu class [Link]:
a. Open Guidewire Studio™ for ClaimCenter.
b. In the Studio Project window, expand configuration→gsrc.
c. Right-click gsrc and click New→Package.
d. Enter a package name for upgrade purposes.
For example, enter something such as [Link].
e. Right-click the newly created package and click New→Gosu Class.
f. Enter CustomAuthServlet as the name for the class and click OK.
g. Enter the following class definition:

package [Link]

uses [Link]
uses [Link]

Additional ClaimCenter setup tasks 95

Guidewire ClaimCenter 10.0.0 Installation Guide

uses [Link]
uses [Link]
uses [Link]
uses [Link]
uses [Link]
uses [Link]
uses [Link]
uses [Link]
uses [Link]
uses [Link]

@Servlet( \ path : String ->[Link]( "/ssosaml" ) )

class CustomAuthServlet extends HttpServlet {
override function doPost(req: HttpServletRequest, resp: HttpServletResponse) {
var user:User = [Link](req, true);
if (user != null) {
redirectToIndex(req, resp);
return;
}

// try to login
try {
[Link](req);
} catch (e : LoginException) {
respondUnauthorized(req,resp);
return;
}

var serviceToken:ServiceToken = [Link];

if (serviceToken == null || ![Link]) {
respondUnauthorized(req,resp);
} else {
// store token
[Link](false).setAttribute(WebServlet.SERVICE_TOKEN_SESSION_ATTR, serviceToken);
redirectToIndex(req, resp);
}

return;
}

private function respondUnauthorized(req:HttpServletRequest, resp:HttpServletResponse) {

print("User is unauthorized")
redirectToError(req, resp);
}

private function redirectToIndex(req:HttpServletRequest, resp:HttpServletResponse) {

print("User is authorized. Send to index page.")
var plugin:IBaseURLBuilder = (IBaseURLBuilder) [Link]("BaseURLBuilderPlugin");
var ccStartupPageEP = "ClaimCenterStartupPageEP"
[Link]([Link](req) + "/" + ccStartupPageEP + ".do");
}

private function redirectToError(req:HttpServletRequest, resp:HttpServletResponse) {

print("User is unauthorized. Send to Default Failure page.")
var plugin:IBaseURLBuilder = (IBaseURLBuilder) [Link]("BaseURLBuilderPlugin");
var defaultFailureEP = "DefaultFailureEP"
[Link]([Link](req) + "/" + defaultFailureEP + ".do");
}
}

2. Add your custom servlet to the list of valid ClaimCenter servlets:

a. Expand configuration→config→servlets.
b. Open [Link].
c. Add the name of your custom servlet to the list.
For example:

<servlet class="[Link]"/>

3. Create custom Gosu class [Link] and place the class in your custom authentication package.
For example:

package [Link]

uses [Link]

96 chapter 5: Additional ClaimCenter setup tasks

 Guidewire ClaimCenter 10.0.0 Installation Guide

uses [Link]
uses [Link]
uses [Link]
uses [Link]
uses [Link]

class AuthServicePlugin implements AuthenticationServicePlugin {

var _handler: AuthenticationServicePluginCallbackHandler;
override function authenticate(p0: AuthenticationSource): String {
if (p0 typeis UserNamePasswordAuthenticationSource == false) {
throw new IllegalArgumentException("Authentication source type " + [Link]().getName() +
"is not known to this plugin");
}
var uNameSource:UserNamePasswordAuthenticationSource = (UserNamePasswordAuthenticationSource) p0 ;
var username = [Link];
var userPublicId = _handler.findUser(username);
if (userPublicId == null) { throw new FailedLoginException("Bad user name " + username);}
return userPublicId;
}

override function setCallback(p0: AuthenticationServicePluginCallbackHandler) {

_handler = p0;
}
}

4. Create custom Gosu class [Link] and place the class in your custom authentication package.
For example:

package [Link]

uses [Link]
uses [Link]
uses [Link]
uses [Link]

class AuthSourceCreator implements AuthenticationSourceCreatorPlugin {

override function createSourceFromHTTPRequest(p0: HttpServletRequest): AuthenticationSource {

var source:AuthenticationSource;
var userName:String = [Link] ("username");
var password:String = [Link]("password");

print("userName\t" + userName)
print("password\t" + password)

source = new UserNamePasswordAuthenticationSource(userName, password);

return source;

}
}

In your code, check for errors and throw InvalidAuthenticationSourceData if there are errors.
5. Associate your custom AuthServicePlugin class with the AuthenticationServicePlugin plugin.
a. Expand configuration→config→Plugins→registry:
b. Open [Link].
c. Click to remove the default plugin.
d. Click and select Add Gosu Plugin.
e. For Gosu Class, enter the [Link] class, including the fully qualified package.
6. Associate your custom AuthSourceCreator class with the AuthenticationSourceCreatorPlugin plugin.
a. Open [Link].
b. Click to remove the default plugin.
c. Click and select Add Gosu Plugin.
d. For Gosu Class, enter the [Link] class, including the fully qualified package.
7. Create an entry point for the ClaimCenter entry page:
a. Expand configuration→config→Page Configuration→pcf, right-click entrypoints and click New→PCF file.
b. Enter ClaimCenterStartupPageEP for the file name.
Additional ClaimCenter setup tasks 97
Guidewire ClaimCenter 10.0.0 Installation Guide

c. Select Entry Point for the file type and click OK.
d. Select the entry point.
e. Set location to ClaimCenterStartupPage().
f. Set authenticationRequired to false.
8. Create an entry point for the default failure page.
a. Right-click entrypoints and click New→PCF file.
b. Enter DefaultFailureEP for the file name.
c. Select Entry Point for the file type and click OK.
d. Select the entry point.
e. Set location to DefaultFailurePage().
f. Set authenticationRequired to false.
9. Create a BaseURLBuilderPlugin plugin implementation:
a. Right-click configuration→config→Plugins→registry and click New→Plugin.
b. Enter BaseURLBuilderPlugin for the name.
c. Enter IBaseURLBuilder for the interface and click OK.
d. Click and select Add Java Plugin.
e. Enter [Link] for the Java Class.
10. Test your work:
a. Create a test HTML page on your local ClaimCenter server.
b. Include the following form on the HTML page:

<form name="input" action="[Link] method="post">

Username: <input type="text" name="username">
Password: <input type="text" name="password">
<input type="submit" value="Submit">
</form>

Starting ClaimCenter on the application server

How you start Guidewire ClaimCenter depends on the specific application server that you use.

See also
• System Administration Guide

Start ClaimCenter on JBoss

About this task
After installing ClaimCenter on JBoss, ClaimCenter starts as you start JBoss. To start JBoss, use the run command
in the JBoss bin directory. If you execute the run command without any parameters, the command launches JBoss
using the default server configuration.

Start ClaimCenter on Tomcat on windows

About this task
After installing ClaimCenter on Tomcat, ClaimCenter starts as you start Tomcat. To start the Tomcat server on
Windows, run the following script from the Tomcat installation directory:
bin/[Link]
98 chapter 5: Additional ClaimCenter setup tasks
 Guidewire ClaimCenter 10.0.0 Installation Guide

Start Tomcat in same command prompt

About this task
By default, Tomcat starts up in a new window. If Tomcat encounters startup errors, the new window often closes
automatically far too quickly for you to read any error messages in it. To run Tomcat from the same command
prompt in which you entered the startup command, perform the following steps:

Procedure
1. Locate the line in the script that runs Tomcat:

[Link]: call "%EXECUTABLE%" start %CMD_LINE_ARGS%

2. Change the start option in the command to run.

3. Save the script, and then run the script again.
Tomcat then runs in the same command window, which you can use to view any error messages.

Start ClaimCenter on WebLogic

Procedure
1. Start the WebLogic Administration Server if it is not already running.
2. Open the WebLogic Administration Console.
3. Under Domain Structure, click Deployments.
a. Select the check box for ClaimCenter.
b. Click Start→Servicing all requests.
The WebLogic Administration Console informs you of the deployments that you selected to be started.
c. Click Yes.
4. Navigate to and select the ClaimCenter application.
WebLogic identifies ClaimCenter by the name that you gave to the deployed EAR file.
5. Click Deploy Application.
This step launches the ClaimCenter server. The application start process can take a few minutes to complete.

Start ClaimCenter on WebSphere

About this task
Guidewire does not support stopping and restarting the ClaimCenter server with the WebSphere Application Server
(WAS) tools alone. Instead, to stop the ClaimCenter application, shut down the WebSphere server itself.

Procedure
1. Open the WebSphere Administrative Console.
2. Click Applications→Application Types→WebSphere enterprise applications.
3. Select the check box next to the ClaimCenter application, abbreviated by default as cc.
4. Do one of the following:
• If ClaimCenter is already running, and you want to restart ClaimCenter, restart WebSphere.
• If ClaimCenter is not running, click Start. It is possible for ClaimCenter to take a few minutes to start.

Tune memory settings for application processes

If a particular process is running slowly, you can increase the amount of memory available to it by tuning a set of
memory parameters. It is possible that the additional memory allocation can improve the process performance. Use
Additional ClaimCenter setup tasks 99
Guidewire ClaimCenter 10.0.0 Installation Guide

the following table to identify the parameters that you can change in file [Link], in the ClaimCenter
installation directory.

Property Description Possible values Default

values
custDistGosuCompileMaxHeapSize Maximum heap size for the JVM that The number of giga‐ 16g
performs Gosu compilation. bytes, followed by
the letter g.
custDistGosuCompileMinHeapSize Minimum heap size for the JVM that The number of giga‐ 2g
performs Gosu compilation. bytes, followed by
the letter g.
custDistGosudocMaxHeapSize Maximum heap size for the JVM that The number of giga‐ 16g
performs Gosudoc generation. bytes, followed by
the letter g.
custDistGosudocMinHeapSize Minimum heap size for the JVM that The number of giga‐ 2g
performs Gosudoc generation. bytes, followed by
the letter g.
custDistJavaCompileMaxHeapSize Maximum heap size for the JVM that The number of giga‐ 16g
performs Java compilation. bytes, followed by
the letter g.
custDistJavaCompileMinHeapSize Minimum heap size for the JVM that The number of giga‐ 4g
performs Java compilation. bytes, followed by
the letter g.
custDistJavaCompileSchemaSourcesMaxHeapSize Maximum heap size for the JVM that The number of giga‐ 16g
performs compilation of XML schema bytes, followed by
generated source for the task the letter g.
genSchemaJar.

custDistJavaCompileSchemaSourcesMinHeapSize Minimum heap size for the JVM that The number of giga‐ 4g
performs compilation of XML schema bytes, followed by
generated source for the task the letter g.
genSchemaJar.

custDistJavaExecMaxHeapSize Maximum heap size for all of the tasks The number of giga‐ 4g
that run in a separate JVM, such as bytes, followed by
genDataDictionary. the letter g.
custDistStudioMaxHeapSize The maximum amount of memory The number of giga‐ 4g
available to Guidewire Studio. bytes, followed by
See the Configuration Guide. the letter g.

custDistStudioBuildProcessHeapSize The initial default value for the Build The number of meg‐ 6000
process heap size setting in the abytes.
Guidewire Studio Settings dialog. After
you run Studio for the first time, this
property is ignored.
See the Configuration Guide.
[Link] Minimum and maximum heap sizes for Minimum: -Xms, fol‐ -Xms1g
the JVM that runs the remaining tasks, lowed by the num‐ -Xmx4g
such as codegen. ber of gigabytes, fol‐
lowed by the letter
g.
Maximum: -Xmx, fol‐
lowed by the num‐
ber of gigabytes, fol‐
lowed by the letter
g.

100 chapter 5: Additional ClaimCenter setup tasks

chapter 6

Configuring free‐text search

This topic describes optional ClaimCenter setup tasks. You perform these tasks after you complete the initial
installation of your ClaimCenter development or production environment and deploy ClaimCenter to your
application server.

About free‐text search

The full-text search engine is a special distribution of Apache Solr, tailored by Guidewire to work with free-text
search. This special distribution is called the Guidewire Solr Extension.

Overview of free‐text search setup

ClaimCenter free-text search depends on a full-text search engine, the Guidewire Solr Extension. In a production
environment, Guidewire supports running the Guidewire Solr Extension in a standalone mode. In a development
environment, Guidewire supports running the Guidewire Solr Extension in the bundled QuickStart server, if you
configure free-text search for embedded operation.

See also
• Configuration Guide

Free‐text search options for production and development

In a production environment, you must configure the free-text search for external operation. With external operation
in a production environment, the Guidewire Solr Extension must run in a different instance of the application server
than the instance that runs your ClaimCenter application.
In a development environment, you can configure free-text search for external or embedded operation. With external
operation in a development environment, the Guidewire Solr Extension runs in a Java Virtual Machine (JVM)
instance rather than in the server that runs your ClaimCenter application. With embedded operation, the Guidewire
Solr Extension runs automatically as part of the ClaimCenter application in the application server instance that runs
ClaimCenter, not as a separate application.
You can configure free-text search for external or embedded operation in development environments installed on a
Tomcat application server or on the bundled QuickStart application server. You can configure free-text search only
for external operation in development environments installed on other supported application servers. Production
environments support only external operation regardless of application server.
Configuring free‐text search 101
Guidewire ClaimCenter 10.0.0 Installation Guide

Simplified free‐text search setup with embedded operation

In a development environment, set up the free-text search for embedded operation to simplify your setup procedure.
Your only set-up task in embedded operation involves changes to the [Link] file. This file
configures how ClaimCenter works with the Guidewire Solr Extension, including connection information, and
whether the mode of operation is external or embedded.

See also
• “Configure free-text search for embedded operation” on page 105

Guidewire Solr extension

Guidewire provides a special distribution of the Apache Solr full-text search engine, the Guidewire Solr Extension.
Guidewire provides the Guidewire Solr Extension in a Zip file in the following location in the ClaimCenter
installation directory:
solr/[Link]
The Guidewire Solr Extension runs self-hosted in a production-grade Jetty container server. If you configure the
Guidewire Solr Extension for embedded operation, it operates as part of ClaimCenter, not as a separate web
application.

WARNING Do not use any distribution of the Apache Solr full-text search engine other than the
one that Guidewire provides as the Guidewire Solr Extension.

Guidewire Solr home directory

Before you implement free-text search, you must create an installation directory for the Guidewire Solr Extension.
The installation directory is known as the Guidewire Solr home directory. Guidewire requires that you create the
Guidewire Solr home directory on the host on which you installed the separate application server instance for it.
Note: Do not create a Guidewire Solr home directory if you configure free-text search for embedded
operation.
The default parameter settings and configuration files for free-text search assume the following directories for the
Guidewire Solr home directory:
• Unix – /opt/gwsolr
• Windows – C:\opt\gwsolr
All Guidewire free-text setup instructions assume the use /opt/gwsolr for the Guidewire Solr home directory. If
you do not install the Guidewire Solr Extension in its default directory, you must perform additional configuration
steps.

Free‐text batch load command

The Guidewire Solr Extension provides a command-line utility to extract policy data from the ClaimCenter
relational database and load the extracted data into the Guidewire Solr Extension.
Note: Do not set up and configure the free-text batch load command if you configure free-text search
for embedded operation. Instead, use the Solr Data Import batch process.
The free-text batch load command depends on a Unix-compatible sort binary that performs character-value sorting.
The batch load command builds intermediate index documents from policy claim-contact data in ClaimCenter. The
batch load command sorts the intermediate documents during its process of collating and compiling the final index
documents that it loads into the Guidewire Solr Extension. Guidewire supports cygwin on Windows.

See also
• “About the free-text batch load command” on page 107
• Configuration Guide
102 chapter 6: Configuring free‐text search
 Guidewire ClaimCenter 10.0.0 Installation Guide

Securing database credentials for free‐text batch load

Free-text batch load for the production instances of the Guidewire Solr Extension requires the ClaimCenter
production database credentials. You must keep these credentials secure. To this end, Guidewire strongly
recommends that you load the database credentials that batch load requires from a separate property file. This
property file must be stored in a secure location. Alternatively, list the property file in a transient OS environment
variable set within the batch load launch script.
The following example contains the batch load database credentials of a property file called [Link]:

[Link]=scott
[Link]=tiger

Guidewire discourages you from placing this property file or any other file requiring security in the document conf
folder or in the Solr home folder. Guidewire Solr Extension uploads files from these locations into ZooKeeper. If the
property file is in either of these locations, the security for the file will be compromised.
Instead, create a new folder either under the Solr root folder or the document folder. Consider naming such a new
folder secure. In addition, use operating system tools to restrict access to the property file.
When addressing property files, adhere to the following guidelines. Refer to the Solr home folder using $
{solrRoot}. Refer to the document folder using ${documentRoot}. Prefix OS environment variable references with
osenv.
A new node exists in the [Link] file that allows you to inject the proper credentials file for
interacting with Guidewire Solr Extension. The name of the node is solrCredentials. In addition, the batchload-
[Link] file supports a variety of mechanisms for property substitution. This combination of features allows you
to avoid hard coding credentials consistent with the Guidewire recommendation:

<document>

...

<-- The property file referenced here defines the [Link] and [Link] properties -->
<propertyFilename="${documentRoot}/secure/[Link]"/>

...

<-- The solrCredentials node uses the [Link] and [Link] properties -->
<solrCredentials username="${[Link]}" password="${[Link]}"/>

...

</document>

The following code example uses the property file for the database credentials in the datasource URL:

<dataSourcename="ds_orcl"driver="[Link]"url="jdbc:oracle:thin:${[Link]}/${[Link]}/
gwapp@testhost:1521:orcl"env="test"/>
<dataSourcename="ds_orcl"driver="[Link]"url="jdbc:oracle:thin:${osenv.DB_USER}/${osenv.DB_PASSWORD}/
gwapp@testhost:1521:orcl"env="test"/>

Securing Guidewire Solr Extension

Securing Guidewire Solr Extension both for the server and the client requires two key configurations. The first is the
requirement of basic authentication. The second is the activation of SSL.

Requiring authentication in Guidewire Solr Extension

Guidewire recommends that you secure communications between ClaimCenter and the Solr application. To this end,
you can configure both ClaimCenter and the Solr application for basic authentication. Note that if you do configure
ClaimCenter or the Solr application for basic authentication, Guidewire recommends that you also configure the
respective application to run with SSL activated. Otherwise, basic authentication will not provide effective security.
Configuring free‐text search 103
Guidewire ClaimCenter 10.0.0 Installation Guide

Configuring ClaimCenter to use basic authentication when communicating with Solr

To configure ClaimCenter to use basic authentication when communicating with Solr, one alternative is to store
username and password properties in the [Link] file. The following code example shows how to
store these properties in an HTTP server environment:

<solrserver name="solr_instance_name" type="http">

<param name="host" value="localhost"/>
<param name="port" value="8983"/>
<param name="securetransport" value="true"/>
<param name="username" value="solr_user"/>
<param name="password" value="the_password"/>
</solrserver>

If you are in a cloud server environment, substitute cloud for the type property assignment as in the following
example:

<solrserver name="solr_cloud_name" type="cloud">

<param name="zkhosts" value="localhost:2181/cc"/>
<param name="username" value="solr_user"/>
<param name="password" value="the_password"/>
</solrserver>

Note: Guidewire does not recommend using this alternative in production for security reasons. Clear
text credentials can upload to a ZooKeeper installation in the cloud environment. ZooKeeper is
accessible by HTTP and is not secure.
As an alternative to using clear text credentials, use the Credentials plugin. If you register this plugin, the Solr
server manager inside the Guidewire Solr Extension will request credentials for the SOLR key. If the plugin returns
credentials in response to such a request, the credential values will supersede any clear text credentials in the
[Link] file.

Configuring the Solr application for basic authentication

To configure the Solr application to use basic authentication, you must define credentials for it. Defining credentials
for the Solr application requires producing a credentials hash. To create this hash, use the commands called
[Link] and [Link] for a given username and password pair. These commands are in the /opt/
gwsolr/cc/bin folder by default. An example of how to use a createuser command is as follows:

C:\opt\gwsolr\cc\bin>.\createuser
Usage: createuser -user username [-password password] [-solrhome solrhome_folder] [-debug]

In the createuser command, if you enter a username without a password, you will receive a prompt to create a
password. Otherwise, you will receive the following instruction:

Add the following entry to the authentication section of $SOLR_HOME/[Link].

"credentials": {
"solr": "LkbT+UV72dlWq8zT/e9hyGFIIZSocHwQtK/h1P/4N2g= gN6KFzYNlIv0wgIyQvHUx+yX8phzY6OivyRGnpyp2to="
}
Be sure to enable the SOLR_AUTH* properties in bin/[Link] or bin/[Link].

If you include the solrhome option in the createuser command and no [Link] file exists at the solrhome
location, the file will be created with default content. This default content will include the generated password hash.

See also
• [Link]
authentication-plugin

Configuring Guidewire Solr Extension to run with SSL activated

You can configure both the Guidewire Solr Extension server and Guidewire Solr Extension clients to run with SSL
activated. Note that if you do configure the server or clients in this way, Guidewire recommends that you also
104 chapter 6: Configuring free‐text search
 Guidewire ClaimCenter 10.0.0 Installation Guide

configure the respective server or clients for basic authentication. Otherwise, running the respective server or clients
with SSL activated will not provide effective security.

Configuring Guidewire Solr Extension server to run with SSL activated

Single HTTP server configuration
In a single HTTP server configuration, set the securetransport property to true in the corresponding
solrserver element of the [Link] file. The following code example shows this configuration:

<solrserver name="solr_ssltest_instance" type="solrhost">

<param name="host" value="localhost"/>
<param name="port" value="8983"/>
<param name="securetransport" value="true"/>
</solrserver>

In addition, configure the appropriate certificates in accordance with instructions for the underlying Java Virtual
Machine (JVM) or application server.

Cloud server configuration

In a cloud server configuration, set the security flag that enables Guidewire Solr Extension instances for secure
transport. To set the flag, run the gwzkcli - zkhost command as the following Windows example shows:

gwzkcli -zkhostlocalhost:2181 -cmd put /cc/[Link] {"urlScheme":"https"}

Note: In configuring the security for Guidewire Solr Extension batch load, follow the same
instructions as for the corresponding Guidewire Solr Extension server type. In addition, configure a
public certificate for the JVM running batch load in accordance with standard JVM properties. These
property settings will be in either the [Link] file or the [Link] file.

Configuring Guidewire Solr Extension clients to run with SSL activated

In both standalone and cloud client configurations, configure security certificates and other environment variables.
These settings include the SOLR_HOME variable. Configure the security certificates and environment variables in
[Link] or [Link] in accordance with Apache instructions.

See also
• Configuration Guide
• [Link]

Configure free‐text search for embedded operation

Set up free-text search for embedded operation for preliminary testing with small amounts of test data. For final
testing with larger volumes of data and to prepare for production, set up free-text search for external operation. It is
only possible to set up free-text search for embedded operation in development environments.

Set up free‐text search for embedded operation on QuickStart

About this task
You can set up free-text search on QuickStart for embedded operation only in a development environment.

Procedure
1. In Studio Project window, expand configuration→config→solr:
a. Open [Link].
b. Verify that the file contains a <solrserver> element that matches the following:
Configuring free‐text search 105
Guidewire ClaimCenter 10.0.0 Installation Guide

<solrserver name="embedded" type="embedded">

<param name="provision" value="true"/>
<param name="solrroot" value="/opt/gwsolr"/>
</solrserver>

c. In the <document> element, change the servername attribute to embedded.

<document name="claimcontact" archive="false" servername="embedded"/>

2. Save your changes to the [Link] file.

3. Open a command prompt in the ClaimCenter installation directory and run the following command:
gwb packageSolr

Next steps
After completing this procedure, proceed to the Configuration Guide.

Set up free‐text search for embedded operation on Tomcat

About this task

It is possible to set up free-text search in a development environment on Tomcat for either embedded or external
operation. For embedded operation, you must include the gwsolrzip parameter in the solrserver element to
specify the absolute path to the [Link] file in your ClaimCenter home directory.

Procedure
1. In the Studio Project window, expand configuration→config→solr:
a. Open [Link].
b. Verify that the file contains a <solrserver> element that matches the following:

<solrserver name="embedded" type="embedded">

<param name="provision" value="true"/>
<param name="solrroot" value="/opt/gwsolr"/>
<param name="gwsolrzip" value="/dev/ClaimCenter/solr/[Link]">
</solrserver>

c. In the <document> element, change the servername attribute to embedded.

<document name="claimcontact" archive="false" servername="embedded"/>

2. Save your changes to the [Link] file.

3. Open a command prompt in the ClaimCenter installation directory and run the following command:
gwb packageSolr

Next steps
After completing this procedure, proceed to the Configuration Guide.

Configure free‐text search for external operation

Before you begin
ClaimCenter free-text search requires that you set up a Guidewire Solr Extension instance separate from the server
instance that runs your ClaimCenter application.
106 chapter 6: Configuring free‐text search
 Guidewire ClaimCenter 10.0.0 Installation Guide

Note:
The ClaimCenter base configuration presets a number of items of which two are of emphasis here.
First, ClaimCenter automatically sets the SOLR_HOME environment variable with a relative path. In a
Microsoft Windows context, the application configures the variable in the [Link] path. In a
Linux or Mac context, the application configures the environment variable in the [Link] path.
You do not need to set the SOLR_HOME environment variable.
Second, the ClaimCenter base configuration accounts for logging. You do not need to change the
logging settings to configure free-text search.

Procedure
1. On the host where the Guidewire Solr Extension instance for free-text search will reside, create an installation
directory to use as the Guidewire Solr home directory. For example:
Unix – /opt/gwsolr/cc
Windows – C:\opt\gwsolr\cc
This topic uses /opt/gwsolr/cc as the Guidewire Solr home directory name.
2. Extract file /solr/[Link] on the ClaimCenter host into the folder you created on the Guidewire Solr
Extension host.
3. Start Guidewire Solr Extension by performing one of the following from the \opt\gwsolr\pc\bin directory:
• If you want Guidewire Solr Extension to operate in standard fashion, run the following command:
solr start -p. In the solr command, the -p option indicates the port number.
• If you want to access the Guidewire Solr Extension with a remote debugger, run the following command:
solr start -p 8983 -a [Debug Arguments]
As a result, you can connect a remote debugging session through port 8000.
4. Examine the logs to ensure the Guidewire Solr Extension web application started successfully. Find the logs at
\opt\gwsolr\pc\server\logs. One such log file is [Link].
The application started successfully if you see a number of log entries related to cc-policy-active.
5. In a browser, open the administrative user interface for the Guidewire Solr Extension web application by
entering the following URL:

[Link]

6. Verify that you see links to administrative pages for each entity type that is searchable in ClaimCenter with
free-text search.
For example, click Core Admin to see information for the cc_claimcontact_active core.

Next steps
After completing this procedure, proceed to “About the free-text batch load command” on page 107.

About the free‐text batch load command

On Windows, ensure that a Unix-compatible sort binary that performs character-value sorting is available.
Note: Do not set up and configure the free-text batch load command if you configure free-text search
for embedded operation. Instead, use the Solr Data Import batch process.

Free‐text search configuration files

Guidewire stores the configuration files that you modify during setup, including the batch load command itself, in
the following directory:
/opt/gwsolr/cc/solr/claimcontact_active/conf
If you created additional index document types, you need to modify the configuration files and the batch load
command, in the following directory for each document type:
Configuring free‐text search 107
Guidewire ClaimCenter 10.0.0 Installation Guide

/opt/gwsolr/cc/solr/documenttype_active/conf
Guidewire locates most of the setup information for the free-text batch load command in a configuration file,
[Link].

Free‐text search configuration parameters

The following list describes the configuration parameters that you may need to modify in the batchload-config
file:

Configuration parameter Description

absolutePathToSortExe Location of a sort binary. You must modify this parameter if you use a binary other
than /bin/sort on Unix or c:\cygwin\bin\[Link] on Windows.
absolutePathToSortTmpDir Location of a working directory into which the sort binary writes its intermediate files.
This directory may be the same as, or different from, the directory specified by
absolutePathToWorkDir.

absolutePathToWorkDir Location of a working directory, possibly on a remote host, for collating and compiling
large volumes of index documents for the full‐text search engine. Generally in a produc‐
tion environment, you modify this parameter. Otherwise, the working directory is within
the Guidewire Solr home directory. Ensure the directory that you specify has sufficient
high‐performance disk space.
If you change this value, you must make a matching change to [Link].
dataSource Connection information for the ClaimCenter relational database. You must modify this pa‐
rameter to specify the network location of the database and the username and password.
documentRoot Highest directory where documents for Guidewire Solr Extension are stored. The default
value for this parameter is ${solrRoot}/pc/solr/policy_active.
solrRoot Highest directory where Guidewire Solr Extension files are stored. The directory is where
you extract the Guidewire Solr Extension .zip installation file. The default value for this
parameter is /opt/gwsolr.
solrServerConfigFile Locates the configuration file that controls how the free‐text feature in ClaimCenter oper‐
ates and interacts with the Guidewire Solr Extension. You must modify this parameter if
your Guidewire Solr Extension home directory is other than /opt/gwsolr.
xsi:noNamespaceSchemaLocation Location of the XSD for batch load configuration files. You must modify this parameter if
your Guidewire Solr home directory is other than /opt/gwsolr.

For Windows paths, you can use the forward slash (/) character as the path separator. If your Guidewire Solr home
directory is on a different Windows drive than your ClaimCenter installation directory, you must specify the drive
letter as well.
Note: You can substitute the parameters in the preceding table from a property file or an environment
variable.

See also
• System Administration Guide
• Configuration Guide

Configure the free‐text batch load command for ClaimCenter

Procedure
1. Navigate to the following Guidewire Solr configuration directory:
opt/gwsolr/cc/solr/claimcontact_active/conf
2. Open the batchload shell script or batch file for editing and perform the following steps:
108 chapter 6: Configuring free‐text search
 Guidewire ClaimCenter 10.0.0 Installation Guide

If using a directory for the Guidewire Solr home directory other than /opt/gwsolr, modify the BASE_DIR
environment variable to locate the configuration files, for example:
Unix
BASE_DIR=/opt/gwsolr
Windows
set BASE_DIR=C:\opt\gwsolr
3. Open the batch load configuration file that you specified in Open the batchload shell script or batch file for
editing and perform the following steps: and perform the following steps:
a. Review the following elements for possible changes.
Unix

<param name="solrRoot" value="/opt/gwsolr"/>

<param name="absolutePathToSortExe" value="/bin/sort"/>

Windows

<param name="solrRoot" value="c:\opt\gwsolr"/>

<param name="absolutePathToSortExe" value="c:\cygwin\bin\[Link]"/>

b. Modify the attributes of the <dataSource> element to match the values for your database.
For example, if your database brand is Oracle:

<dataSource name="ds_orcl" driver="[Link]" url="jdbc:oracle:thin://@grinch:

11201:gwDiaAsc" user="su" password="gw"/>

IMPORTANT Due to security concerns, Guidewire recommends for production installations

that you configure Guidewire Solr Extension database credentials to come from a property
file or from environment variables. Do not hard code the database credentials in step 3b.
Also due to security concerns, Guidewire recommends that you not place a property file
with the database credentials in either c:\opt\gwsolr\pc\solr\claimcontact_active
\conf or c:\opt\gwsolr\pc\solr\claimcontact_active. Instead, place the property file
in a folder adjacent to c:\opt\gwsolr\pc\solr\claimcontact_active\conf.

4. Restart the Solr application to pick up the changes.

5. Run the batchload command to test the setup.
6. Examine the status response to verify your setup.
A problem-free load gives the same positive counts for Total Rows Fetched and Total Documents Processed.

Next steps
After completing this procedure, proceed to the Configuration Guide.

Configuring free‐text search 109

Guidewire ClaimCenter 10.0.0 Installation Guide

110 chapter 6: Configuring free‐text search

chapter 7

Command reference

ClaimCenter includes a number of command prompt tools that assist with build and administrative tasks on your
ClaimCenter server. Because of the simplicity and power of the commands, command prompt tools are the preferred
method of controlling server behavior, loading data, and generating tools in the ClaimCenter configuration
environment.

See also
• System Administration Guide

Build tool commands

Guidewire groups the ClaimCenter build and administration commands and options into a number of useful
categories.

Core application tasks

Command Action
gwb gwTasks Displays all Guidewire gwb command options.
gwb clean Deletes the build directories.
gwb cleanIdea Deletes the ClaimCenter Studio project files (files with .iml and .idea extensions).
gwb codegen Generates metadata classes, page configuration classes, permission classes, localization classes,
xml classes, and entity role constraints classes.
gwb compile Compiles and copies resources for the QuickStart application server. Run this command before
you start the QuickStart server. See the runServer command for more information.
gwb dropDB -Denv=env Prepares a new database for use by the Guidewire application. It will act upon the database
configured in [Link], or as optionally specified by the -Denv="env parameter.
Use caution whenever using this command. If the database has any objects before the command
is run, the objects are all dropped and not available for recovery except from a database backup.
You can pass additional parameters to this command by adding the parameters to the <reset-
tools-params> subelement in [Link] as shown in the following code example:

<database>
<dbcp-connection-pool>
<reset-tool-params system-username="user" system-password="pass"/>

Command reference 111

Guidewire ClaimCenter 10.0.0 Installation Guide

Command Action
</dbcp-connection-pool>
</database>

SQL Server
The command drops and creates a new database. It creates any filegroups named within the
<database> element. The database files will be physically located where the server would put
them by default. If specified, the collate attribute specifies the database collation. Otherwise,
the default collation of the database server will be used. The command SET
READ_COMMITTED_SNAPSHOT ON WITH ROLLBACK IMMEDIATE is issued on the new database.
Since a CREATE DATABASE command is used, attributes of the model system database of the
server are inherited.
The dropDB command will create any file groups listed in the upgrade element of the database
configuration. This does not happen on Oracle. However, the dropDB command will not drop a
database with file groups. If you have file groups configured, first drop the database using the
Management Studio. Then you can run dropDB to create the database with file groups.
Oracle
A Guidewire database corresponds to an Oracle schema: a user and all the objects owned by
that user. So, for Oracle, this command drops all objects owned by the schema owner, and only
the user is left with the required permissions. The dropDB command requires SQLPlus, available
with the Oracle client installation. Include ORACLE_HOME\bin in the PATH, so that dropDB can lo‐
cate SQLPlus.
The system-username and system-password attributes of the <reset-tools-params> element
must be specified so that the required permissions are available for these actions.
gwb idea Builds the ClaimCenter Studio project.
gwb inspect -- Runs Guidewire Studio inspections.
outputDiroutput
directory

gwb runServer Starts the bundled QuickStart application server. Depending on what you want to do, use the
following command options:
• To start the server in development mode using socket debugging, use the command gwb
runServer --debug-socket --no-suspend.
• To start the server in development mode in a suspended state using socket debugging, use
the command gwb runServer --debug-socket.
• To start the server in development mode using shared memory debugging, use the command
gwb runServer --debug-shmem.
• To start the server using a non‐default port, use the command gwb runServer -
[Link]=nnnn.
• To start the server in development mode in a suspended state using shared memory debug‐
ging, use the command gwb runServer --debug-shmem --no-suspend.
IMPORTANT There is a dependency between the gwb runServer command and the gwb
compile command. Guidewire recommends that you run the gwb compile command separately,
before you run the gwb runServer command, for example:
gwb compile
gwb runServer -x compile
Use the -x compile option with the runServer command to remove the dependency between
the compile and the runServer commands. Otherwise, ClaimCenter must first verify what re‐
sources, if any, need to be recompiled, then perform an incremental recompile of those resour‐
ces before starting the server.
gwb stopServer Stops the bundled QuickStart application server.
gwb studio Starts Guidewire Studio.

112 chapter 7: Command reference

 Guidewire ClaimCenter 10.0.0 Installation Guide

Configuration upgrade tasks

Command Action
gwb getRuleReport Builds the rule repository report.

Application server tasks

Command Action
gwb earWeblogicDbcp Builds the EAR file for WebLogic including JDBC drivers. Use gwb earWeblogicDbcp if you are going to
have ClaimCenter manage the database connection pool.
gwb earWeblogicJndi Builds the EAR file for WebLogic without JDBC drivers. Use gwb earWeblogicJndi only if you are going
to use a JNDI database connection managed by WebLogic.
gwb Builds the EAR file for WebSphere including JDBC drivers. Use gwb earWebsphereDbcp if you are going
earWebsphereDbcp to have ClaimCenter manage the database connection pool.
gwb Builds the EAR file for WebSphere without JDBC drivers. Use gwb earWebsphereJndi only if you are
earWebsphereJndi going to use a JNDI database connection managed by WebSphere.
gwb warJbossDbcp Builds the generic WAR file for JBoss including JDBC drivers. Use gwb warJbossDbcp if you are going to
have ClaimCenter manage the database connection pool.
You can include the Boolean parameter includeDictionary=true to also generate the ClaimCenter
Data Dictionary and Security Dictionary while building the WAR file. Use the following command:
gwb warJbossDbcp -DincludeDictionary=true
If includeDictionary=true, the command creates a dictionary folder within the WAR file. The
dictionary folder contains the following subfolders:
• data
• security
These folders contain the Data Dictionary and Security Dictionary respectively.
To view a dictionary, open [Link] in the data or security folder.
gwb warJbossJndi Builds the generic WAR file for JBoss without JDBC drivers. Use gwb warJbossJndi only if you are going
to use a JNDI database connection managed by JBoss.
You can include the Boolean parameter includeDictionary=true, which also generates the
ClaimCenter Data Dictionary and Security Dictionary while building the WAR file. Use the following
command:
gwb warJbossJndi -DincludeDictionary=true
If includeDictionary=true, the command creates a dictionary folder within the WAR file. The
dictionary folder contains the following subfolders:
• data
• security
These folders contain the Data Dictionary and Security Dictionary respectively.
To view a dictionary, open [Link] in the data or security folder.
gwb warTomcatDbcp Builds the generic WAR file for Tomcat including JDBC drivers. Use gwb warTomcatDbcp if you are going
to have ClaimCenter manage the database connection pool.
You can include the Boolean parameter includeDictionary=true to also generate the ClaimCenter
Data Dictionary and Security Dictionary while building the WAR file. Use the following command:
gwb warTomcatDbcp -DincludeDictionary=true
If includeDictionary=true, the command creates a dictionary folder within the WAR file. The
dictionary folder contains the following subfolders:
• data
• security
These folders contain the Data Dictionary and Security Dictionary respectively.
To view a dictionary, open [Link] in the data or security folder.
gwb warTomcatJndi Builds the generic WAR file for Tomcat without JDBC drivers. Use gwb warTomcatJndi only if you are
going to use a JNDI database connection managed by JBoss.

Command reference 113

Guidewire ClaimCenter 10.0.0 Installation Guide

Command Action
You can include the Boolean parameter includeDictionary=true to also generate the ClaimCenter
Data Dictionary and Security Dictionary while building the WAR file. Use the following command:
gwb warTomcatJndi -DincludeDictionary=true
If includeDictionary=true, the command creates a dictionary folder within the WAR file. The
dictionary folder contains the following subfolders:
• data
• security
These folders contain the Data Dictionary and Security Dictionary respectively.
To view a dictionary, open [Link] in the data or security folder.

See also
• “Using a JNDI data source” on page 67

Globalization tasks
Command Action
gwb diffDisplayKeys A display key difference tool that does the following:
• Compares each locale configured on the server against the
master display key list.
• Generates a file that contains a list of any missing keys.
gwb exportLocalizations - Exports a translation file from ClaimCenter into a file.
[Link]=translation_file - The -[Link] parameter specifies the destination file:
[Link]=export_language • If you leave the import translation file in the same location, then
enter only the name of the file to import.
• If you move the translation file to a different location, then
enter an absolute path or a relative path to the file from the
root of the installation directory.
The -[Link] parameter specifies the destination lan‐
guage to export. The -[Link] parameter must match a
ClaimCenter LanguageType typecode, such as fr or ja.
gwb importLocalizations - Imports a translation file into the configuration.
[Link]="translation_file The -[Link] parameter specifies the file that contains the
-[Link]=destination_language translations. It must be in the same format as an export file from
Studio.
The -[Link] parameter specifies the destination lan‐
guage for the translations. The language must match a ClaimCenter
LanguageType typecode, such as fr or ja.

gwb installLocalizedPack - Installs or upgrades a language module in directory

DlocalizedPackPath=pathToLanguagePackZipFile pathToLanguagePackZipFile.

gwb genPhoneMetadata Regenerates phone metadata in directory config/phone/data. Run

this command if you have modified the phone metadata XML files

See also
• Globalization Guide

114 chapter 7: Command reference

 Guidewire ClaimCenter 10.0.0 Installation Guide

Integration tasks
Command Action
gwb genFromWsc Builds WSC meta‐information. Run this command whenever there are new .wsc files containing web
service URLs available to generate the web service stub code. Places all WSC files in the configuration
module.
gwb genWsiLocal Generate the WSDL for WSI web services in gsrc/wsi/local.
gwb exportWsdl Exports WSI web service WSDL files and related resources to a single JAR file. The generated JAR file is
located in the directory modules\configuration\build.
The individual WSDL files are generated in subdirectories of modules\configuration\build\wsdl
\wsi\wsdl. For a client program to access the published services, the Java wsimport tool can parse
the WSDL files and generate the necessary JAX‐WS files. The operation can be automated by a Maven
POM file.

Change verification tools

Command Action
gwb verifyExtConfig Performs a verification of external property substitution to find errors. See the
System Administration Guide for more information.
gwb verifyResources [- Verifies Gosu types, GX models, PCF files, WS‐I web service annotations, XML sche‐
[Link]=<types>] mas, and XML workflow files.
You can use the -[Link]=<types> parameter to verify only some of the
resource types. The resource type options are:
annotation,gxmodel,pcf,workflow. The types are not case sensitive. If you
specify multiple types, use commas. If you include spaces in your list of types,
surround the typelist with double‐quotes.
Examples:
• gwb verifyResources -[Link]="annotation, pcf"
• gwb verifyResources -[Link]=pcf
gwb zipChangedConfig - Creates a ZIP file containing all files that are changed from the base configuration.
[Link] [- Specify the output filename with the -DoutputFile parameter.
DappRootDirectory You can also specify an application root directory by setting the -
application_home ][-Dexclude DappRootDirectory parameter. If you do not set -DappRootDirectory, the tool
"directory1;directory2"] uses the ClaimCenter installation directory as the root. The tool saves the output
file relative to the application root. This file must not already exist.
Specify any directories to exclude by setting the -Dexclude parameter, which takes
a quoted, semicolon delimited, list of directories to exclude. Note that you can only
exclude directories, and cannot exclude files.

Documentation generation and other tools

Command Action
gwb genDataDictionary - Generates the Data Dictionary and Security Dictionary:
DoutputFormat={html|xml} • The Data Dictionary includes physical fields in the database and virtual fields
in the data model.
• The Security Dictionary includes application permission keys, system permis‐
sions, and roles.
Guidewire generate the dictionaries the first time you unzip ClaimCenter. Re‐
generate the dictionaries each time you update the data model.
Run the gwb genJavaApi command before regenerating the security and data
dictionaries.

Command reference 115

Guidewire ClaimCenter 10.0.0 Installation Guide

Command Action
The outputFormat parameter is optional. If you omit this parameter, the de‐
fault output format is HTML.
You can also generate the dictionaries in HTML format while building a WAR
file. See the descriptions for WAR tools in this command list for instructions.
This command has the following useful options:
• Set -DoutputFormat to html to generate HTML:
ClaimCenter/dictionary/data/[Link]
ClaimCenter/dictionary/security/[Link]
• Set -DoutputFormat to xml to generate XML:
ClaimCenter/build/dictionary/data/[Link]
ClaimCenter/build/dictionary/data/[Link]
ClaimCenter/build/dictionary/security/[Link]
ClaimCenter/build/dictionary/security/[Link]

gwb genDataMapping -Dsplit={true| Builds the data mapping files. Data mapping files represent fields present in the
false} physical database. None of the virtual fields are represented.
Set -Dsplit=true to build the files split out by table and typelist.
Set -Dsplit=false to build the data mapping files with all tables and typelists
concatenated.
gwb genEntityModelXml Generates the Data Dictionary in XML format with an associated DTD so the
XML document can be translated.
gwb getImportAdminDataXsd Regenerates the XSD files for importing administrative data.
gwb genPcfMapping Builds the PCF mappings.
gwb genRuleReport Generates an XML report describing the existing Gosu rules.
gwb gosudoc Generates Gosu API reference of the APIs available from Gosu within Studio.
This command produces documentation at directory ClaimCenter/build/
gosudoc/[Link].

gwb packageSolr Regenerates the Solr installation Zip file, [Link] for deployment of the
Guidewire Solr Extension.
gwb version Prints the product version.

See also
• Configuration Guide
• Rules Guide
• Gosu Reference Guide

Merge command tools

Command Action
gwb mergeModule -[Link] Merges a custom module on to the configuration module. The command
module_directory overwrites existing files in the configuration module with files from the new
module. The command merges display property files.

Plugin development tasks

Command Action
gwb genJavaApi Builds the Java API libraries to the ClaimCenter/java-api directory.

116 chapter 7: Command reference

 Guidewire ClaimCenter 10.0.0 Installation Guide

Command Action
gwb pluginStudio Starts IntelliJ IDEA with OSGi Editor. This is a specially‐configured instance of IntelliJ IDEA and included
with Guidewire ClaimCenter. You can use this IDE for Java plugin development.

See also
• Integration Guide

User interface tasks

Command Action
gwb webResources Generates expanded, CSS files that you can debug from the Sass files that define style rules for
ClaimCenter.
gwb updateTheme Applies style and image changes to ClaimCenter.

See also
• Configuration Guide

Command reference 117

Guidewire ClaimCenter 10.0.0 Installation Guide

118 chapter 7: Command reference