The SWIFTReady Financial Enterprise Application Integration label is venerable in that it goes back as far as 2000....
It is a standard overseen by the Society for the Worldwide Interbank Financial Telecommunication group (which itself goes back to 1973), for the purpose of certifying applications and middleware products. SWIFT messaging systems define interfaces, particularly for financial application integration. The Year 2010 saw the advent of a new version of the SWIFTReady Financial Enterprise Application Integration label. An SDK is available to help development teams get up to speed with the Financial EAI.
The major change in the 2010 label for SWIFTReady Financial Enterprise Application Integration is that the choice is now left to integrate either with Alliance Access or with Alliance Gateway. That means that an EAI may include its own messaging interface. For its part, Alliance Access provides a messaging framework for data transfer between business applications, while Alliance Gateway acts as a communications interface that isolates application and messaging components from network level concerns.
There is a series of dimensions that SWIFT EAI is dedicated to covering. Among these dimensions are protocols, connectivity, reference data, processing, validation and standards. Embedded SOAP, for example is a supported standard, as is Automated File Transfer (AFT) adapter for batched processing.
Messaging protocols supported include FileAct RT, FIN, and others. Processing techniques supported include routing, logging, archiving, exception handling, MT-MX translation, transaction management and BPM. Message validation is done against messaging protocols, SWIFT standards and "market practices." SWIFT EAI offers support for the Financial products Mark-up Language (FpML).
Now available is SWIFT's Standards Developer Kit R1 which includes a repository and a model that defines the structure of messages for SWIFT EAI. A schema library within the SDK includes XML schema definitions for MT messages and software that shows how MT format messages can be converted to MT XML, and vice versa.