2 a bank application needs to access information from the customer database and integrate it with...
Post on 30-Mar-2015
213 Views
Preview:
TRANSCRIPT
Conclusion& use cases
13 décembre 2007Eric SAMSON, CTO - XCALIAStève SFARTZ, MICROSOFT France
Use Case: Loan Application
2
A bank application needs to access information from the customer database and integrate it with loan credit history information stored in a legacy database (accessed through CICS transactions).
Scenario 1: database and data service integration
CICS
Use Case: Loan Application
3
IT created a new Web service from the customer database that provides just the information required for loan applications. This does not interrupt direct access to the database while the service is being tested and proven. All these moves are managed with no change in the client application.
Scenario 2: migrating some direct database access to data services
Use Case: Loan Application
4
Meanwhile, the loan department is implementing a new commercial CRM System to serve the complex needs of the bank. The loan application will integrate this new service with legacy loan data. Once again, all these moves can be managed with no change in the client application.
Scenario 3: integrating packaged applications
Atos Telco POC: Customer Issue
5
Atos POC: Xcalia Implementation
6
XIC DAS Use Case
7
Composite application accessing various data sources in a disconnected fashion through an intermediate XIC DAS (WS)
XIC Aggregating Data Use Case
8
Business-Level Domain Object Model
BankingService
AccountingService
SAP R/3,Oracle Apps,
etc.
Wells FargoPayment Service
Person Employment Payment Compensation Account1
1
1
* *
**
1
Composite application accessing a database and two services
HRdatabase
XIC Portability Use Case
9
BusinessApplication
Xcalia IC• Transactions• Queries• Cache• Metadata• Transformations• Business semantic
MySQL
CICSdo { … x.getCustomer();
…}
SQL…
ScreenScrapping
Customer ?
DB2
The same application can transparently access mainframe screens and RDBMS
XIC Use Case: Mondiale Assistance
10
InsuranceApplication
Xcalia IC• Transactions• Queries• Cache• Metadata• Transformations• Business semantic
Oracle
Siebeldo { … x.getCustomer();
…}
SQL…
Connector
Customer ?
Java insurance applications can now transparently access Siebel instead of the former in house CRM database.
Summary of Xcalia DAS benefits
Scalability based on multiple levels caching, dual query engine, SQL statement optimizations, eager fetching, cost-based selection strategiesDynamic monitoring and tuning: ability to analyze and optimize data loading and manipulation at runtimeSupport for all data sources within the Enterprise: RDBMS, XML, Web Services, legacy mainframe transactions (CICS, IMS…), packaged applications (SAP, Siebel…), components (EJB…), ODBMS (Versant)
Ability to map any proprietary data sources through the Universal Java MapperPatented technology for dynamic composition of data services based on metadata
Agility based on the manipulation of a logical business-oriented SDO model
Applications are fully isolated from physical data models
Flexibility based on highly configurable mapping between the logical business model and all the supported data sourcesMultiple open APIs: external caching, custom mappers, data access cost policies, security frameworks, etc.11
Conclusion
XIC is a Transactional Data Services solution for interop within Composite Applications
Data sources interop: RDBMS, ODBMS, XML, Web Services, mainframes, packaged applicationsArchitecture interop: client-server, rich client, web pages, 3-tiers, 4-tiers, SOAPlatform interop: Java, .NetProgramming Language interop: object-oriented (Java, C#, VB) or business oriented (BPEL, workflow)
Designed for scalabilityDynamic tuning at runtimeSupport for complex mappings
Designed for ease of useThe main interface for developers is the Business ModelToolsCompliance with standards
12
© 2007 Microsoft France
Votre potentiel, notre passion TM
top related