Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Integrated Banking System A Use Case for System Integration, Business Rules and Analytics

4,707 views

Published on

-

Published in: Technology

Integrated Banking System A Use Case for System Integration, Business Rules and Analytics

  1. 1. Ramith Jayasinghe Technical Lead
  2. 2. Agenda ● Banking Use-case and extensions ● Solution Architecture ● Product usage patterns.
  3. 3. Usecase: Banking sample ● Demonstrates account opening process in a retail bank . ○ Available online at https://docs.wso2. com/display/DVS370/Retail+Banking+Sample ○ Integrates several existing/legacy systems to orchestrate new business capability. ○ Long running process
  4. 4. Usecase: Banking sample ● Account opening procedure: ○ Check weather customer exists ( in customer database) ○ if customer doesn’t exist, create a record in database ○ Create the account ( Accounts are maintained in mainframe system) ○ Link the debit card to account. ○ Issue debit card ( - done by a separate system. Accessed via a web service)
  5. 5. Usecase: Banking sample
  6. 6. Use Case: Extensions to banking sample ● Account opening procedure: ○ Check weather customer exists ( in customer database) ○ if customer doesn’t exist, create a record in database ○ Validate Customer’s request (based on set of business rules) ○ Send for Bank manager’s approval if required. ○ Create the account ( Accounts are maintained in mainframe system) ○ Link the debit card to account. ○ Issue debit card ( - done by a separate system. Accessed via a web service)
  7. 7. Use Case: Extensions to banking sample ● Cross cutting concerns: ○ Account opening service needs to be secured and access controlled. ○ Need to understand usage patterns of the service by collecting statistics at differents stages. E.g: ■ Number account opening requests. ■ Number of requests required manager approval
  8. 8. Extended Banking usecase
  9. 9. High level Architecture (and Product Mappings)
  10. 10. Account Opening API https://api.sample.org:9452/store/
  11. 11. BPEL/Human Task https://bps.sample.org:9445
  12. 12. Business Rules • Account creation requires approval under following conditions If customer is underage or Initial deposit is below required minimum https://brs.sample.org:9450/carbon
  13. 13. Data Services • Expose customer database as service • Used to check the existence of the customer https://dss.sample.org:9449/
  14. 14. Proxy Services/Endpoints https://esb.sample.org:9444/
  15. 15. Analytics • BAM: Number of Account Opening requests per account type. • CEP: Detect suspicious activities, trigger alarms/emails: Total account deposits > 1 000 000 for a particular customer within 1 minute https://bps.sample.org:9445/ https://cep.sample.org:9453
  16. 16. Demo http://as.sample.org:9763/RetailBankingApp-1.0.0/ http://as.sample.org:9763/HumanTaskWebApp-1.0.0/
  17. 17. QUESTIONS?

×