1 / 32

Alliance Integrator

Alliance Integrator. Kris Vanholst SWIFT Product Management. Pat Antonacci SWIFT Consulting Services. Anna Ngai Bank of Montreal. Agenda. About Alliance Integrator Integrator Releases & Support What is new in Integrator 7.0 Consulting Services The BMO Integrator experience.

fallon
Download Presentation

Alliance Integrator

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. Alliance Integrator Kris Vanholst SWIFT Product Management Pat Antonacci SWIFT Consulting Services Anna Ngai Bank of Montreal

  2. Agenda • About Alliance Integrator • Integrator Releases & Support • What is new in Integrator 7.0 • Consulting Services • The BMO Integrator experience

  3. About Alliance IntegratorThe Framework File & FTP Transform AFT Database Business Data SWIFT Messaging Translate Queuing & Message MQSA & MQHA Alliance Access / Entry Alliance Integrator SWIFT Messaging Validate SOAP Business Data Business Application SOAP Copy Web Platform

  4. Integrator releasesIntegrator 7.0 now available • General availability date – 24 June 2011 • Mandatory release • Install by 30 September 2012 • Works with Alliance Access 7.0 and Alliance Entry 7.0 • Upgrade path 1.0 2.0 2.1 7.0

  5. Support • Integrator 7.0 will be supported by SWIFT at least throughDecember 2016 including: • The Integrator software • The underlying Java CAPS 6.3 software and any other embedded software • Standards releases and other standards components (translations, validations, schemas) • SWIFT supports the underlying Java CAPS 6.3 (GlassFish, NetBeans) for this period, and is backed by Oracle • Alliance Integrator Care option available for custom software

  6. What’s New in Integrator 7.0?Semantic Validation for FIN Messages Rules available on request

  7. What’s New in Integrator 7.0?Duplicate Check • Any data • MT or MX • ToSWIFT • FromSWIFT • Reject or mark as duplicate

  8. What’s New in Integrator 7.0?Export Configuration Data by Customer Integrator Prod. Integrator Test Customer 1 Configuration Customer 1 Configuration Customer 2 Configuration

  9. What’s New in Integrator 7.0?A quick read of other items • FileAct via SOAP and MQHA (in combination with Access) • Support for SWIFTNet copying and distribution features • Real-time File Get Request • Native user management • Encoded and compressed messages • Connectivity to Alliance Entry 7.0 • Validation of Block 4 before conversion to MT • Central site qualification • Other enhancements and bugfixes

  10. Consulting Services Supporting your initiatives and priorities Capitalise on your existing SWIFT infrastructure Implementbest-practices Efficiently manage SWIFT operations Ease implementation of Industry initiatives Maximise STP and reduce back-office processing costs Get valuable market insights and benchmarking

  11. License to believe 450+ Projects 350+ Clients 75+ Countries Average satisfaction rating of above 4.5/5.0 35 members and growing 15 years average experience Access to 2,000 + SWIFT specialists Partners

  12. The BMO Integrator experience Anna Ngai Technology HeadTechnology Development Capital Markets & Risk ManagementBMO Financial Group

  13. The challenge • Reduce impact of SWIFT changes to the BESS payments engine • Enhance the bank’s readiness to the new XML based and ISO 20022 messaging • Ensure long term support for SWIFT messaging • Reduce dependency on legacy code and skills Objective - Remove “pure” SWIFT wireroom functionality out of the current payments engine

  14. Alliance Integrator Consulting Services The solution – A new WireRoom Application (WRAP) Why did we decide on Integrator & SWIFT… • Improved Time to market for integration • Reduced project and operational risk • Leverage on a proven solution • We needed a vendor to rely on, with good track record - To assist initially and for the long term

  15. The solution – A new WireRoom Application (WRAP) Some Internal Objectives… • Standardise internal interfaces using a single interfacing method (MQ GI) • Minimise impact to interfacing systems • Avoid “first timer” mistakes • Thru-put target: 1/3rd of theday’s volume in < 1Hr

  16. WRAP components SWIFT Alliance family of products • SWIFT Alliance Access (SAA) • SWIFT Alliance Integrator (SAI) • SWIFT Alliance Gateway (SAG) Third party solutions • Reporting tool for SAA • Scanning Agent

  17. Lessons learned Challenges • Install and environment complexity,Trip-time increase • Multi-threaded architecture &“SAI enforced” validation Benefits • Project: Risk, Cost, Performance andTime to market! • Significant thru-put improvement (~3x) • Well positioned for MX migration Critical success factors • Reduce risk by phased implementations • Thorough Functional & Non-Functional testing • SWIFT Professional Services • A GREAT internal team !!!

  18. Q&A ?

  19. Thank you

  20. Appendix

  21. General InformationPlatforms / Environments • Windows Server 2008 R2 Enterprise edition and Standard edition • Oracle Solaris 10 Hardware revision 10/09 • AIX v6.1 Technology Level 04 with SP3 • AIX v6.1 Technology Level 06 with SP2 • Virtual environments per Alliance policy • References • OS Levels and Patches Baseline for SWIFTNet 7.0 • Alliance Access Product Family - Compatibility Matrix • Alliance Integrator 7.0 Release Letter • If using MQHA • IBM WebSphere MQ 7.0.1 • IBM WebSphere MQ 7.0.1.3 (recommended)

  22. What’s New in Integrator 7.0?Native user management X • No Oracle Access Manager (Windows and Solaris) • No OpenSSO (AIX) • Native user management • User roles • Password policies • Re-use existing user data from Integrator 2.1 (not passwords)

  23. What’s New in Integrator 7.0?Copying and Distribution SWIFT ACK ACK ACK • Support for SWIFTNet 7.0 copying and distribution features • Appropriate acknowledgement reconciliation • Status monitoring

  24. What’s New in Integrator 7.0?Connectivity to Alliance Entry 7.0 xmlV2 Integrator Entry File transfer xmlV2

  25. What’s New in Integrator 7.0?FileAct via SOAP and MQHA Access only!

  26. What’s New in Integrator 7.0?Real-Time File Get Request • WSDL and schemas provided • Sample code provided • Process file using normal FromSWIFT flow

  27. What’s New in Integrator 7.0?Encoded and Compressed Messages • For processing TransmissionReport from InterAct • If intervention present • Document built • Content unzipped • Base64 content de-coded

  28. What’s New in Integrator 7.0?Validation of block 4 for conversion to MT Detect illegal characters!

  29. What’s New in Integrator 7.0?Central Site Qualification • Testing scenarios completed for central site • Special central site messages • Special acknowledgements

  30. What’s New in Integrator 7.0?Other Functional Enhancements • Knowledge base tip 3001097 • Length of Text field for events in Event Log increased to 80 characters • MT-XML conversion, Validate XML content setting is introducedin SendToSWIFT transaction step • SOAPHA connectivity extended to allow server authentication • sai_semval command uses the zipfile content to load semantic validation rules

  31. What’s New in Integrator 7.0?Resolved Problems • Knowledge base tip 3000747 • Change in sai_msgsvc command line tool • Fix for change view results • Document search values swapped • Example FileAct file format fixed • Support for non-self-contained MX schemas • Block 3 113 and 115 fields copied to xmlV2 after pre-processing(ToSWIFT flow) • Identifier for documents need not be unique across customers of for File Document types • Adding customer causes log event • Change to sai_msgsvc -addsvc • Deactivation of db recovery resets Oracle force logging to original • JMS looping for faulty message fixed • Namespaces in xmlV2

  32. What’s New in Integrator 7.0?More Translation Available Now! Planned

More Related