SWIFT Middle East Regional Conference

SWIFT Middle East Regional Conference
Alliance Portfolio Abu Dhabi, United Arab Emirates 27-28 March 2012

Alliance 7.0 Agenda Alliance 2012 Highlights Alliance Gateway 7.0
Alliance Access/Entry 7.0 Alliance Integrator 7.0 SWIFT Middle East Regional Conference Alliance Portfolio

Alliance Portfolio Leverage R7 and launching new initiatives in 2012
Web Platform - cost reduction deploying SWIFT Database Recovery - increase resilience. Linux version - saving with next hardware renewal Lite 2 - Connectivity Resiliency Services Reduce TCO Increase Resiliency Available with R7 Available with R7 Pilot H2 2012 Live July 2012 Alliance Access - single interface for all traffic Web Services - unlock data for reporting. Reporting option Alliance Access – new framework Available with R7 TBC Increase Value Release 7.0 is a major and mandatory release, aimed to provide you with a platform evolving with your business needs, aligned with today’s technology and addressing your priorities. It consists of a comprehensive set of innovative new features and powerful new tools providing many opportunities to reduce costs and risks, improve efficiency, and increase flexibility. Release 7.0 features are designed to meet customers’ needs and will translate into benefits such as reduced cost and risk, better control and more value. For the Alliance interfaces, this means: A more modern, web-based graphical user interface (GUI) framework (the Alliance Web Platform) for the entire Alliance family Automated operations A customer-hosted database Support for disaster site recovery Easier installation/configuration management Easier integration of FileAct flows New web services to query the messages and events in Access The new release replaces aging technology that is reaching the end of support and introduces new technology including web services. Release 7.0 will also align the SWIFT community on new messaging features such as RMA (Relationship Management Application) support for FileAct and InterAct messages. Web Platform Finalisation Overview The finalisation of the Web Platform 7.0 consisted in supporting the administration and monitoring functions of Access and Entry, which were not yet available on release 6.3 of the Web Platform. The availability of these new functions, coupled with the existing Messenger and RMA functions (available on Web Platform 6.3 and migrated to 7.0), enables the Web Platform 7.0 to support all related Access services, using a browser based interface. Starting from this release, the Web Platform 7.0 can be positioned as an alternative to the Workstation 7.0. The Workstation 7.0 remains available, although in maintenance mode. In general, when a new function is implemented on Access 7.0 and it requires graphical support, the implementation of its associated graphical services is only done on the Web Platform 7.0. The Web Platform 7.0 is also available for Alliance Entry 7.0, supporting all graphical services required to operate Entry 7.0. The Workstation 7.0 remains available, in maintenance mode, for Entry 7.0. Enhanced Database Recovery With the introduction of the 'Database Recovery' option in release 6.3, Alliance Access provided a mechanism to recover the database content in case of a major incident resulting in the unavailability or corruption of the database. Database Recovery allows resuming operations with up to date business data. Database Recovery requires the licence option 14:DATABASE RECOVERY to operate. Access 7.0 enriches further Database Recovery to support the recovery of the database in a remote disaster site recovery scenario. Database Recovery now enables customers relying on the embedded Oracle database model to asynchronously replicate recovery data to the remote disaster site support. Database Recovery now support local and remote recovery scenario. Access 7.0 also features a new Database Repair Service, used to analyse a recovered database and prevent live messages to be sent as duplicate transactions. This service is triggered automatically by Database Recovery, once the database has been recovered. This service is also available for manual invocation, typically for the case where the database is hosted in the customer Oracle infrastructure and must be investigated following its recovery on a disaster site. In Access 7.0, the existing duplicate detection mechanism is also enhanced to detect full duplicate messages over all active days. This enhancement, which is part of core Access features, protects against accidental re-emission of messages by back-office and middleware applications, during their own recovery procedures. For a more detailed description of the different resiliency solutions supported by Access, please refer to the Database Recovery Information Paper available on This paper describes the different options supported by Database Recovery Linux Version NEW: Alliance on Linux. Following an increasing market demand, SWIFT will qualify the Alliance portfolio on RedHat Enterprise Linux during the second half of This will offer significant TCO reduction to some customers (typically those who are running on AIX or Solaris today, and have Linux as their preferred platform already). FileAct Support Access 6.3 initiated the support for FileAct, limited to the File Transfer adapter. With release 7.0, FileAct support has been extended to the MQHA adapter. Access 7.0 also provides a new adapter, the 'Direct FileAct' adapter, which can also be used by back-office applications for FileAct integration. The use of this new adapter is subject to the activation of a new licence option. This section provides a summary description how FileAct is supported in Access. 8.1 General Principles Overview With FileAct support, Access now provides a single integration window for back-office applications to support all SWIFT services (FIN, InterAct or FileAct). Access fully supports FileAct store-and-forward mode. Access partially supports FileAct in real-time mode. The limitations are further documented below. Query Operational Data 6.1 Overview Alliance Access 7.0 provides a generic Web Services layer, which allows business applications and third party applications to access specific data from Alliance Access using standard web protocols. These Web Services provide their full value only when integrated into an application developed by a partner or by the customer. Access 7.0 supports a new set of Web Services, the 'Message and Event Query Service', complementing the RMA Web Services already provided with Access 6.3. This new service offers the capability to search and query messages and events present in the Access database. Why reporting A large number of SWIFT connected users run a single Access/Entry interface, which is used to handle the exchange of all their FIN, InterAct, FileAct institution traffic between their various back office applications and SWIFT. A core function of Access/Entry, as a qualified FIN, InterAct, FileAct, and RMA interface, is to integrate customer back-office applications with SWIFT messaging services, and to record into an internal database all the steps necessary to successfully emit a message to SWIFT or to route to the back-office applications the messages received from SWIFT. Access/Entry also records all user activity, either related to manual creation of messages or to managing the life cycle of messages (verification, authorisation, modification). The value of the Access/Entry message database is therefore: Message concentrator: central consolidated storage of SWIFT traffic generated by all back office applications and users. Message payload plus audit data: for each message, the database stores the actual message data (i.e. the information exchanged over SWIFT with correspondent) and the whole audit information (i.e. how this message was processed between SWIFT and the back office applications). Message history: with R7.0, the embedded Oracle database can keep large volumes of message available for consultation. So far, the reporting potential on the Access/Entry message database has not been fully exploited. It is partially linked to Access/Entry close database model: the message content is accessible only via Access/Entry provided tools like Messenger for user consultation, or via Web services to use the message information from external applications (using a documented XML format). Core objectives The main objective of this evolution is to further leverage Access/Entry potential by adding a new reporting environment that can exploit all message information stored in the database. The reporting environment consists of two main deliverables: A reporting framework A set of ready-to-use reports SOAP The embedded SOAP Host Adapter offers an alternative to the MQ Host Adapter, providing an interactive, real-time exchange of MT/MX messages and FileAct files between Access and back office applications. Some important characteristics of the SOAP adapter are: Data transferred over a SOAP connection must use the XMLv2 format. This format is already used by other Access host adapters (File Transfer, MQHA and MQSA). The SOAP adapter requires the XMLv2 revision 2 level at minimum. The SOAP communication channel supports session management and duplicate prevention, and can as such guarantee a one time delivery. The communication is always initiated by the back office. Therefore, only a SOAP client is required in the back office. Alliance Access acts as the SOAP server. MQ Support With Access 7.0, the MQHA adapter is enhanced to support FileAct flows over IBM WebSphere MQ. Note MQSA 7.0 does not support FileAct. FileAct support over MQ requires the usage of the XMLv2 data format. The back-office application must provide the FileAct settings, using the XMLv2 data format. MQHA supports two different modes (Full & Mixed mode) to transfer the payload file. Packages SWIFT Remit Content •Alliance Integrator software •Consulting services, provided by SWIFT –Functional analysis of one business message flow (send or receive payments), systems and interfaces + project plan –Technical design of system components and process flows between Alliance Integrator and one back office application –Technical implementation: installation of Alliance Integrator; connectivity to one back office application; connectivity to Alliance Access; receiveor send XML customer transfers, generate or process reject/return and status messages; generate and receive FileAct payloads and headers, use Workers’ Remittances reference data –System integration testing in development environment –User acceptance testing –Workers’ Remittances certification tests with one counterparty bank –Go live with one counterparty bank in production environment –Project management Price •50 KEUR one-time fee (software + consulting services) •11 KUSD annual maintenance fee (software) •Travel and expense costs not included •Additional consulting services to connect more back office applications, test and go live with more banks or to build a send andreceive capability can be provided by SWIFT at 1,300 EUR/day •SWIFT training on Workers’ Remittances –ISO20022 messages is available Pre-requisites & conditions •Registration to Workers’ Remittances, Alliance Access and Gateway installed •Valid for Access bands -1 to 5 •Alliance Integrator can only be used for Workers’ Remittances –upgrade to full license required for additional services •At least 1 bank staff must have attended “Implementing Alliance Integrator” training (3 days, 1,650 EUR per person) •Offer valid till June 2011 FileAct Package The SWIFT FileAct Package for Alliance Integrator is designed to seamlessly migrate your ‘To SWIFT Gateway FTA/FTI flows’ to Alliance Access. This migration enables you to adopt RMA for these flows in compliance with evolving Rulebooks.BenefitsQuick transparent migration This package includes software which utilises your existing FTA/FTI parameter files or Sterling Connect:Direct configuration files in association with your application-prepared content files for transmission through Alliance Access for FileAct. Installation and test for the first application is accomplished in a few days. No training or additional hardware is usually necessary.Turnkey implementation All software and services to configure your first application flow and get it live are provided by SWIFT.Monitoring via the WebPlatform You can monitor the status of your files with the WebPlatform.FunctionalityThe FileAct Package — Converts FTA companion parameter file to/from XMLv2 — Converts the Sterling Connect:Direct configuration files to/from XMLv2 — Connects to Alliance Access using AFT, MQHA (7.0 only) or SOAPHA (7.0 only) — Connects to Alliance Entry 7.0 — Connects to 1 business application via the file system — Provides optional feedback to the business application (Alliance Access MessageStatus, TransmissionReport, and DeliveryReport) — Provides notification (success/failure) for every file sending or receiving operation. BAI2/940 Starter PackageThe SWIFT BAI2/940 Starter Package for Alliance Integrator is designed to seamlessly transform your cash reporting flows between BAI2 and MT 94x formats, either to or from SWIFT. Here is everything you need to jumpstart your project.BenefitsShort time to market This package includes everything you need to specify your mapping and implement the flows in a matter of weeks. No training or additional hardware is usually necessary.Best-practice transformation The pre-defined portion of the transformations has been developed based on input from SWIFT Standards and SWIFT Banking Initiatives staff, and validated against actual bank requirements.Turnkey implementation All software and services to configure your first application flow and exchanges with 3 counterparties (correspondents, banks, customers) are provided by SWIFT. Ease Integration SOAP, MQHA and DirectFileAct Alliance Integrator Launching Packages : SWIFTRemit, FileAct, BAI Available with R7 SWIFT Middle East Regional Conference Alliance Portfolio

