Before you upgrade, ensure you review the information in this section and determine whether it is applicable to your configuration:

Upgrade Caveat

 Upgrading from...

Description
Disabled cipher suites Versions prior to Rhapsody 6.5.0. Cipher suites using the TLS anon, DES, RC4, and SSL algorithms and protocols have been disabled in Rhapsody 6.5. Refer to Configuring Cipher Suites for a list of currently supported cipher suites. Ensure components in your configurations are only using supported cipher suites. If you cannot avoid using disabled cipher suites, then you can re-enable them through the java.security and rhapsody.properties files. Refer to Enabling Disabled Cipher Suites for details.
Updating SSL cipher suites Versions prior to Rhapsody 6.5.0.

The list of SSL cipher suites in the rhapsody.properties file is not automatically updated during an upgrade. You can manually add the latest set of cipher suites supported in Rhapsody to the rhapsody.properties file after the upgrade. Refer to Updating Cipher Suites Post-upgrade for details.
Missing fontconfig library Versions prior to Rhapsody 6.5.0 Due to the adoption of OpenAdoptJDK in Rhapsody 6.5.0, the fontconfig library should be pre-installed on non-GUI 64-bit *nix platforms before running the Rhapsody engine installer. Installations on other platforms are not affected.

Mapper's handling of missing fields

 Versions prior to Rhapsody 6.3.x Refer to Handling of Missing Fields to determine whether your mappings require review.

Filter tests

 Versions prior to Rhapsody 6.2.3.

When loading an RLC created by a pre-Rhapsody 6.2.3 version, or upgrading from a pre-Rhapsody 6.2.3 version, Rhapsody converts input test messages into individual tests. For filter testing in pre-Rhapsody 6.2.3 RLC that is configured to send multiple messages through a filter simulating a Message Collector, or in a specific order, Rhapsody 6.2.3 converts them into individual tests with no discernible run order.

To reproduce the pre-Rhapsody 6.2.3 message collector functionality on later versions of Rhapsody, you must manually create a test and add the multiple test messages using Message Collection Test Mode. To do so, you can use the test framework's copy-paste functionality to copy messages from one test to another.

HL7 Acknowledgement Generation filter

 Versions prior to Rhapsody 6.0. After upgrading, ensure the Message Definition configuration property on the HL7 Acknowledgement Generation filters is set correctly to represent the HL7 version of the incoming message when using the setting HL7 version: Same as input message.

Change in the output of database components from non-deterministic to deterministic

 Versions prior to Rhapsody 6.0.

As of Rhapsody 6.0, the order of the XML elements in the output messages of database components is the same as the order of the columns in the database results set. Ensure that your configuration does not rely on non-deterministic results. Refer to Properties for XML Message Generation for details.

HTTP compression for Management Console

Versions from Rhapsody 5.5.7 to 5.5.x.

In Rhapsody 5.5.x as of Rhapsody 5.5.7, HTTP compression used for Management Console access is disabled by default for the MIME types text/xml and text/plain. To maintain this behavior when upgrading, disable the MIME types text/xml and text/plain by adding the following properties to the rhapsody.properties file:

WebMonitoringService.http.compressablemimetype=text/xml,text/plain
WebMonitoringService.https.compressablemimetype=text/xml,text/plain