You are on page 1of 23

Alliance 7.

Final Release Overview

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

1 Key Release Dates...................................................................................................................................5

2 Alliance 7.2 Product Family.................................................................................................................... 6


2.1 SWIFTNet Link 7.2.................................................................................................................................. 7
2.2 Hardware Security Module for Release 7.2............................................................................................. 9
2.3 Alliance Gateway 7.2............................................................................................................................. 11
2.4 Alliance Access 7.2............................................................................................................................... 14
2.5 Alliance Entry 7.2...................................................................................................................................16
2.6 Alliance RMA 7.2................................................................................................................................... 17
2.7 Alliance Web Platform Server-Embedded 7.2....................................................................................... 17
2.8 Alliance Remote Gateway for Release 7.2............................................................................................ 19
2.9 SWIFT WebAccess GUI for Release 7.2............................................................................................... 19
2.10 Alliance Messaging Hub 3.6.................................................................................................................. 19

3 Questions, feedback and support........................................................................................................22

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.

Updated Information Location

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

Updated Information Location

Updated the version of Remote File Handler SWIFTNet Link 7.2


compatible with SWIFTNet Link 7.2.

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

1 Key Release Dates


The following table provides the key target release dates for Alliance 7.2 and SWIFTNet 7.2.

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.

Event Target period

Availability of the preliminary version of the Alliance 7.2 Release September 2015
Overview and the SWIFTNet 7.2 Release Overview

Availability of: July 2016


The final version of the Alliance 7.2 Release Overview and the
SWIFTNet 7.2 Release Overview
Vendor documentation
The updated SWIFTNet and Alliance Release Policy document

Availability of an updated version of the Alliance 7.2 Release Overview December 2016
and the SWIFTNet 7.2 Release Overview.

Availability of: March 2017


SWIFTNet 7.2 in Integration Testbed (ITB)
SWIFTNet Link 7.2 for software developers
Alliance Gateway 7.2 DTK software for software developers

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 Alliance Remote Gateway in the Production environment October 2017


for Test and Training (T&T) operations.

Availability of Alliance Remote Gateway in the Production environment November 2017


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

2 Alliance 7.2 Product Family


Planned for June 2017, Alliance 7.2 is the next mandatory technology release for the Alliance
product family.
Alliance 7.2 is designed to continue to provide a highly secure and efficient SWIFT service for our
customers in the years ahead. This release combines a new operating system baseline with
upgrades to the third-party products used within the SWIFT platform, inside Alliance products, and
SWIFTNet Link. It will retain all the functionalities of the previous product releases and introduce
FileAct enhancements. Additionally, this change will offer some significant performance benefits to
customers because it introduces 64-bit architecture while using the existing hardware.
Support for Alliance 7.0.x, Alliance 7.1.x, and SWIFTNet Link 7.0.x products will end in September
2018, at which point you will need to have installed release 7.2 of your Alliance software.
Be aware of the following:
IBM MQ 8.0 Client is required on the systems that run release 7.2 products, where IBM MQ is
used.
Alliance 7.2 GUIs will be qualified using Windows 7 and Windows 10.

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.

Operating system qualification


Alliance 7.2 server products will be qualified using the following operating systems:

Processor type Operating system Release level

x64 Windows Server 2016 Standard Edition

Power AIX 7.2

SPARC Oracle Solaris 11.3

x64 Red Hat Enterprise Linux 6.7 (1) or 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.

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.

Impact of SWIFTNet CA root key renewal


The renewal of the SWIFTNet CA Root Key requires the upgrade of SWIFTNet Link to release 7.2
by September 2018, the end of the SWIFTNet Link 7.2 migration window. All SWIFTNet certificates
rely on this root key being valid. Only SWIFTNet Link version 7.2 or higher will be able to handle
the new root key exchange.

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.

2.1 SWIFTNet Link 7.2


SWIFTNet Link is a mandatory SWIFT connectivity component for SWIFTNet users. SWIFTNet
Link ensures technical interoperability between users by providing the minimal functionality

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.

2.1.2 New Features