Reduce TCO Increase Resiliency Alliance Portfolio
This slide provides a summary of the major features available on release 7. SWIFT Middle East Regional Conference Alliance Portfolio

Linux Version (Pilot H2 2012)
Reduce TCO Alliance portfolio Alliance Portfolio Alliance Web Platform Alliance Workstation Alliance WebStation Business Applications Alliance Integrator AFT MQSA/MQHA SOAP FileAct support ANY FORMAT AFT /SOAP Alliance Access Alliance Gateway Release 7.0 The release 7.0 includes all enhancements and features already provided by the optional releases 6.1, (6.2 for Access) and 6.3. These enhancements are described in the corresponding release letters. Oracle embedded Linux Version (Pilot H2 2012) LDAP Server Lite 2 ( Live July 2012) LDAP integration Standalone Access SWIFT Middle East Regional Conference Alliance Portfolio

Web Platform Release 7 Cost reduction deploying SWIFT
Reduce TCO Web Platform Release 7 Cost reduction deploying SWIFT Web Platform PKI mgmt Web Platform admin Messenger RMA Monitoring Configuration Gateway admin Browse ACCORD GUI* Financial application Access Gateway Web Platform Finalisation Overview The finalisation of the Web Platform 7.0 consisted in supporting the administration and monitoring functions of Access and Entry, which were not yet available on release 6.3 of the Web Platform. The availability of these new functions, coupled with the existing Messenger and RMA functions (available on Web Platform 6.3 and migrated to 7.0), enables the Web Platform 7.0 to support all related Access services, using a browser based interface. Starting from this release, the Web Platform 7.0 can be positioned as an alternative to the Workstation 7.0. The Workstation 7.0 remains available, although in maintenance mode. In general, when a new function is implemented on Access 7.0 and it requires graphical support, the implementation of its associated graphical services is only done on the Web Platform 7.0. The Web Platform 7.0 is also available for Alliance Entry 7.0, supporting all graphical services required to operate Entry 7.0. The Workstation 7.0 remains available, in maintenance mode, for Entry 7.0. Browser based GUI using the Web Platform In Access and Entry 7.0, all the GUI functions available on Workstation will now be available on the Web Platform. As new GUI functionality for Access/Entry is only implemented on the Web Platform, users are encouraged to install the Alliance Web Platform when upgrading to release 7.0. Alliance Messenger Package The Messenger package on Web Platform includes the functionality delivered in Messenger 6.0 as well as additional enhancements. Some of the additional enhancements that are available only on the Messenger package are: Direct FileAct functionality (7.0, not available on Entry) Authorisation of FileAct messages (7.0) Message search criteria is enhanced with FileAct Copy, FIN Copy, Bank Priority, and MUR fields (as from 6.3) Report export in HTML, xls, PDF, and CSV formats (as from 6.3) Support for FpML messages (as from 6.2) Support for AnyXML message format (as from 6.2) Fast mode for message creation, modification, and consultation (as from 6.2) Minor GUI enhancements such as date, BIC and currency pickers, and variable page size (as from 6.2) SWIFT Middle East Regional Conference Alliance Portfolio

