New and changed in integration in 10.0.0

Guidewire InsurancePlatform Integration Views

Integration Views allows you to define a stable, versioned contract for publishing data to and retrieving data from the PolicyCenter database. In addition, the feature provides a simple, declarative way to map underlying PolicyCenter data into a serialized format that conforms to the contract.

The technical realization of this contract starts with two mandatory components and an optional component. The mandatory components include a mapping and a schema. The optional component is a filter. The mapping is a set of declarations that transform an object of a particular type first into an intermediate object that conforms to a specified schema. In the Integration Views context, the ultimate serialized form of this intermediate object is a JSON object or XML element. The schema defines the structure of the data involved in the custom processes. The schema also enables you to use off-the-shelf tools to generate objects and methods to work with the data once it is serialized. The optional filter specifies the parts of the schema to use as output or for presentation. The end result of an Integration View is a JSON object or XML element.

Marshal and unmarshal Gosu objects to and from XML

The marshal and unmarshal methods of the WsiExportableUtil class can convert additional types of Gosu objects to and from XML.

The methods could always process Gosu DTOs (data transfer objects). The following additional types can also be processed.

Simple types, such as int, Integer, Double, String, boolean, and Boolean
GWRemotable types
GX models
XSD types
Lists of marshallable types

Support for testing JMS inbound integration in non-production mode

PolicyCenter now supports running inbound integration in dev mode on the Jetty server that the base configuration of Guidewire Studio provides. You can use this environment to test your implementation of inbound integration while you develop your code. Use one of the unmanaged thread pool types, not a J2EE managed thread pool.

You cannot use the Jetty server in production mode. You must use one of the supported application servers: JBoss, WebLogic, or WebSphere.

Additional directory in plugins/Gosu for internal use only

The PolicyCenter/modules/configuration/plugins/Gosu directory now has a subdirectory called gresources. This new subdirectory is for internal use as a compilation output path. Never use, modify, or rely upon the contents of this directory.

Changes to servlet definitions in servlets.xml

The configuration/config/servlet/servlets.xml file now supports env and server attributes and static parameters that PolicyCenter uses to configure a servlet at start up.

The env attribute is an optional comma-separated list of names of environments for which the servlet definition applies. The server attribute optionally specifies the server for which the servlet definition applies. The value of this attribute is either a server role preceded by the # character or a server ID.

The servlets.xml file in the base configuration contains an example of the use of <param> subelements in the definition of the InfoServlet servlet.

Changes to inbound integration configuration file

The XML definition structure for inbound integrations has changed:

XML configuration item	Previous releases	Changes
Thread pool definition	Generic `<threadpool>` element	Specific element: `<j2ee-managed-threadpool>` for JMS integration `<unmanaged-threadpool-cached>` to reuse an available thread that is not in use and to create a new thread if one is not available `<unmanaged-threadpool-fixed>` to specify a fixed number of threads `<unmanaged-threadpool-forkjoin>` to use the number of CPUs that the JVM detects as the number of threads `<unmanaged-threadpool-single>` to specify a single thread
Thread pool type	`<gwthreadpooltype>` subelement of `<threadpool>` element	No longer available because the new specific thread pool element types do not require this property
Thread pool environment	Single value for environment	Optional. `env` attribute accepts comma-separated list of values.
Inbound integration environment	Single value for environment	Optional. `env` attribute accepts comma-separated list of values.
For intentional logging, traceability ID creation point for all integration types	Not available	Required. `traceabilityidcreationpoint` subelement, a value specified by the constants in gw.logging.TraceabilityIDCreationPoint.
JNDI properties for JMS integration	Not available	Required. `<jndi-properties>` subelement.
Plugin handler for custom inbound integration	Required	Not supported.

JMS inbound integration support for JBoss

PolicyCenter now supports running JMS inbound integration on a JBoss application server. Use the <j2ee-managed-threadpool> element to define the thread pool for this integration.

Changes to billing system integration

Several changes were made to billing system integration.

New typelists

InvoicingMethod – Whether to use default billing, custom billing, or override the invoice stream
BillingLevel – How to bill policies on the account
BillDateOrDueDateBilling – Corresponds to typelist in BillingCenter

Changes to StandAloneBillingSystemPlugin

Modified and added more payment plans to the StandAloneBillingSystemPlugin plugin:

Twice Per Month Demo – Statement dates are now reliably twice per month. By using Invoicing Overrides, you can set the statement dates. Previously, the statement dates were determined by dividing the range in days by the number of payments, and sometimes missed the expected payment dates.
Quarterly Demo – New. Send statements quarterly.
Monthly Demo – New. Send statements monthly.
Every Other Week Demo – New. Send statements every other week.