Professional Documents
Culture Documents
This document provides customers with an overview of the planned evolution of the Alliance product family. The main
focus of the document is on releases that are planned for 2017 - 2018.
13 December 2016
Alliance 7.2
Final Release Overview Table of Contents
Table of Contents
Preface............................................................................................................................................................... 3
Legal Notices................................................................................................................................................... 23
13 December 2016 2
Alliance 7.2
Final Release Overview Preface
Preface
This document provides an overview of the mandatory upgrades for the Alliance product family
releases that are planned for 2017- 2018, and the potential impact of these upgrades on your
existing application environment.
The following products and services are included in this release:
SWIFTNet Link
Hardware Security Module
Alliance Gateway (including Transaction Delivery Agent)
Alliance Access
CREST over SWIFTNet
Alliance Entry
Alliance RMA
Alliance Web Platform Server-Embedded
SWIFT WebAccess GUI
Alliance Remote Gateway
Note Only refer to the sections in this document that relate to the products or services your
institution has purchased.
The sole purpose of this document is to help technical implementers and operational users of the
Alliance products evaluate the impact of changes that will occur during the period 2017- 2018.
Implementers and users can use this document to plan resources and prepare budget allocations.
The following table lists all significant changes to the content of this document since the July 2016
release. This table does not include editorial changes that SWIFT makes to improve the usability
and comprehension of the document.
Added the target date for FileAct enhancements Key Release Dates
availability for vendor testing on ITB.
Updated the availability dates for Alliance Remote Key Release Dates
Gateway 7.2.
Alliance Remote Gateway for Release 7.2
Updated the availability date for the Transaction Key Release Dates
Delivery Agent 7.2.
Alliance Gateway 7.2
Added details on the HSM token and HSM card Hardware Security Module for Release 7.2
hardware refresh programme and related
subsidization for the new token model.
Updated the browser qualification for SWIFT SWIFT WebAccess GUI for Release 7.2
WebAccess GUI.
13 December 2016 3
Alliance 7.2
Final Release Overview Preface
Important This document is supplied for information purposes only, and shall not be binding, nor
shall it be construed as constituting any obligation, representation, or warranty on the
part of SWIFT.
The information in this document is the latest available at the date of its publication,
and further changes can occur.
For more information about the overall Alliance release policy, see the updated SWIFTNet and
Alliance Release Policy for release 7.2.
This updated version of the SWIFTNet and Alliance Release Policy includes the following changes
as compared to the version issued in February 2009:
The time frame between two major mandatory releases is now a minimum of 36 months.
An end-of-support policy for software versions has been added.
The time frame for maintenance support has been changed to 24 months.
The time frame for migration support has been changed to 12 months.
The OS baseline and update qualification supportability timeline has changed.
More flexible mechanisms for functional upgrades: the functional update is easier to install
compared to minor releases.
13 December 2016 4
Alliance 7.2
Final Release Overview Key Release Dates
Important All dates refer to the end of the month, unless noted differently.
For more details on the SWIFTNet 7.2 release, see the SWIFTNet 7.2 Final Release Overview.
Availability of the preliminary version of the Alliance 7.2 Release September 2015
Overview and the SWIFTNet 7.2 Release Overview
Availability of an updated version of the Alliance 7.2 Release Overview December 2016
and the SWIFTNet 7.2 Release Overview.
Availability of SWIFTNet Link 7.2 and Remote File Handler 7.2 for Mid May 2017
FileAct testing for software developers.
Availability of the complete Alliance 7.2 product family for general June 2017
distribution towards customers
Availability of SWIFTNet 7.2 in the Production environment for live
operations
Availability of Transaction Delivery Agent 7.2 for general distribution. January 2018
End of support for versions older than Alliance 7.2 and SWIFTNet 7.2. September 2018
13 December 2016 5
Alliance 7.2
Final Release Overview Alliance 7.2 Product Family
Upgrade Roadmap
Knowledge base tip 5020967 describes the R7.2 Upgrade Roadmap. This document provides an
overview of the most common migration scenarios and key upgrade notes. Prior to the general
availability of the 7.2 release, the R7.2 Upgrade Roadmap will be further updated with specific
details.
(1) Red Hat Enterprise Linux 6.7 will be supported only until 2020.
Note For all software products and all operating systems supported, the migration principle
will be that a new environment is set up separately from the existing infrastructure,
while configuration and business data of the existing system will be imported after the
installation of release 7.2.
Windows Server 2016 was released October 2016. SWIFT is working with its
suppliers to ensure the delivery of SWIFT products using this operating system. If any
embedded third-party products will not be available as planned, SWIFT will
communicate an alternative plan as soon as possible.
13 December 2016 6
Alliance 7.2
Final Release Overview Alliance 7.2 Product Family
When planning the upgrade of your environment, consider the following dependencies:
Red Hat does not provide an upgrade path from RHEL 6.x to RHEL 7.x.
Oracle does not provide an upgrade path from Solaris 10 to Solaris 11.
Microsoft does not provide a direct upgrade path from Windows 2008 to Windows 2016.
GUI qualification
GUI access via Alliance Web Platform Server-Embedded desktops will be qualified using the
following browsers, running on a Windows system:
Internet Explorer 11
Edge
Chrome
Firefox
Note SWIFT WebAccess 7.2 GUI will be qualified only with Internet Explorer 11.
MQ Integration
All products that provide the possibility to integrate with IBM MQ, will be made compatible with IBM
MQ 8.0. An IBM MQ 8.0 Client will be required in that case. Your MQ server infrastructure will have
to be compatible with MQ 8.0 Client. Contrary to what we mentioned in the preliminary release
overview, this does not mean that MQ Server 8.0 must be deployed.
Hardware sizing
SWIFT will not be able to provide actual hardware sizing information until close to the general
availability date. At the same time, SWIFT is aware that some customers are budgeting to acquire
new server hardware for the implementation of release 7.2. Given that release 7.2 is focused
around technology renewal, SWIFT assumes that if you budget for the same amount as what you
paid for your current hardware, you will have sufficient budget to acquire hardware in line with
release 7.2 and future traffic growth.
Important Release 7.2 does not require new hardware. The above advice is specifically for
customers that have ageing hardware or an internal policy that mandates them to use
new hardware for a project this size.
CAUTION If you do not upgrade by September 2018, the end of the SWIFTNet Link 7.2 migration
window, then the root key renewal will cause any software release prior to SWIFTNet
Link 7.2 to fail.
13 December 2016 7
Alliance 7.2
Final Release Overview Alliance 7.2 Product Family
required to communicate using SWIFTNet services, and access to market infrastructures services
using MI Channel.
2.1.1 Background
SWIFTNet Link 7.2 will integrate all changes made to SWIFTNet Link since 7.0. This will bring the
whole community to the same baseline and allow services to benefit from all these changes.
SWIFTNet Link 7.2 will be available as a native 64-bit application only, whereas preceding
SWIFTNet Link 7.0.x releases have been delivered as a 32-bit application. This will require all
applications that interact directly with SWIFTNet Link to be upgraded at the same time and to be
compiled in 64-bits.
Please be aware of the following:
SWIFTNet Link 7.2 will not be compatible with Alliance Gateway 7.0.x.
Only Remote File Handler 7.0.50 or higher (due to TLS only support) will be compatible with
SWIFTNet Link 7.2. This means that only FileAct Interfaces that use Remote FileHandler 7.0.50
or higher will be compatible.
A new 64-bit Remote File Handler will be delivered with the 7.2 release. To benefit from the
FileAct enhancements you must use Remote File Handler 7.2 and SWIFTNet link 7.2.
Remote File Handler 7.2 will not be compatible with SWIFTNet Link 7.0.x.
Security enhancements
SWIFTNet Link 7.2 will provide TLS 1.2 only support.
Further enhancements will be defined at a later stage in the framework of the Customer Security
Programme. For additional information, see the Customer Security Programme.
2.1.3 Installation
Knowledge base tip 5020967 describes the R7.2 Upgrade Roadmap. This document provides an
overview of the most common migration scenarios and key upgrade notes. Prior to the general
availability of the 7.2 release, the R7.2 Upgrade Roadmap will be further updated with specific
details.
13 December 2016 8
Alliance 7.2
Final Release Overview Alliance 7.2 Product Family
Post release 7.2, each new SWIFTNet Link release will be able to be installed as an update or from
scratch. Alliance Gateway 7.2 can only be used in conjunction with SWIFTNet Link 7.2.
(1) Red Hat Enterprise Linux 6.7 will be supported only until 2020.
Note For all software products and all operating systems supported, the migration principle
will be that a new environment is set up separately from the existing infrastructure,
while configuration and business data of the existing system will be imported after the
installation of release 7.2.
Windows Server 2016 was released October 2016. SWIFT is working with its
suppliers to ensure the delivery of SWIFT products using this operating system. If any
embedded third-party products will not be available as planned, SWIFT will
communicate an alternative plan as soon as possible.
During the installation period, you must upgrade each of the locally installed interface products
(which SWIFT will supply as part of release 7.2) in a specific order. You must start by upgrading the
interface product closest to SWIFT, and must finish with the interface product closest to your back
office.
SWIFTNet Link 7.2 must be installed before Alliance Gateway 7.2. To remain compatible, the
Alliance Gateway 7.2 install must follow immediately after the installation to SWIFTNet Link 7.2.
No mandatory qualification of Communication or Messaging Interfaces is required with SWIFTNet
7.2. However, an optional re-qualification can be considered. If you, as an Interface Vendor, are
interested in an optional re-qualification, kindly make your intention known by e-mail to
SWIFTNet.CBT.Qualification@swift.com.
13 December 2016 9
Alliance 7.2
Final Release Overview Alliance 7.2 Product Family
2.2.1 Background
There are two types of hardware security modules: a highly resilient and optimal LAN-based HSM
box, and an easy to use and portable USB-based HSM token or HSM card (used in combination
with a reader).
HSM box
Following the successful completion of the HSM box refresh, the IS6 HSM box is the only hardware
model supported on SWIFTNet Link 7.2. To identify which version of the HSM box software you
have, see to Knowledge Base tip 5018956.
The HSM box software version 6.1 becomes mandatory with release 7.2. This version, also
provided with SWIFTNet Link 7.0.50, includes all usability enhancements released with SWIFTNet
Link 7.0.x releases (see to Knowledge Base tip 5019374 for an overview of the HSM usability
evolution). The new HSM 6.1 release will also activate the enhanced security capabilities of the
new HSM box crypto card, which has been working so far in compatibility mode to ensure a smooth
HSM refresh.
You must upgrade all the HSM boxes to software version 6.1 by September 2018, at which time
previous versions of the HSM box software will no longer be supported.
HSM client
The HSM client, which manages the communication with the HSM hardware, is embedded in the
SWIFTNet Link. The HSM client for 7.2 will be delivered as a native 64-bit application.
2.2.2 Installation
Knowledge base tip 5020967 describes the R7.2 Upgrade Roadmap. This document provides an
overview of the most common migration scenarios and key upgrade notes. Prior to the general
13 December 2016 10
Alliance 7.2
Final Release Overview Alliance 7.2 Product Family
availability of the 7.2 release, the R7.2 Upgrade Roadmap will be further updated with specific
details.
HSM box
All registered SWIFTNet Link hosts must be running 7.0.50 or 7.2 prior to upgrading the HSM box
software version. SWIFTNet Link release 7.2 is backward compatible with the previous HSM box
software versions 5.6.x, but HSM box software version 6.1 is not compatible with SWIFTNet Link
versions older than 7.0.50.
For Remote PED users, the Remote PED Workstation software must be upgraded to version
7.2.0.1.
Prior to upgrading the HSM box software, the PED firmware must be upgraded to version
2.7.0-3; the HSM box software version 6.1 is not compatible with the previous PED firmware
version. To upgrade the PED firmware, a Remote PED Workstation is required. If you do not
have a Remote PED Workstation installed yet, you must set it up for this purpose.
All HSM boxes in a cluster must be upgraded before starting the HSM cluster; it is not possible to
run a cluster with a mix of boxes running on 6.1 and 5.6.x.
SWIFTNet Link 7.2 will only support IS6 HSM boxes.
The IS6 HSM box software can be upgraded to version 6.1 as of SWIFTNet Link 7.0.50. If you opt
to wait until SWIFTNet Link 7.2, then you must comply with the 15-month migration time line
specified for all products. Failure to upgrade to HSM IS6.1 by September 2018 will result in lack of
support for the old software and the migration, as well as incompatibility with SWIFT products on
release 7.2 and future updates.
2.3.1 Background
Alliance Gateway 7.2 builds on all the functionality of Alliance Gateway 7.0.x releases. Alliance
Gateway release 7.2 will align with SWIFTNet Link release 7.2 and will be built as a native 64-bit
application.
Alliance Gateway 7.2 will be designed to be compatible with Alliance Access/Entry 7.1.x.
13 December 2016 11
Alliance 7.2
Final Release Overview Alliance 7.2 Product Family
Alliance Gateway 7.2 will be designed to be compatible with AMH 3.3 and higher.
Remote API 7.0.40 or higher is designed to be backwards-compatible with Alliance Gateway 7.2.
Older versions of Remote API will not be supported by Alliance Gateway 7.2, due to TLS only
support.
This means that the following applications will be transparent as they use Remote API 7.0.40
currently:
Alliance Access 7.1.x or higher
Alliance Entry 7.1.x or higher
Alliance Messaging Hub 3.3 or higher
In addition, you must validate that Remote API 7.0.40 or higher is installed when using the following
applications:
Transaction Delivery Agent (TDA) 4.0.10 or higher
EUCLID 7.2 or higher
Third-party applications that use Remote API to connect with Alliance Gateway 7.2.
Product streamlining
SWIFT will take the opportunity to terminate the following license options with Alliance Gateway
7.2:
Simple Object Access Protocol (SOAP Proxy)
Web Services Host Adapter (WSHA)
Important You must terminate SOAP Proxy and WSHA licenses options and re-license your
Alliance Gateway prior to the import of Alliance Gateway configuration data in release
7.2. For additional information, see the Knowledge base tip 5016840.
Due to a pricing change effective January 1, 2016, the SIPN Band for an Alliance
Gateway license will only contain the fixed value of 57:SIPN Band -2. This change
will be the default value generated regardless of any parameter of any individual
contract or Global Tier value. As a result of this, you must re-license your Alliance
Gateway 7.0.x version prior to the import of Alliance Gateway configuration data in
Alliance Gateway 7.2.
Security enhancements
Alliance Gateway 7.2 will provide TLS 1.2 only support.
13 December 2016 12
Alliance 7.2
Final Release Overview Alliance 7.2 Product Family
Further enhancements will be defined at a later stage in the framework of the Customer Security
Programme. For additional information, see the Customer Security Programme.
2.3.3 Installation
When planning the upgrade of your environment, consider the following dependencies:
The Alliance Gateway 7.2 GUI requires Alliance Web Platform Server-Embedded 7.2.
The Alliance Gateway 7.2 Administration GUI requires Alliance Web Platform Server-Embedded
7.2.
When using SWIFT WebAccess services, formerly known as Browse Services, ensure that your
service provider has made this service compatible with the minimal operating system and
browser requirements set for the SWIFT WebAccess GUI package.
Knowledge base tip 5020967 describes the R7.2 Upgrade Roadmap. This document provides an
overview of the most common migration scenarios and key upgrade notes. Prior to the general
availability of the 7.2 release, the R7.2 Upgrade Roadmap will be further updated with specific
details.
Alliance Gateway 7.2 can only be used in conjunction with SWIFTNet Link 7.2. The GUI
functionality for HSM management requires SWIFTNet Link 7.2 and HSM box software version 6.1.
Post Release 7.2, each new Alliance Gateway release will be able to be installed as an update or
from scratch.
(1) Red Hat Enterprise Linux 6.7 will be supported only until 2020.
Note For all software products and all operating systems supported, the migration principle
will be that a new environment is set up separately from the existing infrastructure,
while configuration and business data of the existing system will be imported after the
installation of release 7.2.
Windows Server 2016 was released October 2016. SWIFT is working with its
suppliers to ensure the delivery of SWIFT products using this operating system. If any
embedded third-party products will not be available as planned, SWIFT will
communicate an alternative plan as soon as possible.
13 December 2016 13
Alliance 7.2
Final Release Overview Alliance 7.2 Product Family
GUI access via Alliance Web Platform Server-Embedded desktops will be qualified using the
following browsers, running on a Windows system:
Internet Explorer 11
Edge
Chrome
Firefox
2.4.1 Background
Alliance Access is targeted at medium- to high-volume customers. One instance can process up to
1 million messages per day, with a peak throughput of 40 TPS (144,000 messages per hour), using
an out-of-the-box configuration and mainstream hardware. This can be achieved under a specific
configuration and by tuning higher throughput for well-defined scenarios.
Product streamlining
SWIFT will take the opportunity to remove obsolete functionality from Alliance Access 7.2. The
following features will already be retired by the time release 7.2 becomes available, and some
remnants in the product will be completely removed:
CAS
Alliance Workstation
A workaround, provided to a limited set of customers, to negate the PDE enhancements
introduced in Alliance Access/Entry release 7.0.75. For details, see Knowledge Base tip
5019593.
As of Alliance Access 7.2, a direct connection between Alliance Access and IBM MQ Server will
no longer be supported. Similar to Alliance Gateway, only the use of a locally installed IBM MQ
8.0 client will be supported. If you use a direct connection to IBM MQ Server today, then you
must implement an IBM MQ 8.0 client in order to facilitate the migration.
Security enhancements
Alliance Access 7.2 will provide TLS 1.2 only support.
13 December 2016 14
Alliance 7.2
Final Release Overview Alliance 7.2 Product Family
Further enhancements will be defined at a later stage in the framework of the Customer Security
Programme. For additional information, see the Customer Security Programme.
2.4.3 Installation
The users of Alliance Access 7.1.20 (Standards 2016 update) can upgrade to Alliance Access 7.2.
SWIFT will provide a Standards 2017 update on top of 7.1.20. You will be able to upgrade to
Alliance Access 7.2 from this update as well.
If you are using your own Oracle database to store the Alliance Access database, then note that
Alliance Access 7.2 will no longer be compatible with Oracle 10 and Oracle 11. You must
implement an Oracle 12 database available in order to install Alliance Access 7.2.
If you have custom components based on the Alliance Developer Kit (ADK), you will need to
acquire an updated version from your supplier.
For custom code solutions based on IPLA, an impact assessment will need to be performed as
updates to the custom code may be required. If you have the "Developer Seat" licence and have
custom solutions, you will also need to validate that there are no impacts on your solutions. This
may also be the case for Integration Platform modules, including the SWIFT-provided custom
modules Connector for T2S and Connector for Sanctions.
Please be aware of the following:
Alliance Gateway 7.2. will be designed to be compatible with Alliance Access 7.1.
Alliance Access 7.2 will not be compatible with Alliance Gateway 7.0.x, and will require Alliance
Gateway 7.2 to be installed.
The Alliance Access 7.2 GUI requires Alliance Web Platform Server-Embedded 7.2.
When Alliance Access 7.2 is used to connect to the CREST service, you will require the Tuxedo 12
software used for the communication layer. The software used for your communication layer must
be installed independently from Alliance Access.
(1) Red Hat Enterprise Linux 6.7 will be supported only until 2020.
13 December 2016 15
Alliance 7.2
Final Release Overview Alliance 7.2 Product Family
Note For all software products and all operating systems supported, the migration principle
will be that a new environment is set up separately from the existing infrastructure,
while configuration and business data of the existing system will be imported after the
installation of release 7.2.
Windows Server 2016 was released October 2016. SWIFT is working with its
suppliers to ensure the delivery of SWIFT products using this operating system. If any
embedded third-party products will not be available as planned, SWIFT will
communicate an alternative plan as soon as possible.
GUI access via Alliance Web Platform Server-Embedded desktops will be qualified using the
following browsers, running on a Windows system:
Internet Explorer 11
Edge
Chrome
Firefox
2.5.1 Background
Alliance Entry 7.2 will inherit from the Alliance Access technology upgrade.
Further enhancements will be defined at a later stage in the framework of the Customer Security
Programme. For additional information, see the Customer Security Programme.
2.5.2 Installation
The users of Alliance Entry 7.1.20 (Standards 2016 update) can upgrade to Alliance Entry 7.2.
SWIFT will provide a FIN Message Standards 2017 update on top of 7.1.20. You will be able to
upgrade to Alliance Entry 7.2 from this update as well.
Please be aware of the following:
Alliance Entry 7.1 will be compatible with Alliance Gateway 7.2.
Alliance Entry 7.2 will not be compatible with Alliance Gateway 7.0.x, and will require Alliance
Gateway 7.2 to be installed.
The Alliance Entry 7.2 GUI requires Alliance Web Platform Server-Embedded 7.2.
13 December 2016 16
Alliance 7.2
Final Release Overview Alliance 7.2 Product Family
Note For all software products and all operating systems supported, the migration principle
will be that a new environment is set up separately from the existing infrastructure,
while configuration and business data of the existing system will be imported after the
installation of release 7.2.
Windows Server 2016 was released October 2016. SWIFT is working with its
suppliers to ensure the delivery of SWIFT products using this operating system. If any
embedded third-party products will not be available as planned, SWIFT will
communicate an alternative plan as soon as possible.
GUI access via Alliance Web Platform Server-Embedded desktops will be qualified using the
following browsers, running on a Windows system:
Internet Explorer 11
Edge
Chrome
Firefox
2.7.1 Background
Alliance Web Platform Server-Embedded is now the only user interface GUI for all Alliance servers
(Alliance Gateway, Access, and Entry).
Important Alliance Web Platform Server-Embedded is not a standalone product, and cannot be
installed separately. It must be ordered and installed in conjunction with Alliance
Gateway, Access, or Entry.
Further enhancements will be defined at a later stage in the framework of the Customer Security
Programme. For additional information, see the Customer Security Programme.
13 December 2016 17
Alliance 7.2
Final Release Overview Alliance 7.2 Product Family
2.7.2 Installation
Please be aware of the following:
The GUIs for Alliance Gateway, Access, and Entry 7.2 require Alliance Web Platform Server-
Embedded 7.2.
Alliance Web Platform Server-Embedded 7.2 will not be compatible with Alliance Gateway 7.0.x,
Alliance Access 7.1.x, or Alliance Entry 7.1.x.
Due to the technology changes in Alliance Web Platform Server-Embedded 7.2, it will not be
possible to install older GUI packages. For the same reason, it will not be possible for GUI
packages of release 7.2 products to be used on Alliance Web Platform Server-Embedded 7.0.x. As
a result, you will need to install Alliance Web Platform Server-Embedded 7.2 separately from your
existing environment to support a gradual migration track.
(1) Red Hat Enterprise Linux 6.7 will be supported only until 2020.
Note For all software products and all operating systems supported, the migration principle
will be that a new environment is set up separately from the existing infrastructure,
while configuration and business data of the existing system will be imported after the
installation of release 7.2.
Windows Server 2016 was released October 2016. SWIFT is working with its
suppliers to ensure the delivery of SWIFT products using this operating system. If any
embedded third-party products will not be available as planned, SWIFT will
communicate an alternative plan as soon as possible.
GUI access via Alliance Web Platform Server-Embedded desktops will be qualified using the
following browsers, running on a Windows system:
Internet Explorer 11
Edge
Chrome
Firefox
Note SWIFT WebAccess 7.2 GUI will be qualified only with Internet Explorer 11.
13 December 2016 18
Alliance 7.2
Final Release Overview Alliance 7.2 Product Family
2.8.1 Implementation
Alliance Remote Gateway for release 7.2 will be available in the Test and Training (T&T)
environment by the end of October 2017, and in the live environment by the end of November
2017.
SWIFT will provide formal communication when Alliance Remote Gateway for release 7.2 is
available in the test or live environment, and you can upgrade the Alliance Access and Alliance
Entry installations to release 7.2.
13 December 2016 19
Alliance 7.2
Final Release Overview Alliance 7.2 Product Family
IBM Java 8
MQ IBM MQ 8
Note For all software products and all operating systems supported, the migration principle
will be that a new environment is set up separately from the existing infrastructure,
while configuration and business data of the existing system will be imported after the
installation of release 7.2.
Windows Server 2016 was released October 2016. SWIFT is working with its
suppliers to ensure the delivery of SWIFT products using this operating system. If any
embedded third-party products will not be available as planned, SWIFT will
communicate an alternative plan as soon as possible.
2.10.3 Installation
Alliance Messaging Hub 3.6 is scheduled to be available by the end of the first half of 2017.
Alliance Messaging Hub 3.6 builds on all the functionality of previous Alliance Messaging Hub 3.x
releases.
Alliance Gateway and SWIFTNet Link 7.2 are backward compatible with Alliance Messaging Hub
versions 3.3 to 3.6.
13 December 2016 20
Alliance 7.2
Final Release Overview Alliance 7.2 Product Family
When migrating to Release 7.2, in the scope of Alliance Messaging Hub, customers have three
possibilities:
Stay on the current supported version 3.3 or higher.
Directly upgrade from one Alliance Messaging Hub version to a higher one, within the same
supported OS release.
Upgrade and migrate to the new OS release, whereby the migration principle is that a new
environment is set up separately from the existing infrastructure.
Note Upgrading Alliance Messaging Hub for Release 7.2 is optional if you are on AMH 3.3
or higher.
For detailed guidelines on how to perform an upgrade, see the AMH Upgrade Notes document that
is available with each AMH delivery.
13 December 2016 21
Alliance 7.2
Final Release Overview Questions, feedback and support
Exchanging views
If you want to share specific considerations with the product managers, send an e-mail to:
interface.changes@swift.com.
If you would like to share views with your peers, a topic is open in the SWIFT Alliance User
Community group on LinkedIn.
13 December 2016 22
Alliance 7.2
Final Release Overview Legal Notices
Legal Notices
Copyright
SWIFT 2016. All rights reserved.
Restricted Distribution
Do not distribute this publication outside your organisation unless your subscription or order
expressly grants you that right, in which case ensure you comply with any other applicable
conditions.
Disclaimer
The information in this publication may change from time to time. You must always refer to the
latest available version.
Translations
The English version of SWIFT documentation is the only official and binding version.
Trademarks
SWIFT is the trade name of S.W.I.F.T. SCRL. The following are registered trademarks of SWIFT:
the SWIFT logo, SWIFT, SWIFTNet, Accord, Sibos, 3SKey, Innotribe, the Standards Forum logo,
MyStandards, and SWIFT Institute. Other product, service, or company names in this publication
are trade names, trademarks, or registered trademarks of their respective owners.
13 December 2016 23