Database Recovery Increase Resiliency
SWIFT Middle East Regional Conference Alliance Portfolio

Database Recovery What’s new with Release 7
Increase Resiliency Database Recovery What’s new with Release 7 Remote Disaster Site Support the recovery of the database in a remote disaster site recovery scenario (asynchronously) Database Repair Service Used to analyse a recovered database and prevent live messages to be sent as duplicate transactions. Re-emission Protects against accidental re-emission of messages by back-office and middleware applications, during their own recovery procedures. Database Recovery With Access 7.0, the Database Recovery option introduced in Access 6.3 will be enhanced to support remote disaster site recovery. It will allow bringing the database back to a consistent state, recovering from the last available transaction found in the incomplete set of recovery data. Enhanced Database Recovery With the introduction of the 'Database Recovery' option in release 6.3, Alliance Access provided a mechanism to recover the database content in case of a major incident resulting in the unavailability or corruption of the database. Database Recovery allows resuming operations with up to date business data. Database Recovery requires the licence option 14:DATABASE RECOVERY to operate. Access 7.0 enriches further Database Recovery to support the recovery of the database in a remote disaster site recovery scenario. Database Recovery now enables customers relying on the embedded Oracle database model to asynchronously replicate recovery data to the remote disaster site support. Database Recovery now support local and remote recovery scenario. Access 7.0 also features a new Database Repair Service, used to analyse a recovered database and prevent live messages to be sent as duplicate transactions. This service is triggered automatically by Database Recovery, once the database has been recovered. This service is also available for manual invocation, typically for the case where the database is hosted in the customer Oracle infrastructure and must be investigated following its recovery on a disaster site. In Access 7.0, the existing duplicate detection mechanism is also enhanced to detect full duplicate messages over all active days. This enhancement, which is part of core Access features, protects against accidental re-emission of messages by back-office and middleware applications, during their own recovery procedures. For a more detailed description of the different resiliency solutions supported by Access, please refer to the Database Recovery Information Paper available on This paper describes the different options supported by Database Recovery SWIFT Middle East Regional Conference Alliance Portfolio

