Service Offerings | Clients | Consultants | Careers | Learning Environment | Case Studies | Testimonials
What Makes Omnikron Special?
“At Omnikron, we feel we are a very special group of people who take exceptional care of all the people we work with – our Customers, Consultants and Employees. It’s easy for us to make this claim, but what makes this declaration true? It can only be validated if the people who work with us have the same lofty opinion of us as we have of ourselves! So, here are a few testimonials and stories of excellence from people whom we have touched – from the past to the present.”
Case Studies
Case Study 4: Tier 1 Online Broker
Our client is an online insurance company (they also have a call center, besides online business). They use a variety (EXE/COM etc) of applications to generate a set of insurance quotes from various vendors.
The purpose of their new online system was to integrate different in house applications (Proprietary Quote Engines) as well as external applications (3rd party COM objects that take input from the company and return quotes), apply business rules, synchronize data and provide results to online users. (They get insurance rates from different "Insurance Quote Engines".Some of these engines are local EXE's, some of them are remote COM objects).
BroadVision was used for web front end and E*Gate for Middle Tier/EAI tier.
Here is a MINIMAL architecture of the system. Everything except UI, DB and Quote Engines are part of e*Gate suite. (We had one such architecture for EACH of their lines of business, such as Home, Auto, Life etc). MUXes are used as interfaces between BV and e*Gate.
E*Ways (COM/DART) interact with external applications (Quote Engines) BOBs (Business Object Brokers) make up mostly the main business rules layer. They massage data based on certain business rules.
Correlators are used as data synchronizers. Different Quote Engines may have different response times, and this is the place where the returning data is synced before giving it back to UI for display.
IQs (Intelligent Queues) are used (internally) for persistent (guaranteed) data delivery. If for any reason, a message can’t be passed on to the next component (say because of communication glitches), it stays in the IQ until it is sent through.
Besides, this, we implemented Error Logging system for messages using e*Gate.