Unsolved
This post is more than 5 years old
2 Posts
0
852
Open Questions in regard to "change to XAM SDK support"
I like to open a new discussion in regard to the following announcement made by EMC:
------
Change to XAM SDK support
Dear valued EMC customer / partner,
The EMC Centera team has recently restricted access to the XAM API as its adoption in the market has not materialized. Therefore, the Centera SDK API is the preferred method for application integrations with EMC Centera. If you are a new customer / partner or an existing Centera SDK API user, EMC supports using the SDK API for application integrations. If you are an existing XAM API user, EMC will continue to support the existing XAM API integration (XAM 1.0p3) but will only be providing new XAM API releases on a break / fix basis. In addition, EMC will not be extending XAM API support into our Big Data and Cloud family of products.
Thank you for your consideration.
-----
As an ISV we would be advised by EMC a couple of years ago to replace the from centera SDK to XAM API. The exchange results in a lot of workload and pain on emc's side, on our side and on customer side. Now as the situation is more or less stable we would be advised turn the wheel back to previous situation.
This announcement leads us at least to the following open questions:
1. Is EMC really knowing what such a decission causes on the ISV side as well as on the customer side?
2. The data written to centera via XAM are in a different format than as written by SDK.
a) Will there be a migration path provided by EMC for the data written by XAM API?
b) Will the SDK be enhanced by a backward support for data written by XAM API
3. What means "providing new XAM API releases on a break / fix basis" exactly?
4. What e.g. about further plattform support for XAM API?
5 How long will EMC continue support of the existing XAM API Integration (XAM 1.0p3)?
I am looking forward getting answers to those questions by EMC.