Advertisement

Exploring Integration Tier Design Patterns

Abstract

The integration tier is a boundary tier and interacts with different external systems for data exchange. The integration tier in the eInsure application accessed the relational database for storing, retrieving, and manipulating data related to policies, claims, accounting, customers, and products. eInsure used entity beans for typical create, read, update, and delete (CRUD) operations with the database. The legacy version of eInsure had lots of leftovers in the formof stored procedures. The eInsure application made heavy use of these stored procedures for database-intensive tasks, especially for the batch jobs that ran daily after regular business hours or in certain intervals such as monthly or quarterly.

Keywords

Bind Variable Public Class Deployment Descriptor Spring Framework Page Controller 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Copyright information

© Dhrubojyoti Kayal 2008

Personalised recommendations