Increase Value Alliance Portfolio

A new set of Web Services Message and Event Query Service
Increase Value A new set of Web Services Message and Event Query Service Web Platform Financial Applications Gateway Integrator Back Office Support Access Web Services The main benefit is to address the needs for analysing, from an external application, the operational data present in Access database SWIFT Middle East Regional Conference Alliance Portfolio

Alliance Access Reporting Pilot H2 2012 - Tentative
Increase Value Alliance Access Reporting Pilot H Tentative Current idea : Reporting framework in Alliance Access Set of predefined reports Report Category : Capacity Planning & System Management End of the Day check, including exceptions Back-office reconciliation reports Audit reports Why reporting A large number of SWIFT connected users run a single Access/Entry interface, which is used to handle the exchange of all their FIN, InterAct, FileAct institution traffic between their various back office applications and SWIFT. A core function of Access/Entry, as a qualified FIN, InterAct, FileAct, and RMA interface, is to integrate customer back-office applications with SWIFT messaging services, and to record into an internal database all the steps necessary to successfully emit a message to SWIFT or to route to the back-office applications the messages received from SWIFT. Access/Entry also records all user activity, either related to manual creation of messages or to managing the life cycle of messages (verification, authorisation, modification). The value of the Access/Entry message database is therefore: Message concentrator: central consolidated storage of SWIFT traffic generated by all back office applications and users. Message payload plus audit data: for each message, the database stores the actual message data (i.e. the information exchanged over SWIFT with correspondent) and the whole audit information (i.e. how this message was processed between SWIFT and the back office applications). Message history: with R7.0, the embedded Oracle database can keep large volumes of message available for consultation. So far, the reporting potential on the Access/Entry message database has not been fully exploited. It is partially linked to Access/Entry close database model: the message content is accessible only via Access/Entry provided tools like Messenger for user consultation, or via Web services to use the message information from external applications (using a documented XML format). Core objectives The main objective of this evolution is to further leverage Access/Entry potential by adding a new reporting environment that can exploit all message information stored in the database. The reporting environment consists of two main deliverables: A reporting framework A set of ready-to-use reports SWIFT Middle East Regional Conference Alliance Portfolio

