Introduction to Insbridge Extended Services Interface

Oracle Insurance Insbridge Enterprise Rating Extended Services Interface (ESI) is a library module designed to provide remote services to the Insbridge Enterprise Rating (Insbridge) business services and Insbridge Soft Service (IBSS) without directly utilizing the system User Interfaces (UI).

ESI for Insbridge

ESI allows users to pass information between a user’s source policy or business admin system and the RateManager system or the Insbridge Framework Administrator (IBFA) without using either the RateManager or IBFA UI. ESI itself is not a web service. You reference it in your applications and consume it natively. ESI then calls the web services in RateManager or IBFA. Both RateManager and IBFA have a web service interface that ESI can call.

ESI is designed to operate on Insbridge version 04.01.00 or higher and connects with:

• Oracle Insurance RateManager Interface
• Oracle Insurance Framework Administrator Interface

For example, if you had a vendor Policy Administration system and wanted to provide integrated product management through your custom solution; ESI would allow you to model and use the workflow on the Insbridge business services and functions but control all the user presentation aspects through your custom product interface.

Rule and Functionality Highlights

• ESI is available on Insbridge Enterprise Rating version 04.01.00 or higher.
• ESI is shipped with the IBFA installation. To locate ESI, look under the Insbridge directory for the SDK/ESI/Java file; [INSTALL_DIR]\Insbridge\SDK\ESI\Java. This file contains five items:

• InsbridgeEsiServices.jar
• EsiSwingTester.cmd
• EsiSwingTester.jar
• EsiSwingTester Source Code.zip

• ESI entries are immediate. There is no lag time or system sync required.
• An ESI cannot be recalled or undone. If an ESI needs to be edited, for example a folder has an incorrect name; you must enter RateManager or IBFA and make the changes there.
• ESI works with the default subline in the folder of your choice for any line of business.
• Unless specifically stated as Optional, all Inputs are Required.

 

ESI Work Flow for IBSS

 

Note: For further details, please see the Javadoc file.

Rate Model ESI: IBSS

 

Functionality Highlights

• A rate request now can be an Object (Rate) with rate request details or an Insbridge XML.
• With the ESI API, you can submit an InputBatch as a collection of rate objects or Insbridge XML, to the runtime database of IBSS.
• Using the InputBatch, input rates can be retrieved either as an XML or as a rate object.
• Using the Result Batch, the result of a rate can be retrieved either as an XML or as a result object.
• When an InputBatch is submitted for execution, a Job is returned that can be used to get the status of the Job, or stop the Job even if it is being executed.
• The status can be retrieved either as an XML or as a status object.