FileAct enhancements
SWIFT introduces with Release 7.2 a number of FileAct enhancements including:
The support of larger file sizes.
The automatic resume of file transfers.
The enhanced status of file transfers.
The enhanced transfer efficiency.
The dynamic control of concurrent file transfers.
For additional information, see the SWIFTNet 7.2 - Final Release Overview.

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.

2.1.4 System Requirements


SWIFTNet Link 7.2 will be qualified using the following systems:

Processor type Operating system Release level

x64 Windows Server 2016 Standard Edition

Power AIX 7.2

SPARC Oracle Solaris 11.3

x64 Red Hat Enterprise Linux 6.7 (1) or 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.

2.2 Hardware Security Module for Release 7.2


The Hardware Security Module (HSM) is a mandatory SWIFT connectivity component for
SWIFTNet users. The HSM is the security device used to safestore the SWIFTNet PKI certificates
and to generate signatures for the traffic. The device secures the generation, storage and use of
cryptographic keys by providing logical and physical protection

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 token and HSM card


This technology will undergo a hardware refresh as part of release SWIFTNet 7.2. A new token
hardware model will be introduced with SWIFTNet Link 7.2, replacing the previous models of both
HSM token and HSM card.
With release 7.2, no HSM card model will be supported. The new HSM token will be the only USB-
based model supported.
The models supported with SWIFTNet Link 7.0.x releases will not be compatible with SWIFTNet
Link 7.2.
To facilitate the upgrade, this hardware refresh will be subsidized: each user currently using, for
their SWIFT connectivity, either HSM tokens or HSM cards with their SWIFTNet Link (version prior
to 7.2) are entitled to a pack of 10 tokens of the new model free-of-charge. Should additional tokens
be required beyond the entitlement of 10 tokens, these should be ordered at standard price.
This offer applies only to customers equipped with the previous HSM token or HSM card models.
New users setting up their SWIFT connectivity after that SWIFTNet Link release 7.2 is available will
be able to use the new token model immediately and will need to order their tokens at standard
price. Customers entitled to an HSM token pack will be informed through a separate campaign,
which will provide further details on the distribution of tokens.

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.

HSM token and HSM card


SWIFTNet Link 7.2 will only support the new HSM token models. The HSM cards and card reader
will not be supported.
You must recover all certificates from the HSM tokens and HSM cards of the previous models onto
the HSM tokens of the new model after upgrading to SWIFTNet Link 7.2.

2.2.3 System Requirements


See the SWIFTNet Link 7.2 section for the system requirements applicable to the HSM client. The
Remote PED Workstation, which makes it possible to use the PED remotely from the HSM box, is
supported on Windows 7 and Windows 10.

2.3 Alliance Gateway 7.2


Alliance Gateway is a communications interface that enables you to concentrate the flows of
multiple messaging interfaces, and helps with traffic routing. It connects to SWIFT through a single
SWIFTNet Link instance, which takes care of the lower-level SWIFTNet protocol stack.

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.

Transaction Delivery Agent (TDA)


Transaction Delivery Agent 7.2 will be released on January 12 2018. Transaction Delivery Agent 7.2
will be available as a native 64-bit application and it will only support IBM MQ 8 Client.
Support for Transaction Delivery Agent 4.0.1, 4.0.2, and 4.0.10 will end in September 2018, at
which point you must install Transaction Delivery Agent 7.2.
Transaction Delivery Agent 7.2 will require a fresh install on the new operating system baseline and
the use of Remote API 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.

2.3.2 New Features

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.

2.3.4 System Requirements


Alliance Gateway 7.2 will be qualified using the following systems:

Processor type Operating system Release level

x64 Windows Server 2016 Standard Edition

Power AIX 7.2

SPARC Oracle Solaris 11.3

x64 Red Hat Enterprise Linux 6.7 (1) or 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.

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 Alliance Access 7.2


Alliance Access is SWIFT's prime messaging interface, designed to connect your business
applications to SWIFT messaging services.
Alliance Access is a multi-platform interface that enables you to connect single or multiple
destinations to SWIFT with the maximum automation of system management tasks.
The section below also covers CREST over SWIFTNet, as well as Standalone for Message Entry
and Repair.

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.

2.4.2 New Features


Alliance Access 7.2 will already support the FIN Standards Release 2017.

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.

2.4.4 System Requirements


Alliance Access 7.2 will be qualified using the following systems:

Processor type Operating system Release level

x64 Windows Server 2016 Standard Edition

Power AIX 7.2

SPARC Oracle Solaris 11.3

x64 Red Hat Enterprise Linux 6.7 (1) or 7.2

(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 Alliance Entry 7.2


Alliance Entry is a messaging interface targeted at low- to medium-volume customers.

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.

2.5.3 System Requirements


Alliance Entry 7.2 will be qualified using the following systems:

Processor type Operating system Release level

x64 Windows Server 2016 Standard Edition

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.6 Alliance RMA 7.2


Alliance Relationship Management Application (RMA) allows third-party interface users to manage
(create, modify, delete, revoke, accept, and reject) their RMA authorisations.
While Alliance RMA still exists as a commercial product, it no longer exists as a software package.
Instead, if you have an Alliance RMA contract you are able to use the same RMA functionality
through an Alliance Access 7.2 licensed for 'RMA use only' and will inherit from the Alliance Access
technology upgrade.

2.7 Alliance Web Platform Server-Embedded 7.2


Alliance Web Platform Server-Embedded is the framework that hosts browser-based graphical user
interfaces (GUIs) of the Alliance portfolio. Alliance Web Platform Server-Embedded runs in an
application server environment, enabling centralised deployment of the software.
The GUIs of the Alliance portfolio are provided as packages that are installed in Alliance Web
Platform Server-Embedded.

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.

2.7.3 System Requirements


Alliance Web Platform Server-Embedded 7.2 will be qualified using the following systems:

Processor type Operating system Release level

x64 Windows Server 2016 Standard Edition

Power AIX 7.2

SPARC Oracle Solaris 11.3

x64 Red Hat Enterprise Linux 6.7 (1) or 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.
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 Alliance Remote Gateway for Release 7.2


Alliance Remote Gateway is a hosted service managed and operated by SWIFT, which allows
customers to connect Alliance Access/Entry directly to the SWIFT network without the need for the
customer to manage its own Alliance Gateway, SWIFTNet Link, and Hardware Security Modules
(HSMs).
Alliance Remote Gateway supports the use of all SWIFTNet messages and files as supported by
Alliance Access/Entry (FIN/MT, InterAct/MX, FileAct), and supports the use of all WebAccess
services offered over SWIFTNet.

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.

2.9 SWIFT WebAccess GUI for Release 7.2


SWIFT WebAccess (previously named Browse) enables secure, browser-based access from an
end user who uses a standard browser to a service provider's web server over SWIFT. SWIFT
WebAccess is for person-to-application use, meant for use in the context of HTML-based
interfaces.
SWIFT WebAccess 7.2 GUI will provide compatibility with Alliance Gateway and Alliance Web
Platform Server-Embedded 7.2 releases. This release of the SWIFT WebAccess GUI will be
qualified only with Internet Explorer 11.

2.10 Alliance Messaging Hub 3.6


Alliance Messaging Hub (AMH) is a flexible, multi-network, high-volume financial messaging
solution.
AMH offers advanced features to integrate with the customer application landscape, using SWIFT
MT, ISO, and proprietary message standards, and to exchange those messages over either SWIFT
or other networks. The AMH configuration options, complemented with the embedded workflow
orchestration engine and message transformation module, make it possible to tailor the message
processing to the customer specific needs.

2.10.1 New Features


Security enhancements
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 19
Alliance 7.2
Final Release Overview Alliance 7.2 Product Family

2.10.2 System Requirements


Alliance Messaging Hub 3.6 will be qualified using the following systems:

Component Operating system Release level

Operating system Oracle Solaris 11.3

Microsoft Windows Server 2016

IBM AIX 7.2

Linux Red Hat Enterprise Linux 6.7 or


7.2

Database Oracle 11.2 and 12.1

Application Server IBM WebSphere 8.5.5.9

Red Hat JBoss EAP 6.4

Oracle WebLogic 12.2.1

Java Run-time (JDK) Oracle Java 8

IBM Java 8

MQ IBM MQ 8

Browser IE 11, Firefox, and Chrome

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

3 Questions, feedback and support


Questions and support
If you have questions with regard to the content of this document, report a case in the Case
Manager on www.swift.com.

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

You might also like