Alliance Access Operational Reporting Functional Overview
Increase Value Reduce TCO Alliance Access Operational Reporting Functional Overview SWIFT Middle East Regional Conference Alliance Portfolio

Ease Integration Alliance Portfolio

Alliance Access – FileAct Interface
Ease Integration Alliance Access – FileAct Interface Payload File FileAct Settings Financial Applications File Transfer, MQHA, SOAP Access FTA/FTI Alliance Gateway solution is in maintenance mode. Payload File Financial Applications FileAct Settings Direct FileAct MENTION PACKAGES AND AI (as in summary slide in beginning) Access 7.0 will support FileAct exchanges over MQ based back office connections. MQHA will be enhanced to support FileAct transactions (MQSA will not support FileAct transactions). Access 7.0 will support a new 'Direct FileAct' Integration, simplifying the integration of back office applications. For file based exchanges, the back office will only need provide the payload file to initiate a FileAct exchange. There will be no need to generate an associated XMLv2 file to provide the FileAct settings. FileAct Support Access 6.3 initiated the support for FileAct, limited to the File Transfer adapter. With release 7.0, FileAct support has been extended to the MQHA adapter. Access 7.0 also provides a new adapter, the 'Direct FileAct' adapter, which can also be used by back-office applications for FileAct integration. The use of this new adapter is subject to the activation of a new licence option. This section provides a summary description how FileAct is supported in Access. 8.1 General Principles Overview With FileAct support, Access now provides a single integration window for back-office applications to support all SWIFT services (FIN, InterAct or FileAct). Access fully supports FileAct store-and-forward mode. Access partially supports FileAct in real-time mode. The limitations are further documented below. Access SWIFT Middle East Regional Conference Alliance Portfolio

Alliance Gateway 7.0 Enhanced automation and control
Silent Installation Licensing GUI Configuration Replication Integrated HSM Management SWIFT Middle East Regional Conference Alliance Portfolio

Alliance Gateway 7.0.10 January 2012
Scope Functional patch delivering operational enhancements aimed at reducing TCO Fixes for most problems identified since R7.0 Deliverables Alliance Gateway (includes RA, Gateway Admin GUI and Browse GUI ) Alliance Web Platform Enhancements Virtual SWIFTNet Users Local traceability of activity LDAP authentication Monitoring Alliance Gateway Alerts Multi-instance monitoring overview Event Search enhancements (e.g. Multi- severity and ‘text-based searches) Operational Message Partner and End-point configurations FT-Interfaces: LTA-Filter configuration parameter Supportability enhancements Browse: Preferences for messages confirmation Gateway 7.0.2: mandatory for FTI users! Support of store-and-forward system recovery Override of RequestRef in the parameter file Dependencies Gateway Web Platform Gateway Administration GUI Remote API and Browse are optional Remarks No licence update required – No WebStation update (or update on Gateway Admin GUI for WebStation) Backward compatible (no change on message flow) It is not possible to uninstall Alliance Gateway : Make sure that you take a full system backup Event Search Enhancements Multi-severity event search Additional GUI field Search Text to match text in logged events Selection of an Application ID from a drop-down Operational Enhancements When configuring a message partner that uses relaxed SNL format, the box that lists matching DN values is no longer restricted to 256 entries. When creating a new message partner or endpoint, operators can replicate an existing one before applying changes (Add As function). When performing certification or recovery of a certificate, Alliance Gateway asks the user to confirm the password entered to avoid typos (passwords typed are masked for security purposes). When doing an import operation (data replication facility), the related report will indicate if any data tampering has been observed (such as attempting to edit encrypted data), which may require further investigation. The Alliance Gateway Administration GUI lets a user determine the number of rows to show in a list when paging is offered. Max is now 999 (iso 200) Supportability Enhancements GUI-initiated sag_supportinfo : Operators using the Alliance Gateway Administration GUI on Alliance Web Platform can trigger the generation of sag_supportinfo and its transmission to SWIFT. Health check data collection : When running sag_supportinfo with the -hc option, Alliance Gateway adds information collected in the context of Alliance Gateway and the SWIFTNet Link health check. The GUI-initiated call of sag_supportinfo also allows an operator to provide this option. Enhancements delivered in Alliance Gateway (mandatory for FTI users) Store-and-forward system recovery: report for FT-Integrated (FTI) applications Override of RequestRef in the companion parameter file of FT-Adapter (FTA) SWIFT Middle East Regional Conference Alliance Portfolio

