PolicyCenter configuration files

Warning: Do not attempt to modify any files other than those in the PolicyCenter/modules/configuration directory. Any attempt to modify files outside of this directory can cause damage to the PolicyCenter application and prevent it from starting thereafter.

Installing Guidewire PolicyCenter creates the following directory structure:

Directory	Description
.gradle	Configuration and settings for Gradle, the project build tool.
.idea	Configuration and settings for IntelliJ IDEA, the foundation for Guidewire Studio.
admin	Administrative tools. See Command prompt tools for descriptions.
bin	Deprecated. The gwpc batch file and shell script used to launch commands for building and deploying. These commands are deprecated, and are provided only for backwards compatibility with previous releases. For the updated commands, see Command reference.
build	The output of build commands such as exploded .war files and the data and security dictionaries. This directory is not present when you first install PolicyCenter. The directory is created when you run one of the build commands.
dist	Guidewire application .war, and .jar files are built in this directory. The directory is created when you run one of the build commands to generate .war files.
doc	HTML and PDFs of PolicyCenter documentation.
gradle	Support files for Gradle, the project build tool.
java-api	The Java API libraries created by running the gwb genJavaApi command. See Regenerating integration libraries and WSDL.
javadoc	Reference documentation for the Java API libraries.
licenses	License information for third-party tools used by PolicyCenter.
logs	Application log files.
modules	Subdirectories including configuration resources for each application component.
productdesigner	Application files for Product Designer.
repository	Necessary PolicyCenter files.
solr	Installation and support files for the Solr free text search platform. See Free-text search configuration.
studio	Application files for Guidewire Studio.
ThemeApp	Files defining the user interface styling for PolicyCenter.
webapps	Necessary files for use by the application server.

Edited resource files reside in the configuration module only

The configuration module is the only place for configured resources. As PolicyCenter starts, a checksum process verifies that no files have been changed in any directory except for those in the configuration directory. If this process detects an invalid checksum, PolicyCenter does not start. In this case, overwrite any changes to all modules except for the configuration directory and try again.

Guidewire recommends that you use Studio to edit configuration files to minimize the risk of accidentally editing a file outside the configuration module.

Key directories

The installation process creates a configuration environment for PolicyCenter. In this environment, you can find all of the files needed to configure PolicyCenter in two directories:

The main directory of the configuration environment. In the default PolicyCenter installation, the location of this directory is PolicyCenter/modules/configuration.
PolicyCenter/modules/configuration/config contains the application server configuration files.

The installation process also installs a set of system administration tools in PolicyCenter/admin/bin.

PolicyCenter runs within a J2EE server container. To deploy PolicyCenter, you build an application file suitable for your server and place the file in the server’s deployment directory. The type of application file and the deployment directory location is specific to the application server type. For example, for PolicyCenter (deployed as the pc.war application) running on a Tomcat J2EE server on Windows, the deployment directory might be C:\Tomcat\webapps\pc.