1 / 22

101970 - Leveraging Integration Broker To Increase Availability And Throughput

101970 - Leveraging Integration Broker To Increase Availability And Throughput. Top Reasons to Use IB. 10 Endorsed by Prof. Axe Emel at Whatsamatta U. 9 Dealing with a Broker makes you feel richer 8 Same initials as Irritable Bowel 7 It’s better than a Disintegration Broker

varen
Download Presentation

101970 - Leveraging Integration Broker To Increase Availability And Throughput

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 101970 - Leveraging Integration Broker To Increase Availability And Throughput

  2. Top Reasons to Use IB 10 Endorsed by Prof. Axe Emel at Whatsamatta U. 9 Dealing with a Broker makes you feel richer 8 Same initials as Irritable Bowel 7 It’s better than a Disintegration Broker 6 Less Prone to Inappropriate comments than App Package 5 One more thing to pad your resume with 4 It’s sure to impress the babes 3 Moderately Cool Sounding 2 Buzz words have hypnotic effect on management 1 A bad day with IB is better than a good day with COBOL

  3. Introductions Sam Pred Applications System Engineer Located in Minneapolis Currently supporting Benefits and 9.2 upgrade Wayne Fuller Applications System Engineer Located in Minneapolis Technology Lead for 9.2 Upgrade

  4. Agenda • About Wells Fargo • High Volume • High Availability • Messaging Architecture • When to Message?

  5. Wells Fargo Population • Wells Fargo & Company (NYSE: WFC) Wells Fargo & Company is a diversified financial services company providing banking, insurance, investments, mortgage, and consumer and commercial finance through more than 9,000 stores and more than 12,000 ATMs and the Internet (wellsfargo.com) across North America and internationally serving over 70 million customers. • We employ over 282,000 team members in more than 35 countries across our 80+ businesses • Current US population consists of • 265,000 full-time employees • 16,000 part-time employees • 1800 flexible employees • 38,000 Managers

  6. High Volume • Alternative to traditional Batch processing • Concurrent Processing • Reduced Contention • Restartability • Business Logic Reuse

  7. High Volume • Annual Merit Increase Load PS HRMS IB CompEx AppEngine File CI JOB

  8. High Volume • Annual Merit Increase Load • 200,000+ via JOB_DATA CI. • Approx. 5 seconds per transaction. • 11.5 days to single thread. • Reduced to 14 hours via messaging. • Respond to errors as they occur.

  9. High Volume • HRA Compensation Category PS HRMS HRA Cat SavePost Change JOB IB AppEngine

  10. High Volume • HRA Compensation Category • ~280,000 processed in 168 minutes • 1,667/min or 28/sec • Multiple sources of input (batch/real time)

  11. High Volume • Other Uses • Automated Benefits Reprocessing (single thread 3 to 4 hours, down to 30 minutes) • Quarterly ABBR Calc • Reorgs (dept/company changes) • Acquisition Loads

  12. High Availability • Staff Management PS HRMS Handler IB Asynch Staff Mgmt POS Data CI JOB Data CI

  13. High Availability • Staff Management • 38,000 managers • 24/7 Access • Decouple request from fulfillment • Asynch to Synch (commit points)

  14. High Availability • Employee Self Service • W4, Direct Deposit (future) • No need to lock Team Members out • Improve satisfaction levels

  15. Messaging Architecture • Two dedicated servers • Runs only messaging, services and gateway, no application servers • Gateway load balanced, allows sync services to run balanced • Node load balanced through Gateway setup • 2 CPU/2.27 gHz 16 core machines with 24 GB of memory • Average daily use < 15% of capacity • Method to use multi-queues • Delivered doesn’t work • Helps with contention and partitioning the work • Only with unordered queues • ig.connection property in integration.properties • Maximum cached connections, connection time is costly when hit heavily with synchronous services • Default is 10, changed to 200

  16. Messaging Architecture F5 – Load Balancer Server A Server B Physical Gateway Physical Gateway Async Master Async Slave Sync Domain 1 Sync Domain 1 Sync Domain 2 Sync Domain 2

  17. Messaging Architecture • Current • Async 7 dedicated servers on master, only default goes to slave • Sync 4 domains load balanced with 2 gateways, 10 appservs each • Future • Sync stays the same • Slave processing takes place of dedicated servers, will try using only default

  18. Some Numbers • Synchronous services • TurboTax W2 service • 1,000 to 2,000 daily, avg. of .5 seconds. Utilized Datapower transformation • Job Agent service • 35,000 daily, avg < .3 seconds. • Asynchronous • Identity management message • 5000 daily, < .13 seconds • Guaranteed email • 35000 daily • Staff Management • 7500 daily

  19. When to Message? • High Volume Concurrent Processing • Ability to pause processing, scheduling flexibility. • High Availability (decoupling) • Transactions from multiple sources (internal/external/batch/online). • Error Handling • Can respond to errors while transactions continue processing

  20. Questions??

  21. Wells Fargo Sessions

  22. Save the Date APRIL 7-11, 2014 Sands Expo and Convention Center Las Vegas, Nevada QuestDirect.org/COLLABORATE COLLABORATE 14- Quest Forum is THE source for PeopleSoft roadmaps & news. It matters where you register! All PeopleSoft education and events run through Quest

More Related