Accord GUI on Alliance Web Platform
SAB-1 Accord GUI-1 SAB-2 Accord GUI-2 SAB-3 Accord GUI-3 SAB-... Accord GUI-... Accord GUI Web Platform 7.0 Swift Alliance Gateway Swift Alliance Gateway 7.0 SWIFT Middle East Regional Conference Alliance Portfolio

Alliance Access Mandatory patch 7.0.20
Message Standards 2011 Mandatory as of November 19, 2011 Support for SSI updates and Sanctions solution FileAct over SOAP Completes our FileAct offering via Alliance Access Message and Event Extractor Web Service Command line SWIFT Middle East Regional Conference Alliance Portfolio

Alliance Access Optional patch 7.0.30
Must be installed on top of New features: GUI for Manual FileAct Additional FileAct header fields for Direct FileAct Internet Explorer 9 support for Web Platform Knowledge base tip for a detailed list of 11 minor enhancements implemented in this release Fixes Knowledge base tip for a detailed list of resolved problems SWIFT Middle East Regional Conference Alliance Portfolio

Alliance Access Optional patch 7.0.31
Must be installed on top of New features: Normalization for routing on requestor and responder DNs Fixes Knowledge Base tip for a detailed list of resolved problems addressed in this release. SWIFT Middle East Regional Conference Alliance Portfolio

Alliance Integrator Addressing a Situation
Largely paper based Impact on existing business processes Business processes Technical adapters Data formats (Standards) End-to end message flows SWIFTNet Business applications SWIFT interfaces Requires deep SWIFT expertise Complex technical activity SWIFT Middle East Regional Conference Alliance Portfolio

Alliance Integrator Customizable Platform
Web Platform Monitoring Alliance Integrator Transform Translate Validate Copy Duplicate Check Notify Queuing & Message File & FTP SOAP Database AFT MQSA & MQHA SOAP Business Application Business Application Business Application Business Data SWIFT Messaging Alliance Access / Entry Alliance Access / Entry SWIFT Middle East Regional Conference Alliance Portfolio

Alliance Integrator Project Delivery
Phased Approach Knowledge Transfer & Training WP1 Functional Annalysis WP2 Technical Design WP3 Implemen-tation WP4 Integration Testing WP5 Go-Live WP6: Project Management SWIFT Middle East Regional Conference Alliance Portfolio

Alliance Integrator More Than Just Software
SWIFT support Local services + Integrator Care Contract + Remote Support SWIFT Middle East Regional Conference Alliance Portfolio

Alliance Integrator Concretely
SWIFTRemit Interface Displacement FileAct Migration Format Conversion Message validation Automatic Rejection RTGS Automation SWIFT Middle East Regional Conference Alliance Portfolio

