The following plan
outlines what we consider an acceptable process that will allow you to better
manage your upgrades, as well it will allow Amadeus to introduce and to update
any IATA mandates on a timely manner.
To move forward with new APIv2 product deliveries, you need to take into account two types of deprecations:
Proxy version deprecation
Proxy 43, making the APIv2 product PCI-DSS compliant is the last proxy released. On the last ten (10) proxies will be continued to be supported until there is the full APIv2 decommissioning (to be announced). The last 10-proxies are supported with following conditions:
- For proxies earlier than proxy 34, in the event of errorenous behaviour, first an upgrade to the latest proxy is required. If the error persists, potential patches will be provided for proxy 43 (in case the APIv2 product is the cause).
For proxies later than 34, in the event of errorenous behaviour, potential patches will be provided for proxy 43 (in case the APIv2 product is the cause). Users will be asked to upgrade to proxy 43 in order to benefit from the provided solution.
Proxy users can at all times decide to upgrade to the latest proxy. For this please follow the normal ordering procedures in place.
List of impacted function calls:
|Removed in Proxy#
||Rejected in Test
||Rejected in Production
|Proxy of Q4 2007||Jan|
Starting with Proxy-32, which will be the first
Proxy to be relased in 2006, the traditional CAI_openConversationByCorporateID()
and CAI_createConversationFactory functions will no longer exist.
If you want to benefit from the new functionalities introduced with the Proxy-32 and beyond, you have to migrate to