fileact in access
Post on 04-Jun-2015
704 Views
Preview:
DESCRIPTION
TRANSCRIPT
Presentation title Client or event
Speaker
Day Month Year
Presentation title – dd month yyyy – Confidentiality: xxx 2
Agenda
• FileAct Overview support
• Manual FileAct Support
• FileAct Traffic Control
• Summary & Benchmark
Alliance Interface positioning
Alliance Access
Alliance
Gateway
(FTI/FTA)
Alliance
WebStation
Support for
Manual file
transfer?
Support for
Automated file
transfer
Support for RMA
filtering and
ASP?
3
Alliance Access positioned as SWIFT strategic FileAct
interface for the future
Alliance 7.0
4
Alliance Access/Entry & FileAct
FileAct
traffic
benefits from
Access/Entry
rich set of
features
Support a
variety of
integration
mechanisms
Leverage
existing
SWIFT
infrastructure
Alliance 7.0
Alliance Access rich set of features
5
Security
Monitoring
Archiving
Security profiles and user definitions
extended to support FileAct
FileAct covered by Access monitoring
features (alarms, monitoring GUI, command
line monitoring tools, etc)
FileAct traffic history is stored in the database
and is archived next to FIN and MX traffic.
Note: File is NOT included in archives.
Routing Benefits from Access advanced routing
features
Alliance 7.0
Resilience Possibility to failover message flow to
secondary Gateway or implement multiple
active flows going over different Gateways
Automated integration through Alliance Access
6
Direct FileAct
XML v2
XML v2
message
Payload
File Payload
File only
Static
Payload Only
Dynamic
Payload with parameters
Automated integration through Alliance Access
7
Direct FileAct
XML v2
XML v2
message
Payload
File Payload
File only
Static
Payload Only
Dynamic
Payload with parameters
Automated integration through Alliance Access
8
Direct FileAct
XML v2
XML v2
message
Payload
File Payload
File only
Static
Payload Only
Dynamic
Payload with parameters
Routing information stored in XML v2 Routing information stored in Message
Partner configuration
Highly flexible integration trough a
variety of technical adapters (MQ, File
Transfer, SOAP)
Easy implementation through a file drop
mechanism
Recommended for customers using
many services, request types or
counterparties
Recommended for customers using a
limited number of services, request
types and counterparties
XML v2 based integration – Adapters
9
Access
and Entry
Back Office
Automated File
Transfer
SOAP
Host Adapter
File System
SOAP
MQ
Host Adapter
Access
Access
XML v2
message
Payload
File
XML v2
message
Payload
File
XML v2
message
Payload
File
XML v2 based Integration – Mixed mode
10
Alliance
Access
Back Office
MQ or SOAP
Host Adapter
WebSphere MQ
or
SOAP
File System
XML v2
message
Payload
File
Easy FileAct implementation on Access Direct FileAct
11
Direct FileAct
Message Partners
Payload
Files
Correspondent A
MP 1
Back Office
Access
Directory …
Directory …
Correspondent B
Correspondent C
SWIFTNet
Interface
-Responder DN A
-Service
-…
Directory …
MP 2
MP 3
-Responder DN B
-Service
-…
-Responder DN C
-Service
-…
Direct FileAct is only possible
with Static headers
Presentation title – dd month yyyy – Confidentiality: xxx 12
Agenda
• FileAct Overview support
• Manual FileAct Support
• FileAct Traffic Control
• Summary & Benchmark
Financial application
Manual File Transfer through Entry/Access
Web Platform
Gateway Entry/Access
13
The Alliance Messenger GUI package available on
Web Platform is enhanced to support manual file
transfer (patch 7.0.30)
7.0.30
Manual FileAct support
Overview
• Manual FileAct support
– Send files in real-time or store-and-forward mode
– Get files from SWIFTNet correspondents in real-time mode
– Monitor file transfers
– Abort file transfers
• Template support
– Similar to FIN, InterAct template support
Presentation title – dd month yyyy – Confidentiality: xxx 14
More information in Messenger Administration and Operations Guide Sections: - Message Creation > File Message Send, File Message Get
- Message Search and Report > File Transfer Monitoring
Manual FileAct Support
Receiving a file
Presentation title – dd month yyyy – Confidentiality: xxx 15
Manual FileAct Support
Sending a file
Presentation title – dd month yyyy – Confidentiality: xxx 16
Manual FileAct Support
Monitoring
Presentation title – dd month yyyy – Confidentiality: xxx 17
Save file content.
Also available on Messenger GUI.
Transfer progress
Presentation title – dd month yyyy – Confidentiality: xxx 18
Agenda
• FileAct Overview support
• Manual FileAct Support
• FileAct Traffic Control
• Summary & Benchmark
Controlling FileAct Black/White list
• Alliance Access supports only white list filtering, so all valid
correspondents must have an authorisation for the service
• The white list can be created using RMA bootstrapping for
FileAct, refer to section 4.7 “Create a bootstrap authorisation” in
the “Alliance Access 7.0 Relationship Management Guide”
• When created or modified, these authorisations do not trigger
the exchange of an authorisation Protocol Data Unit (PDU) with
the correspondent i.e. Only stored in local RMA data store
• Traffic filtering is effective based on the filtering date in the
Application Service Profile for that service
19
Pre-requisites
• The ASP (Application Service Profile) for the specific FileAct
service must be enabled for RMA
– e.g. SCORE is enabled for RMA
• A user can create authorisations if the profile that has been
assigned to him/her in Alliance Access includes the Create Auth
function of the Relationship Mgmt application
• The following permissions restrict the business relationships
that a user can access:
• Own Destination(s) (BIC8) (Allowed/Prohibited)
• Service(s) (Allowed/Prohibited)
20
Sample screen
21
Presentation title – dd month yyyy – Confidentiality: xxx 22
Agenda
• FileAct Overview support
• Manual FileAct Support
• FileAct Traffic Control
• Summary & Benchmark
Summary – FileAct on Alliance Entry/Access
23
MQ or
SOAP, full
mode
File
Transfer Direct
FileAct
MQ or
SOAP,
mixed
mode
Manual
Automation
Availability
Integration
Usage
Implementa
tion effort
Throughput
File drop Interactive File drop Interactive &
file drop
All usages
Low*/
Medium
Medium
Automated
or manual Automated Automated Automated Manual
As of R6.3 As of R7(MQ)
As of patch
7.0.20 (SOAP)
As of R7(MQ)
As of patch
7.0.20 (SOAP) As of R7
As of patch
7.0.30
All usages
Low*/
High
High
Low*/
Medium
High
All usages •Limited number of
counterparts
•Static header only
Low
Medium
Messenger on
WebPlatform
Low
Occasional
file transfer
Low
XML v2
* With Integrator FileAct package
Alliance
Interface
Entry /
Access Access Access Access
Entry /
Access
More information
• Alliance Access related documentation
– System Configuration Recommendations and Guidelines on UHB
(KB Tip 2156213)
– Benchmark information
• On Alliance Access area on SWIFT.com, in Additional
Information section:
– Alliance Interfaces FileAct support in SWIFTNet Release 7.0
– Direct FileAct Information Paper
Presentation title – dd month yyyy – Confidentiality: xxx 24
System Recommendations – Benchmark
CPU Usage - High-end Systems
Presentation title – dd month yyyy – Confidentiality: xxx 25
0.0
10.0
20.0
30.0
40.0
50.0
MQHA SOAP MQHA SOAP
Full Mode Mixed Mode
20KB x 5000 files
50KB x 2000 files
1MB x 100 files
0.0
10.0
20.0
30.0
40.0
50.0
MQHA SOAP MQHA SOAP
Full Mode Mixed Mode
20KB x 5000 files
50KB x 2000 files
1MB x 100 files
0.0
10.0
20.0
30.0
40.0
50.0
MQHA SOAP MQHA SOAP
Full Mode Mixed Mode
20KB x 5000 files
50KB x 2000 files
1MB x 100 files
AIX Power 7
Sun M4000
Windows X7350
System Recommendations – Benchmark
CPU Usage - High-end Systems
Presentation title – dd month yyyy – Confidentiality: xxx 26
AIX Power 7
Sun M3000
Windows E5540
0.0
10.0
20.0
30.0
40.0
50.0
MQHA Full Mode
20KB x 5000 files
50KB x 2000 files
1MB x 100 files
0.0
10.0
20.0
30.0
40.0
50.0
MQHA Full Mode
20KB x 5000 files
50KB x 2000 files
1MB x 100 files
0.0
10.0
20.0
30.0
40.0
50.0
MQHA Full Mode
20KB x 5000 files
50KB x 2000 files
1MB x 100 files
Presentation title – dd month yyyy – Confidentiality: xxx 27
Thank you
top related