We are delivering an APM project for a large CA customer.
The customer plans to use APM Web Services to interface around 30 tiers applications with APM.
Those applications will call the standard APM Web Services in order to read, update and create assets and relationships.
Each time a change is made within the APM application as defined in TEC1872387 (https://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.TEC1872387.html) a new download of the WSDL is required. The former URL is invalidated and a new URL become valid as soon as it is downloaded.
Due to this constraint, we believe that APM Web Services are not usable in a production environment in our case where around 30 client applications or even more will be impacted each time. This technical constraint is a serious challenge for the project.
Can you redesign the APM Web Service in order to have no impact on existing clients each time a change is made within the application?
It would be a great idea to have APM Web Services that never break existing code and eluminate the need to upgrade existing code.