An Agile Service-Oriented Architecture

Exigen IPB's technical architecture is service-oriented (SOA). Each IPB-based solution is created by assembling a number of service components from IPB’s own insurance business services and common services library, as well as leveraging the functionality of existing legacy or third party systems. IPB is entirely based on JAVA Enterprise Edition (JEE) specifications and its associated frameworks, deployed as a fault-tolerant, distributed, multi-tier Java implementation running on an application server. By using common technology and standards, IPB removes the risks associated with proprietary technology lock-in and skills shortage.

The IPB’s ACORD standards-based Business Object Model (BOM) provides the ability to integrate functionality and information from all sources — legacy systems, third party systems, and the IPB itself. IPB BOM design abstracts its object management layer from the logic, process, and interaction layers using a technique called “virtual object model.” This virtualization technique enables the IPB business objects to render services by seamlessly accessing and persisting data leveraging one or more external systems as well as IPB’s own persistence layer. As a result, IPB solutions benefit from the full complement of services provided by the BOM without having to deal with the complexities associated with systems integration.

This capability opens systems integration options that would otherwise require substantial customization. Also, the isolation of this layer facilitates transition and/or consolidation of underlying systems to a service-oriented component architecture. For example, multiple current rating or billing systems can be transitioned to a single rating or billing engine without significant perceptible change — aside from any improvements — to the business users.