The main components of INSIS Integration Architecture are (see the picture bellow):
The BPEL processes covering the insurance business. This is a BPEL process, which encapsulates the logic of the appropriate insurance business logic and workflow. BPEL process needs access to certain functionality from the participating Service Providers. All those activities should be provided as standard interface functions, which are providing the data in a common format.
Collection of proxy BPELprocesses that provides common functionality.
INSIS Integration Manager. This is a tool for managing integration in asynchronous mode. It can be configured to poll the counterpart systems for specific events, extract the necessary data, when it is available
and feed it to the main business process. It manages the task queues and performs the polling activities, required for completion of each task. It is highly configurable and can be set up to perform any kind of
interactions between the Service Providers
The integration architecture defines a common approach and methodology for integrating INSIS modules and subsystems into SOA environment. The cornerstone of the architecture is INSIS Integration Bus (see the figure bellow). It provides the tools for transparent management of asynchronous communication with third-party systems. The core technology used in INSIS Integration Bus is BPEL. The business functionality is implemented in a set of main business processes, such as registering a policy, claim, customers, managing claim workflow, etc.