Using integration-specific containers for integration

The base configuration implementation of the billing system integration passes information from PolicyCenter to BillingCenter, and from BillingCenter to PolicyCenter. These applications use web services defined as Gosu code to pass information to each other. The objects passed between applications are not direct references to persisted Guidewire entities. Each application defines core APIs to pass containers that encapsulate important information.

If you modify the integration, Guidewire strongly recommends that you maintain this pattern.

For example, if you customize or write additional web services, do not expose entities directly to the API as parameters or return objects from the web service APIs. Instead, create a Gosu class to encapsulate your integration data.

This approach makes the WSDL smaller because it does not expose the whole entities tree. It also minimize the chance that the API breaks every time you make a domain model change during development.