WSO2 products like ESB and DataServices are helping Alfa-Bank modernize their integration architecture and move to a more flexible SOA. Key reasons for choosing WSO2 included its ease of use, administration and development. The architecture in use exposes core banking systems like Temenos T24 as services and uses WSO2 to compose and publish services to partners. Ongoing plans include adding business process support and improving support response times for the WSO2 products.
2. WSO2 in Action
• Old integration technologies
• Motivation to move to SOA
• Why WSO2?
• WSO2 Products in Alfa-Bank
• Architecture
• Statistics
• Issue handling for WSO2 products
• Interesting points about ESB usage
• Our plans
3. Main integration technologies were:
– RDBMS, RPC, Files
Cons: Security, Dependency lock, Offline processing
SQL RPC
Core systems
Old integration technologies in Alfa-Bank
RDBMS N
Files
RDBMS 1
External systems
Front systems
4. Goals:
• Less development (more configuration), small team, low cost
• Make integration fast & flexible
• Enable online processing
New Core Banking System
Temenos T24
Motivation to move to SOA
SQL RPC
Back systems
RDBMS N
Files
RDBMS 1
External systems
Front systems
•No RDBMS / RPC
•Specific OFS interface
•Near 35% of cost – integration
5. Why WSO2?
• Products with high license price out of compare
• Open source products:
– OpenESB
– JbossESB
– MuleESB
– WSO2 ESB & WSAS
• Key criteria
– Simple Administration
– Easy to understand
– Fast development
Everything evaluated practically
• Installation
• Development
• Administration
6. WSO2 Products in Alfa-Bank
WSO2 DataServices
• Enable functionality of relational databases for SOA
• With minor development we can expose Temenos T24 OFS
protocol as web services
WSO2 ESB
• Make composed web services
• Make proxy services for non-standard protocols
• Publish services for partners over internet
9. Issue handling for WSO2 products
First thing we do – ask the community at the forum
http://wso2.org/forum/
When there is a product bug, we report it in the
issue tracker
If the issue is critical, we fix it ourselves since we
have the source code.
10. Interesting points about ESB usage
• We use SVN to manage the source of ESB
configuration
• We use ANT to deploy ESB configuration
• We are generating documentation from WSDL with
XSLT into Confluence (corporate Wiki)
• We use RELAX-WS to generate WSDL (compact
RELAXNG for WSDL)
11. Our plans
We need complex message processing ( BPS? )
We need support to spend less time on wso2 code
digging and to have better time of response.
