Migrating Electronic Signature
An Axway Financial Exchange implementation is composed of two principal sets of elements:
When you migrate from Financial Exchange version 2.4, 2.5.1 or 2.6.1 to version 2.9.0 you must update both of these sets of elements.
The EBICS implementation of FEX is composed of several parts:
In addition, the EBICS Server may be used in conjunction with the PassPort product.
In order to properly upgrade FEX for EBICS to version 2.9.0, you must upgrade all of these elements.
EBICS Client is now fully integrated into Electronic Signature. This new version is able to handle EBICS T as well as EBICS TS protocols. You can migrate from EBICS Client to Electronic Signature 2.9.
You can migrate from Electronic Signature 2.7 to Electronic Signature 2.9.
In Integrator, the Business-Document object serves as a container for message content. When the format of the standardized message changes, the structure of the Business-Document must also change.
Some of the standard formats of messages that are exchanged between financial exchange partners have changed between release versions of FEX. In many cases, new messages have been added to repositories to respond to evolutions of standards and services. For this reason you must update message repositories to newer versions.
For example, you may want to update a library from a previous version.
View Business-Document repository update procedure
In Integrator, Integration-Processes describe sequences of message-processing events on an Integration Server.
For FEX you must migrate the Integration-Process which defines processing for the validation of messages and recycling of invalid messages.
For message recycling for Financial Exchange, Integrator requires a set of Integration-Processes / Integration-Tasks / Channels for each category of SWIFTNet message that you expect to recycle.
From Financial Exchange 2.2 onwards, message recycling operates dynamically:
The FEX installation package includes Custom-Functions that are used by Integrator when parsing messages to Business-Documents to check messages for compliance with SWIFT Network Validation Rules.
The Custom-Functions have been modified since the last FEX version and no longer use the same libraries. For this reason you must upgrade the Custom-Functions before using them with FEX Business-Documents.
View Custom-Function migration procedure
During the message recycling process, SWIFTNet Portal requires a set of descriptions of the structure of each message type it will recycle. These repositories must be updated to take into account any modifications in the standards definitions of message structures.
To update the document type repositories on SWIFTNet Portal, refer to the SWIFTNet Portal Migration Guide.
From version 2.4, the TARGET2 SSP supports concurrent versions of schema files supplied by the following two Cash Management standards releases: CAMT version 3.0 – former version CAMT version 4.0 – updated November 2008 release version.
For full Axway Financial Exchange support of TARGET2 V2.4 (CAMT V3.0 and CAMT V4.0 messages), you must install FEX for TARGET2 on Gateway.
This service pack is delivered in the FEX installation package. It is labeled:
qt2_1.0.3_[machine_type].zip
This service pack is available for the following machine types:
All service packs are also available from the Axway Support website.