View stunning SlideShares in full-screen with the new iOS app!Introducing SlideShare for AndroidExplore all your favorite topics in the SlideShare appGet the SlideShare app to Save for Later — even offline
View stunning SlideShares in full-screen with the new Android app!View stunning SlideShares in full-screen with the new iOS app!
Bank wants an easy way to access customer, product, and account information spread across all lines-of-business.
Deploying SOA, where customer data can be consolidated and integrated across the different product silos, can provide a single, comprehensive real-time view of a customer’s relationship with the bank. By connecting back-end legacy systems to front-end delivery channels, an SOA enables customer data to be made available in real-time at all the bank’s touch points – ATMs, online banking, call centers and retail branches – so that the bank is able to provide accurate, personalized service based on a complete relationship profile.
Adopting an SOA approach delivers a more consistent multi-channel experience. Data, applications and processes are exposed as services, which can be re-used across the different channels, ensuring that all channels have access to a common set of processes, systems and data.
Banks can achieve tighter coordination and integration of their channels so that customer interactions can be managed, tracked and completed across multiple channels. For example, a customer can initiate an activity such as applying for a loan via one channel and complete it using another.
Converging isolated back-office systems into a single, consistent data and services hub
A complex IT environment can lead to automation gaps in business processes, which result in customer service issues. For example, a fragmented mortgage origination process often leads to lengthy ‘time to offer’ cycles, which ultimately causes the customer to be so frustrated that he ends up taking his business elsewhere.
BPM technology can help banks achieve operational excellence by bridging automation gaps and enabling banks to standardize on best-in-class practices across the different channels and product lines.
Hence in order to fulfill the SLA, and sort out performance, availability and scalability issues we must
Proactively do necessary analysis and do proper capacity planning, followed by implementation and testing .
In production, do an end-to-end monitoring of the performance across all application tiers, back-end databases and Web Services, to pinpoint and address performance bottlenecks within the application and find root causes.
Within the network infrastructure there are many components that impact performance and capacity including connection speeds, routers, switches, traffic load balancers, encryption (SSL) and transformation (XLST) accelerators, application server, database.
SOA is a composite application made of services with varying performance and availability characteristics. One must consider the SLA of every service within the composite service since the weakest link impacts overall performance and availability.
To establish a capacity plan one must establish the baseline performance characteristics of the infrastructure then plan for future growth. Once the initial infrastructure is setup, establish a set of processing patterns to test capacity. The processing patterns need to cover typical SOA design patterns and exercise all the components within the infrastructure. Processing patterns should include a mix of simple, medium and complex patterns. For example, a simple pattern would be validate (a schema), transform (XLST) and publish (a message). More complex patterns would include work flows, database lookups (cross reference and enrichment), message routing and database transactions.
* Properly plan for infrastructure cost, time, deliverables and dependences as part of the SOA project plan * Consider professional services for hardware sizing, software installation, configuration and certification * Put the software vendor on the hook to support the initial architecture, configuration and performance of the infrastructure * Dedicate an administrator to the SOA infrastructure early in the project to work with the vendor though the installation, configuration and testing * Send the administrator to the administration training courses * Do a capacity test on the production environment before deployment * Track your systems dependencies and include them in an operations guide as part of project transition