Chapter - 2 : Overview
This chapter includes following topics:
- Basic information about OIDG portal applications
- Their functions
- Terminologies
OIDG portal gives you access to following applications based on your role in organization:
- For Administrators
- AdminView
- Oracle Identity Management
- WebLogic Console
- FMW Control
- Service Bus Console
- Managed File Transfer Console
- Scheduler
- For Non-Administrators
- QuickView
WebLogic Console
WebLogic Server Administration Console is a Web browser-based, graphical user interface that you use to manage a WebLogic Server domain.
Service Bus Console
Oracle Service Bus Console is a web-based console where you can create and configure most Service Bus resources, test the resources, and activate your changes to the runtime. You can also import and export Service Bus configuration JAR files.
Oracle Identity Management
Oracle Identity Management enables organizations to effectively manage the end-to-end lifecycle of user identities across all enterprise resources, both within and beyond the firewall and into the cloud.
FMW Control
Oracle Fusion Middleware is a comprehensive family of products ranging from application development tools and integration solutions to identity management, collaboration, and business intelligence reporting.
MFT Console
Oracle Managed File Transfer (MFT) is a high performance, standards-based, end-to-end managed file gateway. It features design, deployment, and monitoring of file transfers using a lightweight web-based design-time console that includes file encryption, scheduling, and embedded FTP and sFTP servers.
Scheduler
Oracle Scheduler enables you to control when and where various computing tasks take place in the enterprise environment.
AdminView
AdminView is a web-based application that is part of the Oracle Insurance Data Gateway (OIDG) product. It allows users to configure parties, party services, endpoints, environments, and party contract mapping using the AdminView application.
How AdminView Functions within OIDG
AdminView provides configuration control for transaction activities between parties. It allows you to define which services will be used between parties and the endpoint configuration details needed to communicate between them.
QuickView
QuickView is a front-end web-application used by insurance companies to view real-time and batch transactions that are sent to and routed through Oracle Insurance Data Gateway (OIDG) to 3rd party destinations. It is used by authorized OIDG users to view the status and routing of policies processed through the system.
How QuickView Functions within OIDG
OIDG validates and routes policy transaction data provided by sender parties to various target destinations depending on the transaction type. QuickView displays these transactions showing the sending and receiving parties as well as the transaction type and status. Transactions can fail to pass validation rules or to reach their target recipient services for various reasons. QuickView provides a means to monitor transaction health.
The validation process includes these stages:
- ACORD® AML Compliance Validation – In this stage, the input request XML is validated to check whether it is ACORD complaint.
- Business Rule Validation – In this stage, the request data is checked against the business rules as defined in the OIDG rule engine.
If either of these stages fail, the transaction would be terminated, marked as failed, and appropriate error messages would be logged. A QuickView user would be able to view the transaction list, find the failed transaction, its captured error messages, and respond as needed to that particular failure.
The transactions listed in QuickView can be searched, sorted, and filtered by applying criteria such as policy number, transaction IDs, message time, sender party, etc.
After passing validation, a transaction will continue to be routed to the destination system. If OIDG experiences a failure communicating with the destination system, the failing transaction can be resubmitted from QuickView.
Terminologies
This section describes the terminologies used within the OIDG portal applications.
Data Integration Mechanisms
Web Service
Allows parties to communicate their services with web-service supported applications.
File Transfer
Allows parties to integrate their services with supported file transfer based integration services. It supports PGP encrypted files and compressed zip files. File transfers are triggered from jobs defined in the Enterprise Scheduler Service (ESS).
Following types of file transfer mechanisms are supported:
- FTP – to read and move files from an FTP server
- FileMove – to read and move files from a remote or local server folder location
- LocalFile – to read files from a local OIDG application folder
Batch
A batch is an XML file that generally has one or more policy transactions included. Each XML file is considered to represent one “batch” of transactions. These files are identified with a unique ID called a batch ID. Batches are monitored on the Batch Transactions tab.
Batch Group
A batch group is a collection of one or more batch XML files. It can be a single zip file or a collection of all the XML request files present in the request folder when a batch job starts. This “collection” of batch files is identified with a unique ID called a batch group ID. Batch groups are monitored on the Batch Group tab.
Transaction Direction
Transactions are directional and the QuickView application presents transactions based on their direction as it pertains to OIDG. Transactions are either inbound to OIDG or outbound from OIDG.
Inbound Transactions
These are inbound requests that OIDG has received. They can be web service requests or batch requests.
Outbound Transactions
These are outbound requests that are sent from OIDG to external destination systems. A single inbound transaction may result in multiple outbound transactions.
Transaction Message Types
These are the supported transaction types:
Policy Synchronization
A Policy Synchronization message contains policy and client data. It allows full policy details to be communicated between a sender and a receiver. This can be used to send new business data or policy changes between parties. Policy Synchronization can be used to send policy data one policy at a time via the OIDG web-service interface or in large batches via the OIDG file transfer interface.
Policy Reconciliation
A Policy Reconciliation message implies that the policy exists in the sender system and is possibly known by or new to the receiving system, which needs to be brought up to date. It is basically intended to get the receiving system in sync with the sending system. This message type is used to sync large batches of policies.
Policy Migration
A Policy Migration message implies that the policy exists in the sender system but is not known to the receiving system. This message is used to send large batches of policies from one system to another to initialize the receiving system with this policy information.
Commission
A Commission message contains a commission statement which reports commission details for multiple policies.
Premium
A Premium message contains premium payment data for a policy.
Transaction Errors
Errors incurred during transaction processing are categorized as follows:
- XMLSchemaError - The input XML is not well formed or not ACORD complaint.
- BusinessRuleValidationError - Failed to meet business rule requirements.
- CommunicationError -The destination web service is down or communication to it is not possible.
- BusinessServiceError - The destination web service returned an error.
- ApplicationError - Internal failure within the OIDG application.