Reduce TCO Increase Resiliency
Alliance Portfolio Increase Value Reduce TCO Increase Resiliency Ease Integration Release 7.0 is a major and mandatory release, aimed to provide you with a platform evolving with your business needs, aligned with today’s technology and addressing your priorities. It consists of a comprehensive set of innovative new features and powerful new tools providing many opportunities to reduce costs and risks, improve efficiency, and increase flexibility. Release 7.0 features are designed to meet customers’ needs and will translate into benefits such as reduced cost and risk, better control and more value. For the Alliance interfaces, this means: A more modern, web-based graphical user interface (GUI) framework (the Alliance Web Platform) for the entire Alliance family Automated operations A customer-hosted database Support for disaster site recovery Easier installation/configuration management Easier integration of FileAct flows New web services to query the messages and events in Access The new release replaces aging technology that is reaching the end of support and introduces new technology including web services. Release 7.0 will also align the SWIFT community on new messaging features such as RMA (Relationship Management Application) support for FileAct and InterAct messages. Web Platform Finalisation Overview The finalisation of the Web Platform 7.0 consisted in supporting the administration and monitoring functions of Access and Entry, which were not yet available on release 6.3 of the Web Platform. The availability of these new functions, coupled with the existing Messenger and RMA functions (available on Web Platform 6.3 and migrated to 7.0), enables the Web Platform 7.0 to support all related Access services, using a browser based interface. Starting from this release, the Web Platform 7.0 can be positioned as an alternative to the Workstation 7.0. The Workstation 7.0 remains available, although in maintenance mode. In general, when a new function is implemented on Access 7.0 and it requires graphical support, the implementation of its associated graphical services is only done on the Web Platform 7.0. The Web Platform 7.0 is also available for Alliance Entry 7.0, supporting all graphical services required to operate Entry 7.0. The Workstation 7.0 remains available, in maintenance mode, for Entry 7.0. Enhanced Database Recovery With the introduction of the 'Database Recovery' option in release 6.3, Alliance Access provided a mechanism to recover the database content in case of a major incident resulting in the unavailability or corruption of the database. Database Recovery allows resuming operations with up to date business data. Database Recovery requires the licence option 14:DATABASE RECOVERY to operate. Access 7.0 enriches further Database Recovery to support the recovery of the database in a remote disaster site recovery scenario. Database Recovery now enables customers relying on the embedded Oracle database model to asynchronously replicate recovery data to the remote disaster site support. Database Recovery now support local and remote recovery scenario. Access 7.0 also features a new Database Repair Service, used to analyse a recovered database and prevent live messages to be sent as duplicate transactions. This service is triggered automatically by Database Recovery, once the database has been recovered. This service is also available for manual invocation, typically for the case where the database is hosted in the customer Oracle infrastructure and must be investigated following its recovery on a disaster site. In Access 7.0, the existing duplicate detection mechanism is also enhanced to detect full duplicate messages over all active days. This enhancement, which is part of core Access features, protects against accidental re-emission of messages by back-office and middleware applications, during their own recovery procedures. For a more detailed description of the different resiliency solutions supported by Access, please refer to the Database Recovery Information Paper available on This paper describes the different options supported by Database Recovery Linux Version NEW: Alliance on Linux. Following an increasing market demand, SWIFT will qualify the Alliance portfolio on RedHat Enterprise Linux during the second half of This will offer significant TCO reduction to some customers (typically those who are running on AIX or Solaris today, and have Linux as their preferred platform already). FileAct Support Access 6.3 initiated the support for FileAct, limited to the File Transfer adapter. With release 7.0, FileAct support has been extended to the MQHA adapter. Access 7.0 also provides a new adapter, the 'Direct FileAct' adapter, which can also be used by back-office applications for FileAct integration. The use of this new adapter is subject to the activation of a new licence option. This section provides a summary description how FileAct is supported in Access. 8.1 General Principles Overview With FileAct support, Access now provides a single integration window for back-office applications to support all SWIFT services (FIN, InterAct or FileAct). Access fully supports FileAct store-and-forward mode. Access partially supports FileAct in real-time mode. The limitations are further documented below. Query Operational Data 6.1 Overview Alliance Access 7.0 provides a generic Web Services layer, which allows business applications and third party applications to access specific data from Alliance Access using standard web protocols. These Web Services provide their full value only when integrated into an application developed by a partner or by the customer. Access 7.0 supports a new set of Web Services, the 'Message and Event Query Service', complementing the RMA Web Services already provided with Access 6.3. This new service offers the capability to search and query messages and events present in the Access database. Why reporting A large number of SWIFT connected users run a single Access/Entry interface, which is used to handle the exchange of all their FIN, InterAct, FileAct institution traffic between their various back office applications and SWIFT. A core function of Access/Entry, as a qualified FIN, InterAct, FileAct, and RMA interface, is to integrate customer back-office applications with SWIFT messaging services, and to record into an internal database all the steps necessary to successfully emit a message to SWIFT or to route to the back-office applications the messages received from SWIFT. Access/Entry also records all user activity, either related to manual creation of messages or to managing the life cycle of messages (verification, authorisation, modification). The value of the Access/Entry message database is therefore: Message concentrator: central consolidated storage of SWIFT traffic generated by all back office applications and users. Message payload plus audit data: for each message, the database stores the actual message data (i.e. the information exchanged over SWIFT with correspondent) and the whole audit information (i.e. how this message was processed between SWIFT and the back office applications). Message history: with R7.0, the embedded Oracle database can keep large volumes of message available for consultation. So far, the reporting potential on the Access/Entry message database has not been fully exploited. It is partially linked to Access/Entry close database model: the message content is accessible only via Access/Entry provided tools like Messenger for user consultation, or via Web services to use the message information from external applications (using a documented XML format). Core objectives The main objective of this evolution is to further leverage Access/Entry potential by adding a new reporting environment that can exploit all message information stored in the database. The reporting environment consists of two main deliverables: A reporting framework A set of ready-to-use reports SOAP The embedded SOAP Host Adapter offers an alternative to the MQ Host Adapter, providing an interactive, real-time exchange of MT/MX messages and FileAct files between Access and back office applications. Some important characteristics of the SOAP adapter are: Data transferred over a SOAP connection must use the XMLv2 format. This format is already used by other Access host adapters (File Transfer, MQHA and MQSA). The SOAP adapter requires the XMLv2 revision 2 level at minimum. The SOAP communication channel supports session management and duplicate prevention, and can as such guarantee a one time delivery. The communication is always initiated by the back office. Therefore, only a SOAP client is required in the back office. Alliance Access acts as the SOAP server. MQ Support With Access 7.0, the MQHA adapter is enhanced to support FileAct flows over IBM WebSphere MQ. Note MQSA 7.0 does not support FileAct. FileAct support over MQ requires the usage of the XMLv2 data format. The back-office application must provide the FileAct settings, using the XMLv2 data format. MQHA supports two different modes (Full & Mixed mode) to transfer the payload file. Packages SWIFT Remit Content •Alliance Integrator software •Consulting services, provided by SWIFT –Functional analysis of one business message flow (send or receive payments), systems and interfaces + project plan –Technical design of system components and process flows between Alliance Integrator and one back office application –Technical implementation: installation of Alliance Integrator; connectivity to one back office application; connectivity to Alliance Access; receiveor send XML customer transfers, generate or process reject/return and status messages; generate and receive FileAct payloads and headers, use Workers’ Remittances reference data –System integration testing in development environment –User acceptance testing –Workers’ Remittances certification tests with one counterparty bank –Go live with one counterparty bank in production environment –Project management Price •50 KEUR one-time fee (software + consulting services) •11 KUSD annual maintenance fee (software) •Travel and expense costs not included •Additional consulting services to connect more back office applications, test and go live with more banks or to build a send andreceive capability can be provided by SWIFT at 1,300 EUR/day •SWIFT training on Workers’ Remittances –ISO20022 messages is available Pre-requisites & conditions •Registration to Workers’ Remittances, Alliance Access and Gateway installed •Valid for Access bands -1 to 5 •Alliance Integrator can only be used for Workers’ Remittances –upgrade to full license required for additional services •At least 1 bank staff must have attended “Implementing Alliance Integrator” training (3 days, 1,650 EUR per person) •Offer valid till June 2011 FileAct Package The SWIFT FileAct Package for Alliance Integrator is designed to seamlessly migrate your ‘To SWIFT Gateway FTA/FTI flows’ to Alliance Access. This migration enables you to adopt RMA for these flows in compliance with evolving Rulebooks.BenefitsQuick transparent migration This package includes software which utilises your existing FTA/FTI parameter files or Sterling Connect:Direct configuration files in association with your application-prepared content files for transmission through Alliance Access for FileAct. Installation and test for the first application is accomplished in a few days. No training or additional hardware is usually necessary.Turnkey implementation All software and services to configure your first application flow and get it live are provided by SWIFT.Monitoring via the WebPlatform You can monitor the status of your files with the WebPlatform.FunctionalityThe FileAct Package — Converts FTA companion parameter file to/from XMLv2 — Converts the Sterling Connect:Direct configuration files to/from XMLv2 — Connects to Alliance Access using AFT, MQHA (7.0 only) or SOAPHA (7.0 only) — Connects to Alliance Entry 7.0 — Connects to 1 business application via the file system — Provides optional feedback to the business application (Alliance Access MessageStatus, TransmissionReport, and DeliveryReport) — Provides notification (success/failure) for every file sending or receiving operation. BAI2/940 Starter PackageThe SWIFT BAI2/940 Starter Package for Alliance Integrator is designed to seamlessly transform your cash reporting flows between BAI2 and MT 94x formats, either to or from SWIFT. Here is everything you need to jumpstart your project.BenefitsShort time to market This package includes everything you need to specify your mapping and implement the flows in a matter of weeks. No training or additional hardware is usually necessary.Best-practice transformation The pre-defined portion of the transformations has been developed based on input from SWIFT Standards and SWIFT Banking Initiatives staff, and validated against actual bank requirements.Turnkey implementation All software and services to configure your first application flow and exchanges with 3 counterparties (correspondents, banks, customers) are provided by SWIFT. SWIFT Middle East Regional Conference Alliance Portfolio

SWIFT Middle East Regional Conference

Similar presentations

Presentation on theme: "SWIFT Middle East Regional Conference"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

SWIFT Middle East Regional Conference

Similar presentations

Presentation on theme: "SWIFT Middle East Regional Conference"— Presentation transcript:

Similar presentations

About project

Feedback