cls star gateway migration
DESCRIPTION
Presentation from SWIFT's Operations Forum Europe 2014 on 26-28 November in ParisTRANSCRIPT
•CLS STAR Gateway
Migration
Thiru Vijayan
Enterprise Architecture and Strategy
• ® CLS and the CLS logo are registered trademarks of CLS UK Intermediate Holdings Ltd © 2014 CLS Intermediate Holdings Ltd.
• This document is for the exclusive use of the recipient and may not be quoted, forwarded, copied or shared, in whole or in part, without the prior written permission of CLS Group.
2
Agenda
Introduction
Standards – XML benefits
CLS GUI Browser support
Key considerations for XML/GUI implementation
Technical Approval Process – GUI
Technical Approval Process – XML
Q&A
3
CLS Gateway operational model
CLS gateways have local storage for the data files, which is used for recovery
CLS sends trade notifications to both Member primary and secondary gateways
Both gateways must be up and connected to the CLS core system
CLS Gateway Application
Internal storage
Data
filesC
LS
AP
I -
Inte
rfa
ce
SW
IFT
RA
-In
terf
ace
SAG/SNL
Member
Application
CLS PD processesCLS GUI
client
4
CLS STAR operational model
SWP/
SAG/SNL*
Member
Application
MQ
Browser Based
GUI
Legacy components removed
following completion of migration
5
STAR – CLS members architecture
• STP XML channel interface
ISO 20022-based XML messages
SWIFT InterAct store and forward Service as
transport between members and CLS
• STP – SWIFT FIN channel interface
Members can continue to use FIN CBT for MT-
based messaging over the SWIFT network
• Browser-based user interface
A browser-based GUI
Connectivity will be through the SWIFTNet Browse
service
All communication will be encrypted via HTTPS
and transactions will be subject to non-repudiation
6
Standards- XML benefits
CLS
Incoming from
member
XML ISO20022Phase 0 SR2014
Outgoing to member
XML ISO20022
Phase 0
SR2014
XML member
CLS Browse GUI
SR2014
SR2014 Schema used for screen
7
SWIFT Standards 2014 - XML
JAS now supports Standards 2014 ISO20022 XML
CLS will support both ‘migration phase 0’ (previous) and ‘SWIFT Standards 2014’
(current)
8
CLS GUI browser support and compatibility
Supported
Windows Internet Explorer 8
Windows Internet Explorer 9 (recommended)
Qualification in progress
Windows Internet Explorer 10
Qualification yet to start
Windows Internet Explorer 11
Under review
Firefox 24
9
Key considerations for XML implementation
Firewall connectivity set-up
10
Key considerations for XML implementation
MQ setup and consideration
(Details in interface specifications for CLS members)
11
Key considerations for XML implementation
MQ setup - local MQ configuration
12
GUI user provisioning guidance
Update the user provisioning worksheet
13
CLS Browse via primary
CLS Browse via Primary SWP
The secondary SWP is inactive
Two users in two locations
Browser-based
GUI
Browser-based
GUI
Primary
Production
SWP/SAG/SNL*
SWIFT
DISABLEDSecondary
Production
SWP/SAG/SNL*
* SNL upgraded with MI Channel Patch
14
TAP - CLS Browse via secondary
CLS Browse via secondary SWP
The primary SWP is inactive
Two users in two locations
Browser-based
GUI
Browser-based
GUI
Primary
Production
SWP/SAG/SNL*
SWIFT
DISABLED
Secondary
Production
SWP/SAG/SNL*
* SNL upgraded with MI Channel Patch
15
XML channel via primary connection
XML via primary SAG
The secondary SAG is inactive
MQMember
application
Primary
Production
SWP/SAG/SNL*
SWIFT
DISABLEDSecondary
Production
SWP/SAG/SNL*
* SNL upgraded with MI Channel Patch
16
XML channel via secondary connection
XML via secondary SAG
The primary SAG is inactive
MQMember
application
Primary
Production
SWP/SAG/SNL*
SWIFT
DISABLED
Secondary
Production
SWP/SAG/SNL*
* SNL upgraded with MI Channel Patch
17
Summary of the TAP tests
CLS
Browse
CLS XML
•Q&A