Alliance Access Integration SOAP Host Adaptor

of 25

Please download to get full document.

View again

All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
PDF
25 pages
1 downs
23 views
Share
Description
SWIFT Certified Applications Alliance Access Integration SOAP Host Adaptor Technical Qualification Test 2017 This document lists the tests for application providers that integrate their back-office application
Transcript
SWIFT Certified Applications Alliance Access Integration SOAP Host Adaptor Technical Qualification Test 2017 This document lists the tests for application providers that integrate their back-office application or middleware with Alliance Access using SOAP Host Adaptor and that are looking at qualifying against the SWIFTCertified Application. Version 1.1 February 2017 Legal Notices Copyright SWIFT All rights reserved. You may copy this publication within your organisation. Any such copy must include these legal notices. Disclaimer SWIFT supplies this publication for information purposes only. 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 version. Trademarks SWIFT is the trade name of S.W.I.F.T. SCRL. The following are registered trademarks of SWIFT: SWIFT, the SWIFT logo, Sibos, SWIFT, SWIFTReady and Accord. Other product, service, or company names in this publication are trade names, trademarks, or registered trademarks of their respective owners. 2 / 25Alliance Access Integration SOAPHA Table of Contents 1 Preface Purpose Audience SWIFT Certified Application program Related Documents Introduction SWIFT Certified Application Validation Alliance Access configuration Alliance Access Message Partner configuration Exchanging messages using Message Partner Wipro Testing Service SOAPHA Test preparation Reconciliation of Delivery Notification Transmission Notification Message Flow SOAP Primitives SWIFT Certified Programme SOAPHA testing Test Evidence Annexure Sample Message Partner Configuration Message Flow Input MT Message in XML v2 format ACK for MT message in XML v2 format Output MT message in XML v2 format Delivery Notification of MT Message in XML v2 format Input MX message in XML v2 format ACK for MX Message in XML v2 format Output of MX Message in XML v Delivery Notification of MX Message in XML v / 25Alliance Access Integration SOAPHA 1 Preface 1.1 Purpose This document describes the test scenarios that a financial application has to pass to be compliant with Alliance Access using SOAP Host Adaptor (SOAPHA). The purpose of the SOAPHA qualification is to verify the capacity of an application to correctly integrate with SWIFTNet via Alliance Access SOAP Host Adapter. 1.2 Audience The target audience for this document is both partners considering the certification of a product, and SWIFT users that look after an overview of the SWIFT Certified Applications contents. The audience should be familiar with SWIFT portfolio from a technical and a business perspective. 1.3 SWIFT Certified Application program The SWIFT Certified Application programme covers the entire financial application chain, from Trade, Treasury and Payment, to Corporate and Securities segments. Each SWIFT Certified Application defines a set of criteria, which are reviewed every year to ensure that the software remains aligned with the financial market evolution and with customer needs. These criteria are designed to reflect the capability of a financial application to provide message processing automation in a SWIFT context, and to support straight through processing (STP) in order to increase customer value, limit customisation needs and cost, and reduce time to market. 1.4 Related Documents The following documents can be found over swift.com: Alliance Access 7.2 final release overview Alliance access system management guide sam_aaccess_headers 4 / 25Alliance Access Integration SOAPHA 2 Introduction SOAP, originally defined as Simple Object Access Protocol, is a protocol specification for exchanging structured information over HTTPS. The SOAP connection method enables the exchange of MT and MX using XML V2orFileAct messages between Alliance Access and back-office applications through the SOAP protocol. Message Partner and routing rules have to be configured in alliance access for SOAPHA. 2.1 SWIFT Certified Application Validation Support of SOAPHA is one of the qualification criteria for granting the SWIFT Certified Application Label to a financial application. The Partners who deployed the SWIFT Alliance connectivity to SWIFT ITB can perform these tests independently. Test environment configurations described in section 3. As an alternative, Wipro Testing Services offers a test service for connecting to SWIFT ITB. Using this service, the Partner can connect to SWIFT ITB. The testing service allows testing application connectivity with Alliance Access AFT, MQHA and SOAPHA. Please go to section 4, if you wish to use this service. 5 / 25Alliance Access Integration SOAPHA 3 Alliance Access configuration This set-up is applicable for Partners who have deployed an ITB environment and connect to Alliance Access from their premises. 3.1 Alliance Access To prepare for the tests, the Alliance Access system must be installed and configured at Partner premises. The following configuration is required for communicating through SOAPHA: Alliance Access must be upgraded to release 7.2. Please note that Alliance access 7.2 can be used for MT and MX using XML V2. FileAct with SOAPHA will work with SAA 7.2 versions. Additional licence 14:SOAP ADAPTER is required for SOAP For exchanging XML messages 19:AI FILE XML, license is needed It is necessary to get acquainted with the Alliance Access - System Management Guide and alliance 7.2 release overview to further configure the interface for test purpose. The Application Interface module of Alliance Access provides all the functions necessary to manage Message Partner profiles. Using Application Interface, the Partner needs to set up the connection profiles that are used by Alliance Access to connect with external message partners. The Application Interface allows exchanging messages with external back-office systems or Message Partners . 3.2 Message Partner configuration The SOAPHA communication session is set up and controlled with a dedicated Message Partner configuration in Alliance Access. Using the procedure described in the Alliance Access System Management Guide SOAP Connection Method, create a Message Partner. Specify the connection method as SOAP Specify the direction of message transfer Configure other parameters For detailed procedure for creating message partner profile for SOAPHA, please refer to the procedure described in the Alliance Access System Management Guide Managing Message Partner Profiles A screenshot of sample Message Partner configuration is provided in section Exchanging messages using Message Partner The SOAPHA supports MT, MX and FileAct messages. It will support only the XMLv2 data format. The messages being sent must be the message types supported by the partner application. All messages entering Alliance through the Application Interface are queued at one single point of entry _AI_from_APPLI (AI Inbound Queue), before being routed onwards The successfully processed messages will be stored by Alliance Access in the _SI_to_SWIFTNetQueue SWIFT Network returns Notification messages for technical reconciliation and response messages, since the test messages were used for self transfers, meaning, the sender and receiver BIC are the same The application must download the Network notifications and messages sent in Output from SWIFT direction 6 / 25Alliance Access Integration SOAPHA 4 Wipro Testing Service The vendor needs to liaise with Wipro to enrol into Wipro Testing Services and test the exchange of messages through this service The vendor application should be able to connect and exchange messages using SOAP protocol The vendor will be provided with a PIC (Partner ID Code) This PIC must be used in the sender and receiver block for exchanging messages over SWIFT ITB The Vendor needs to configure the SOAP Configuration parameter details provided by Wipro in the application The connectivity is very similar to connection to own environment, except for the reason that this connectivity is established outside Vendor s internal network environment and hence necessary permission needs to be obtained upfront from Vendor s IT Security team for using Port 48200over internet. Once the connectivity is established, the vendor can exchange the messages. SWIFT Network returns Notification messages for technical reconciliation and response messages, since the test messages were used for self transfers, meaning, the sender and receiver BIC are the same. The application must download the Network notifications and messages sent in Output from SWIFT direction. 7 / 25Alliance Access Integration SOAPHA 5 SOAPHA Test preparation SOAPHA supports the exchange of messages in the following data formats: XML version 2 (MX and MT messages, and files for FileAct service) SOAPHA supports XML version 2 ONLY. The Partner must use XML version 2 and latest revisions as described is Alliance Access System Guide. For more information about these formats, see the Alliance Access System Management Guide Message Formats Used in AI . Sample messages for MT and MX are provided in section 7.Please refer to sam_aaccess_headers.pdf document for messages samples exchanged with Alliance Access, in scope of the SWIFT solution. 5.1 Reconciliation of Delivery Notification When the messages are sent to Alliance Access, the application can optionally request for a delivery notification. This will result in Alliance Access receiving a message about the message delivery, which can be reconciled with the original message. The Partner must demonstrate the capability of their application to process the Delivery Notification Message and to reconcile it with the original message. A sample Delivery Notification message is provided in section Transmission Notification A transmission notification is a message representing the result of transmission to SWIFT network. SWIFT performs full syntax and semantic checks before it returns an acknowledgement (ACK). Other checks, such as validity of the sender and the receiver, are also performed. These checks can cause a message to be rejected and a negative acknowledgement (NAK) is returned in response. The Partner must demonstrate their application capability to process the Transmission Notification Message and reconcile with the original message. 5.3 Message Flow Alliance Access controls the interactive exchange of SOAP messages between the back-office Applications and Alliance Access using an additional SWIFT-defined protocol on top of the SOAP protocol. This protocol provides a set of primitives to manage the message exchange Sessions, to guarantee and ensure unique delivery of messages SOAP Primitives The following SOAP primitives are used in SOAP messages: Open: open a session Close: close a session Put: send a message to Alliance Access GetAck: request Alliance Access to send a message that is waiting delivery to the back office Application, and optionally, acknowledge a message received from Alliance Access Ack: acknowledge a message received from Alliance: Please refer the SAA system management guide for more information about SOAP messages. 8 / 25Alliance Access Integration SOAPHA 6 SWIFT Certified Programme SOAPHA testing To be qualified as SOAPHA compliant, Partners need to send MT,MX or FileAct messages (depending on the label category), and act upon received MT, MX or FileAct messages including Ack/Nack and delivery notifications. 1. The Partner application vendor prepares the MT / MX/FileAct message types as required for the SWIFT Certified programme. Partners having their own ITB environment must use their PIC in the sender and receiver fields of the message. The Partner using Wipro Testing Services for connecting to ITB must use the PIC provided by Wipro in the sender and receiver field of the message. 2. For individual label requirements, the vendor application must exchange application supported SWIFT Messages. Vendor should refer to label specific technical validation guide for the in-scope SWIFT MT, MX or FileAct Messages. 3. The partner application must include delivery notification instructions while generating the test messages. The partner application must receive the delivery notification information and reconcile with the original message sent to Alliance Access. 4. Alliance Access must be configured to return Alliance Access information. When receiving messages the partner application must accept this information from Alliance Access Info. When using Wipro Testing Services for connecting to ITB, the message format and acknowledgement format for receiving Alliance Access information must be agreed in advance. 5. The acknowledgement of transmission is sent through transmission notification message the partner application needs to capture the ACK and NAK received back from SWIFT and reconciled in the partner application. Evidences of reconciliation mechanism (screen dump, event log, dataset extract) will be handled back to SWIFT Qualification service provider. 6.1 Test Evidence The Partner should extract the following evidences covering the testing period and send them via to the Validation Service provider for Technical Validation of SOAPHA connectivity test. Partners with own ITB connectivity Alliance Access Event Journal report Message File report Samples of XMLv2 files (MT, MX,FileAct) Screenshots /Configuration details / Log File / Dataset extract / Reports generated from the Partner application evidencing the test execution through Partner application and the reconciliation mechanism against delivery notification and transmission notification for ACK and NAK Partners testing through Wipro Testing Service Alliance Access Event Journal report and Message File report will be generated by Wipro The Partner has to provide the exchanged samples of XMLv2 files (MT, MX,FileAct) Screenshots / Configuration details / Log File / Dataset extract / Reports generated from the Partner application evidencing the test execution through Partner application and the reconciliation mechanism against delivery notification and transmission notification for ACK and NAK 9 / 25Alliance Access Integration SOAPHA 7 Annexure 7.1 Sample Message Partner Configuration Direction: From Message Partner to Alliance Access 1. For MT, MX and FileAct Full mode 10 / 25Alliance Access Integration SOAPHA 2. For MT, MX and FileAct Mixed mode 11 / 25Alliance Access Integration SOAPHA 3. Reception Tab(for full and mixed mode) 12 / 25Alliance Access Integration SOAPHA Direction: From Alliance Access to Message Partner 1. For MT, MX and FileAct Full mode 13 / 25Alliance Access Integration SOAPHA 2. For MT, MX and FileAct Mixed mode 14 / 25Alliance Access Integration SOAPHA 3. Emission Tab(for full and mixed mode) 7.2 Message Flow The message is sent to the Alliance access from back office application in Put request and messages received from Alliance access to back office application in GetAck response. Message flow of SOAPHA is given in Appendix F SOAP Connection Method of SAA System Management guide Input MT Message in XML v2 format soapenv:envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/ xmlns:urn= urn:swift:saa:xsd:soapha soapenv:header urn:saaheader Id= SAAHeader urn:sessiontoken bd96d62e-c005-4ec6-b b739 /urn:sessiontoken urn:sequencenumber 9 /urn:sequencenumber urn:expirydatetime t20:33:51.373 /urn:expirydatetime /urn:saaheader /soapenv:header soapenv:body urn:put DataPDU xmlns= urn:swift:saa:xsd:saa.2.0 Revision 2.0.7 /Revision Header Message 15 / 25Alliance Access Integration SOAPHA SenderReference REF /SenderReference MessageIdentifier fin.540 /MessageIdentifier Format MT /Format Sender BIC12 SPXAINJJAXXX /BIC12 FullName X1 SPXAINJJXXX /X1 /FullName /Sender Receiver BIC12 SPXAINJJXXXX /BIC12 FullName X1 SPXAINJJXXX /X1 /FullName /Receiver InterfaceInfo UserReference REF /UserReference /InterfaceInfo NetworkInfo IsNotificationRequested true /IsNotificationRequested /NetworkInfo SecurityInfo FINSecurityInfo/ /SecurityInfo /Message /Header Body DQo6MTZSOkdFTkwNCjoyMEM6OlNFTUUvLzExLTU0MC1TUi0yMDEwDQo6MjNHOk5FV00NCjoxNlI6T ElOSw0KOjIwQzo6UE9PTC8vUkVGRVJFTkNFDQo6MzZCOjpUVVJOLy9GQU1ULzEwMDAwMDAsDQo6MTZTOkxJ TksNCjoxNlM6R0VOTA0KOjE2UjpUUkFEREVUDQo6OThBOjpTRVRULy8yMDEwMTEyMA0KOjM1QjpJU0lOIFV TMDAwMDEyMzQ1Ng0KQUJDRCANCjoxNlI6RklBDQo6OTRCOjpQTElTL1hOWVMvRVhDSC9ORVdZT1JLIFNUT0 NDIEVYQ0hBTkdFDQo6MjJGOjpNSUNPLy9BMDEyDQo6OThBOjpNQVRVLy8yMDEwMTEyMA0KOjE2UzpGSUENC joymky6oljqt1ivl0rfrlincjoxnlm6vfjbrerfva0koje2ujpgsufddqo6mzzcojptrvruly9gqu1ulzew MDAwMCwNCjo5N0E6OlNBRkUvLzEyMzQ1Ng0KOjE2UzpGSUFDDQo6MTZSOlNFVERFVA0KOjIyRjo6U1RDTy8 vtlbbug0kojiyrjo6u0vuui8vvfvstg0koje2ujptrvrqulrzdqo6otvqojpcvvlsly9tv0hrqkvcqg0koj E2UzpTRVRQUlRZDQo6MTZSOlNFVFBSVFkNCjo5NVA6OlNFTEwvL1NXSFFCRUJCDQo6OTdBOjpTQUZFLy8xM jm0ntyncjoxnlm6u0vuufjuwq0koje2ujptrvrqulrzdqo6otvqojperufhly9tv0hrqkvcqg0koje2uzpt RVRQUlRZDQo6MTZSOlNFVFBSVFkNCjo5NUM6OlBTRVQvL1VTDQo6MTZTOlNFVFBSVFkNCjoxNlM6U0VUREV U /Body LAU xmlns= urn:swift:saa:xsd:saa.2.0 signature xmlns= http://www.w3.org/ 2000/09/xmldsig# SignedInfo CanonicalizationMethod Algorithm= http:// / SignatureMethod Algorithm= http:// / Reference URI= Transforms Transform Algorithm= http://www.w3.org/2000/09/ xmldsig#enveloped-signature / /Transforms DigestMethod Algorithm= http:// / DigestValue Y7oScHnYOUQvni/TSzZbDec+HR +mwifh149gxpwj1ws= /digestvalue /reference /signedinfo signaturevalue 6ynf/ FcwbPsHrtlj3h2agJigdnvpbO6hOzKSRGzqkw0= /SignatureValue /Signature /LAU /DataPDU /urn:put /soapenv:body /soapenv:envelope ACK for MT message in XML v2 format S:Envelope xmlns:s= http://schemas.xmlsoap.org/soap/envelope/ S:Header SAAHeader Id= xmlns= urn:swift:saa:xsd:soapha SessionToken 4fd95b3e-6a30-4cc3-9de6-919fbebc /SessionToken SequenceNumber 5 /SequenceNumber /SAAHeader /S:Header S:Body GetAckResponse xmlns= urn:swift:saa:xsd:soapha Saa:DataPDU xmlns:swsec= urn:swift:snl:ns.swsec xmlns:swint= urn:swift:snl:ns.swint xmlns:swgbl= urn:swift:snl:ns.swgbl xmlns:sw= urn:swift:snl:ns.sw xmlns:saa= urn:swift:saa:xsd:saa.2.0 Saa:Revision 2.0.7 /Saa:Revision Saa:Header 16 / 25Alliance Access Integration SOAPHA Saa:TransmissionReport Saa:SenderReference REF /Saa:SenderReference Saa:ReconciliationInfo 120177SPXAINJJAXXX /Saa:ReconciliationInfo Saa:NetworkDeliveryStatus NetworkAcked /Saa:NetworkDeliveryStatus Saa:OriginalInstanceAddressee Saa:X1 SPXAINJJXXX /Saa:X1 /Saa:OriginalInstanceAddressee Saa:ReportingApplication FINInterface /Saa:ReportingApplication Saa:NetworkInfo Saa:Priority Normal /Saa:Priority Saa:IsPossibleDuplicate false /Saa:IsPossibleDuplicate Saa:IsNotificationRequested true /Saa:IsNotificationRequested Saa:Service swift.fin /Saa:Service Saa:Network FIN /Saa:Network Saa:SessionNr 0132 /Saa:SessionNr Saa:SeqNr 174569 /Saa:SeqNr Saa:FINNetworkInfo Saa:MessageSyntaxVersion 1105 /Saa:MessageSyntaxVersion /Saa:FINNetworkInfo /Saa:NetworkInfo Saa:Interventions Saa:Intervention Saa:IntvCategory TransmissionReport /Saa:IntvCategory Saa:CreationTime /Saa:CreationTime Saa:OperatorOrigin SYSTEM /Saa:OperatorOrigin Saa:Contents {1:F21SPXAINJJAXXX }{4:{177: }{451:0}{108:REF }} /Saa:Contents /Saa:Intervention /Saa:Interventions Saa:IsRelatedInstanceOriginal true /Saa:IsRelatedInstanceOriginal Saa:MessageCreator ApplicationInterface /Saa:MessageCreator Saa:IsMessageModified false /Saa:IsMessageModified Saa:MessageFields NoOriginal /Saa:MessageFields /Saa:TransmissionReport /Saa:Header /Saa:DataPDU /GetAckResponse /S:Body /S:Envelope Output MT message in XML v2 format S:Envelope xmlns:s= http://schemas.xmlsoap.org/soap/envelope/ S:Header SAAHeader Id= xmlns= urn:swift:saa:xsd:soapha SessionToken 4fd95b3e-6a30-4cc3-9de6-919fbebc /SessionToken SequenceNumber 6 /SequenceNumber /SAAHeader /S:Header S:Body GetAckResponse xmln
Related Search
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks