Preparing for integration development

During integration development, you edit configuration files in the hierarchy of files in the product installation directory. In most cases, you modify data only through the Guidewire Studio interface, which handles any SCM (Source Control Management) requests. The Studio interface also copies read-only files to the configuration module in the file hierarchy for your files and makes files writable as appropriate.

However, in some cases you need to add files directly to directories in the configuration module hierarchy, such as Java class files for Java plugin support. The configuration module hierarchy for your files is in the hierarchy:

PolicyCenter/modules/configuration

Some of the main configuration subdirectories are described in the following table.

Directory under the configuration module

Files that the directory contains

config/web

Your web application configuration files, also known as PCF files.

config/logging

The logging configuration file log4j2.xml.

config/templates

Two types of templates relevant for integration.

Plugin templates
Use Gosu plugin templates for a small number of plugin interfaces that require them. These plugin templates extract important properties from entity instances and generate text that describes the results. Whenever PolicyCenter needs to call the plugin, PolicyCenter passes the template results to the plugin as String parameters.
Messaging templates
Use optional Gosu messaging templates for your messaging code. Use messaging templates to define notification letters or other similar messages contain large amounts of text but a small amount of Gosu code.

The base configuration provides versions of some of these templates.

plugins

Your Java plugin files.

Register your plugin implementations in the Plugins registry in Studio. When you register the plugin in the Plugins registry, you can specify a plugin directory, which is the name of a subdirectory of the plugins directory. If you do not specify a subdirectory, PolicyCenter uses the shared subdirectory as the plugin directory.

For a messaging plugin, you must register this information in two different registries:

  • The plugin registry in the plugin editor in Studio
  • The messaging registry in the Messaging editor in Studio.

Some additional important integration-related directories are described in the following table.

Directory under the PolicyCenter installation directory

Files that the directory contains

PolicyCenter installation directory

Command-prompt tools such as gwb.bat. Use for the following integration tasks:

  • Regenerating the Java API libraries and local WSI web service WSDL.
  • Regenerating the Data Dictionary.

modules/configuration/gsrc/wsi/local/gw/webservice/

modules/configuration/gsrc/wsi/local/gw/wsi/

WSDL files generated locally.

admin

Command-prompt tools that control a running PolicyCenter server. Almost all of these tools are small Gosu scripts that call public web service APIs.