Integrator Demonstration Sibos 2011 Toronto Kris Vanholst, SWIFT Product Management September 2011

Integrator Demonstration2 Table of Contents Integrator introduction New 7.0 features Key existing features Examples –Basic paymentsBasic payments –Choosing MT or MX for FundsChoosing MT or MX for Funds –FileAct for Workers’ RemittancesFileAct for Workers’ Remittances Maintenance of Standards

Integrator introduction 3Integrator Demonstration

The SWIFT integration challenge 4 Business application 1 Business application 2 Business application 3 Alliance Access Business data Business data SWIFT messaging SWIFT messaging Alliance Integrator Integrator Demonstration Back

Business Application Queuing & Message File & FTP SOAP Database Transform Translate Validate Copy Business data Business data SWIFT messaging SWIFT messaging AFT MQSA & MQHA SOAP Alliance Access / Entry Web Platform 5 Alliance Integrator The Alliance Integrator framework Integrator Demonstration Back

Integrator releases 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 Integrator Demonstration Back

Support Integrator 7.0 will be supported by SWIFT at least through December 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. 7Integrator Demonstration Back

Platforms/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.0OS Levels and Patches Baseline for SWIFTNet 7.0 –Alliance Access Product Family - Compatibility MatrixAlliance Access Product Family - Compatibility Matrix –Alliance Integrator 7.0 Release Letter If using MQHA –IBM WebSphere MQ –IBM WebSphere MQ (recommended) 8Integrator Demonstration Back

New features in Integrator 7.0 9Integrator Demonstration

Semantic Validation for FIN Messages 10 Rules available on request Integrator Demonstration Back

Duplicate Check 11  Any data  MT or MX  ToSWIFT  FromSWIFT  Reject or mark as duplicate Integrator Demonstration Back

Export Configuration Data by Customer 12 Customer 1 Configuration Customer 2 Configuration Integrator Test Customer 1 Configuration Integrator Production Integrator Demonstration Back

A quick read of other new features 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 13Integrator Demonstration Back

Native user management 14 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) X Integrator Demonstration Back

ACK Copying and Distribution Support for SWIFTNet 7.0 copying and distribution features –Appropriate acknowledgement reconciliation –Status monitoring 15 SWIFT Integrator Demonstration Back

Connectivity to Alliance Entry 7.0 File transfer xmlV2 16 Integrator Entry xmlV2 Integrator Demonstration Back

FileAct via SOAP and MQHA 17 FINInterActFileAct File Transfer MQHA SOAP Access only! Integrator Demonstration Back

Real-Time File Get Request WSDL and schemas provided Sample code provided Process file using normal FromSWIFT flow 18Integrator Demonstration Back

Encoded and Compressed Messages For processing TransmissionReport from InterAct –If intervention present Document built Content unzipped Base64 content de-coded 19Integrator Demonstration Back

Validation of block 4 for conversion to MT 20 Detect illegal characters! Integrator Demonstration Back

Central Site Qualification Testing scenarios completed for central site –Special central site messages –Special acknowledgements 21Integrator Demonstration Back

Other Functional Enhancements Knowledge base tip –Length of Text field for events in Event Log increased to 80 characters –MT-XML conversion, Validate XML content setting is introduced in SendToSWIFT transaction step –SOAPHA connectivity extended to allow server authentication –sai_semval command uses the zipfile content to load semantic validation rules 22Integrator Demonstration Back

Resolved Problems in 7.0 Knowledge base tip –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 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 23Integrator Demonstration Back

Existing features 24Integrator Demonstration

Standalone Flows 25 NAK Integrator Demonstration Back

SOAP Connectivity to Access 26 Alliance Access 6.3/7.0 Alliance Integrator MQSA/MQHA AFT Integrator Demonstration Back

Database Recovery Warm restart following recovery Configuration and operational data to last committed database transaction Consistent with Access 6.3 database recovery 27Integrator Demonstration Back

Demos Integator Demonstration28

29 An example – Payments to SWIFT SWIFTNet … SWIFT Correspondents DEMOBank NY Payments Department Accepts interchange Parses interchange into separate documents If necessary, determines steps via Partner Lookup Transforms to proper payment format Prepares XMLv2 and sends to Access Prepares payments and transmits to Integrator Reconciles acknowledgement and updates status ACK Integrator Duplicate check Semantic validation Integrator Demonstration Back

30 SWIFTNet An example – Funds to SWIFT SWIFT Correspondents DEMOBank LU Funds Department Accepts interchange Parses interchange into separate documents In our example, determines MT/MX based on ISIN Transforms to proper funds format (MT or MX) Prepares XMLv2 and sends to Access Prepares funds order and transmits to Integrator Reconciles acknowledgement and updates status ACK Funds Application … Integrator Integrator Demonstration Back

FileAct Flows (1/2) No more “files in the DMZ” (Access 6.3) Parameters managed by Integrator Pass-through flows for prepared files Mapping flows for content transformation and header calculations 31 Business application Prepare for FileAct Alliance Access Business Data Business application Business data Prepare for FileAct Alliance Access Transform item by item Build header fields Integrator Demonstration Back

32 Sending Workers’ Remittances (2/2) Integrator Demonstration Back

Translation 33 MXMT Subscription OrderMT 502 Redemption OrderMT 502 Subscription Order ConfirmationMT 515 Redemption Order ConfirmationMT 515 Order Instruction Status ReportMT 509 Business application Translate Business data Business data SWIFT messaging SWIFT messaging Alliance Access Correspondent SWIFTNet MX Integrator Demonstration Back

Alliance Integrator Message Standard Update scenario 34Integrator Demonstration

Alliance Integrator Message Standard Update scenario Assumptions –Transformation Service transforms a CSV document into a MT103 –MT103 is part of Standard Release 2008 –New Release 2009 is downloaded from swift.com –MT103 field 71 is modified Method valid for any format update, Standard and Proprietary, XML and other formats Standard feature of Java CAPS 35 Integrator Demonstration Back

CSV to MT Message standard update Integrator Demonstration Back

Open Properties of Transformation Service 37 Message standard update Integrator Demonstration Back

Select new MT Message standard update Integrator Demonstration Back

39 Message standard update Integrator Demonstration Back

Open Transformation Service 40 Differences are automatically identified Explicit Validation errors 40 Message standard update Integrator Demonstration Back

Error correction: new mapping followed by… 41 Create a new mapping rule and validate 41 Message standard update Integrator Demonstration Back

Updated Transformation Services ready for testing 42 No validation errors New mapping rule 42 Message standard update Integrator Demonstration Back

Back to Contents Contact your local SWIFT representative for more information. 43Integrator Demonstration Back