Xcalia -: Safely integrate your high-volume transactional applications to SOA. ° ~ °° ~ °°° ~ °° ~ ° ~ °° ~ °°° ~ °° ~ ° ~ °° ~ °°° ~ °° ~ ° ~ °° ~ °°° ~ °° ~ ° ~ °° ~ °°° ~ °° ~ ° ~ °° ~ °°° ~ °° ~ ° ~ °° ~ °°° ~ °° ~ ° ~ °° ~ °°° ~ °° ~ ° ~ °° ~ °°° ~ °° ~ ° ~ °° ~ °°° ~ °° ~ ° ~ °° ~ °°° ~ °° ~ ° ~ °° ~ °°° ~ °° ~

Customer Scenario

Xcalia customers are large enterprise customers in high-volume transactional environments with a lot of mainframe and legacy systems. These tend to be financial institutions (insurance, banking and brokerage firms), retail businesses, and telecommunications. Here is a typical scenario for how the Xcalia Intermediation platform solves data and service integration issues within an SOA environment in an Insurance company.

A typical use case would be the one of a bank wanting to develop a new loan application, using information coming from a legacy loan database on a mainframe and from an in-house CRM application built upon a relational database. Using Xcalia, it is possible to directly access the relational model from the business layer (object-relational mapping).

With Xcalia, the IT department in the Insurance company can reuse of the business logic already defined in a CICS service deployed in front of the loan database with the same ease of use). This is a composite application, using a pure business model. The diagram illustrates the transparent manipulation of the logical loan model and the automatic composite mapping to the CRM database and the reuse of the legacy business logic from a CICS transaction on a mainframe. The development of a new application can easily be externalized, as it just requires basic Java programming skills. Some experts mastering the complex enterprise data topology and IT architecture will just have to define the right metadata within Xcalia Intermediation.

Loan Application Use Case: Step 1

The second step would be to progressively migrate to SOA in order to prepare a further move to a packaged CRM application. A piece of the CRM application will be accessed through a new service layer and will co-exist with the older part still directly accessing the database.

Loan Application Use Case: Step 2

To automate this process, the loan officer has asked IT to create a new web service from the customer database that provides just the information required for loan applications. This can not interrupt direct access to the data while the service is being tested and proven. All these moves are managed with no change in the client application. With Xcalia, this can be done without any change in the client application, the new service relies on Xcalia Intermediation for its own database access needs.

Loan Application Use Case: Step 3

Meanwhile, the loan department is implementing a new commercial CRM System to serve the complex needs of the bank. But, the loan officer still wants to integrate a service with a subset of functionality from the CRM application with legacy loan data for his application. Once again, all these moves are managed with no change in the client application.

Xcalia is a major SOA vendor addressing enterprise IT and business requirements regarding business oriented enterprise data access, data access, business model driven data access, enterprise data integration architecture, enterprise information access, comparison of SOA and EIA, EII, enterprise SOA, mitigate the cost of SOA migration, transaction management within SOA architectures, data access layer for the agile enterprise, metadata driven SOA business oriented architecture for composite application design and deployment, data integration infrastructure, data integration findings, enterprise integration patterns, enterprise SOA adoption strategies, SOA in practice, object to service mapping within service oriented architectures, data access in an SOA perspective.