CA eHealth r6.3.3 GA Announcement
October 14, 2016
CA Technologies is pleased to announce the General Availability of CA eHealth® r6.3.3. Release 6.3.3 is an Update to eHealth r6.3.2.x which includes all solutions delivered in previous eHealth versions, as well as an updated database. Release 6.3.3 provides users with added security and more detailed and accurate performance management of their networked devices. Please refer to the bundled “ReadMe” document for detailed migration paths, installation steps, and device certifications in CA eHealth r6.3.3.
Updates in CA eHealth r6.3.3
The mission of CA eHealth is to update and enhance the device monitoring capabilities of the eHealth product for broader coverage and ease of IT Management, end to end. CA eHealth r6.3.3 contains the following product updates:
Updated Oracle Database
In keeping with CA Technologies’ commitment to support the needs of our customers who require updated database security and supportability, we have updated the embedded eHealth database to Oracle 12c. Specifically, updating to CA eHealth r6.3.3 requires an eHealth database update to Oracle Database version 126.96.36.199.
Please refer to the CA eHealth 6.3.3 ReadMe for more information about the Oracle update.
Product Integration and Third-Party Component Updates
CA eHealth 6.3.3 includes updated support for the following software product versions:
- CA EEM 12.51 CR04
- CAPKI 5.1.0
See the CA eHealth ReadMe for a complete list of updates.
Key Device Certifications
Additional valuable content in eHealth 6.3.3 are new and enhanced SNMP device certifications. CA eHealth r6.3.3 includes new support for over 50 devices from numerous major network vendors such as Cisco. The goal of the eHealth product team is to deliver significant mission-critical certifications in every release and maintenance kit. Please refer the ReadMe for the full list of certifications in r6.3.3.
Where to obtain CA eHealth r6.3.3
The CA eHealth r6.3.3 (the self-extracting install files for each of the supported operating systems) and associated ReadMe documents can be obtained via electronic download from our “Download Center” area on the CA Support site (http://support.ca.com). Please fully review the ReadMe document, including the Migration Path and Install Instructions sections, before installing. It is important to note that a full backup of the eHealth database should be completed prior to patching, upgrading or updating any server system to r6.3.3, as a best practice.
How to Update, Upgrade, or Migrate to CA eHealth r6.3.3
Migration Path Information
As with previous eHealth Service Packs, you can install r.6.3.3 directly over any 6.3.2 revision in order to complete the update to r6.3.3. In order to determine your best migration path from an earlier eHealth revision, use the information in the migration table in the ReadMe which describes update, upgrade, and migration paths from earlier CA eHealth versions and OS versions.
Platform Support Information
CA eHealth r6.3.3 has been certified to fully operate on the following OS platform versions:
- Red Hat Enterprise Linux (RHEL) 7.0 and higher (7.x support started in eHealth r188.8.131.52.)
- Red Hat Enterprise Linux (RHEL) 6.0 and higher (6.x support started in eHealth r6.3.2.05.)
- Red Hat Enterprise Linux (RHEL) 5.8 and higher
- Solaris 5.10 (64-bit)
- Windows 2012 R2 (64-bit)
- Windows 2008 R2 (64-bit)
Maintenance Releases such as CA eHealth r6.3.3 are recommended for all eHealth installations to ensure users are able to take advantage of the latest device certifications and software updates. It is strongly recommended that you plan to keep current with regard to release versions across your eHealth installations in order to get the most from the product’s monitoring capabilities, as well as the latest security and other enhancements. Should you need any assistance in understanding the various eHealth migration paths, or have questions about installing this maintenance release, our CA eHealth Technical Support team can help. Please call 800-CALL-CAI to open a ticket with your local CA Support team.