This release of Rhapsody includes a number of fixes and improvements that introduce functional changes with respect to previous releases:
JRE Updates
Oracle recently introduced licensing changes that now require royalties for the use of the latest versions of their Java Runtime Environment (JRE). Therefore, Rhapsody 6.5 has adopted the latest Java 8 AdoptOpenJDK JREs for the 64-bit engines on Windows, Linux and Solaris, and Rhapsody IDE on Windows. These JREs can be used royalty-free. The 32-bit engines on Windows and Linux have been updated to use the latest royalty-free versions of Oracle's Java 8 JREs. The JREs used for the engines on AIX and HP-UX have been updated to the latest Java 8 JRE from IBM and HP, respectively, which are also royalty-free. Refer to JRE Versions for details.
Rhapsody 6.4.2 and earlier versions of Rhapsody use Oracle's JREs which continue to be royalty-free.
Disabled Ciphers Suites
The TLS anon, DES, RC4, and SSL algorithms and protocols, as well as the cipher suites which use them, have been disabled in the latest releases of Java 8 JREs because of vulnerabilities. They have therefore also been disabled in Rhapsody 6.5. If absolutely necessary, you can re-enable them. Refer to Enabling Disabled Cipher Suites for details.
Cipher suites in the rhapsody.properties file are not updated during an upgrade. Therefore, testing components which use SSL is especially important after an upgrade.
Replacement of DICOM Filters
The DICOM to XML / XML to DICOM and DICOM JPEG Extraction filters have been discontinued and replaced by the DICOM XML Converter and DICOM JPEG Converter filters, respectively. If you want to use an RLC that contains the discontinued filters, you must replace them with their new counterparts. Users should contact Rhapsody Support to assist with the migration.
Installation Directory Changes
The default installation directories for Rhapsody applications have changed:
| Rhapsody Component | From... | To... |
|---|---|---|
| Engine (Windows) |
|
|
C:\Program Files (x86)\Orion Health\Rhapsody |
C:\Program Files (x86)\Rhapsody\Rhapsody Engine 6 |
|
| Engine (*nix) |
|
|
| Rhapsody IDE | C:\Program Files (x86)\Orion Health\Rhapsody IDE 6 |
C:\Program Files (x86)\Rhapsody\Rhapsody IDE 6 |
| Rhapsody Messaging Toolkit (formerly Symphonia) | C:\Program Files (x86)\Orion Health\Symphonia |
C:\Program Files (x86)\Rhapsody\RMT |
Rhapsody Dashboard (Windows) |
|
|
| Rhapsody Dashboard (*nix) | /orionhealth/dashboard |
|
Changes to the internal XSD representation in Map Designer
As of Rhapsody 6.5.0, the way that XSD schemas are represented internally in an MDF file has been slightly altered to enable Map Designer to load XSD schemas with recurring elements. Existing mappings which use XSD schemas as input or output definitions may fail to compile after these definitions are reloaded. The compilation errors can be resolved by modifying the affected submap definitions to use the new LocalComplex datatype IDs referred to in the error details.
Mappings compiled in earlier versions of Rhapsody will continue to run in Rhapsody 6.5.0 without issue.
Rhapsody IDE Menu Changes
Rhapsody IDE menus have been reorganized to make the user interface more intuitive. In particular:
- The View menu items have been reordered.
- The User Manager has been moved to the Rhapsody menu.
- The Management Console has been moved to the Tools menu.
- The Managers Menu accessible from the toolbar ordering has changed for consistency.
- The Output panel has been renamed the Information panel.
Advanced Routing
Rhapsody 6.5 introduces Advanced Routing for continued routing on failure for communication points. Output communication points placed on the input side of routes have an error output connector for configuring continued routing on failure.
Continued routing on failure is not supported on versions of Rhapsody prior to Rhapsody 6.5. You can still load RLCs, which contain communication points configured to use continued routing, into older engines, but the continued routing functionality will be stripped out in the process.
Removal of the User Feedback Form
The Orion Health-administered User Feedback Form in the Management Console has been removed in Rhapsody 6.5. You may now provide feedback directly to your Rhapsody Account Manager. Requests for product enhancements can be submitted via Rhapsody Support.
STDOUT and STDERR Redirection
Rhapsody no longer redirects STDOUT and STDERR to the Rhapsody logs. Logging from third-party or RDK components that log to STDOUT and STDERR is now redirected to the Wrapper log.
New Access Rights
Refer to New Access Rights for details.