In order to continue to provide quality software and solutions with maximum customer value, CA Technologies often has to make challenging investment decisions.
Given the strategic focus on CA Performance Management as our Network Performance and Diagnostics solution, we have decided to DISCONTINUE support for the eHealth Data Source within CAPC.
We have dropped official support for the eHealth CAPC Data Source as of our 3.0 release. The functionality will remain in the product “as-is” until the CAPM 3.1 release at which time we will no longer provide a product option for eHealth Data Sources within CAPC.
We strongly urge our eHealth customers to contact their Account Representatives to evaluate CA Performance Management against your business needs.
A new CA Communities site has launched focused around CA Performance Management upgrades (both from eHealth and older versions of CAPM) to aid in evaluation and planning of migrations and upgrades. You can view those resources here:
As always we appreciate your continued support and understanding and look forward to continuing to work with you to ensure you receive the most value out of your investments in CA Technologies.
If a customer has ehealth, they will have to with CAPM 2.8 for now, if they wish to be supported.
Customer should look to move from ehealth to PM/DA as soon as possible, if customer wish to move to r3.0 and above.
CA didn't remove the eHealth datasource type from CAPM 3.0 for customers who upgrade and are currently using ehealth. It should still sync with the existing ehealth DS.
CA will not be providing support for new or existing PM customers with ehealth, if there are any issues for CAPM 3.0.
CA has updated the following page to make it clear ehealth is no longer supported in CAPM 3.0.
Performance Center Data Source Compatibility - CA Performance Management - 3.0 - CA Technologies Documentation
The various ehealth pages in the docs talk about ehealth being deprecated entirely in future releases. We are allowing them to still run it in r3.0, but will be removed as a Datasource in CAPM 3.1.