The following table outlines the steps Rhapsody as an organization recommends for updates and upgrades, presented in one checklist, with indications of the steps that are specific to the upgrade process.

  • The checklist assumes a multi-environment upgrade process; the steps in the checklist must be performed in one or more non-production environments initially and then in the production upgrade.
  • Non-production environments should match the production environment as closely as possible while not interfering with the production environment in any way.
  • We strongly recommend at least two non-production environments. This ensures that there is an opportunity to upgrade, revise and verify the upgrade process.

Complete the following checklist for each environment being affected by product changes:

1. Before Upgrade

2. Upgrade

3. Functional Testing

4. Non-functional Testing

5. Final Steps

Review relevant manual upgrade steps in the flowchart in Upgrade Caveats.

▢ Done

▢ N/A (update only)

Follow installation steps as defined for your version.

▢ Done

Re-run the test message validation set to ensure the same results (output messages) as the pre-upgrade test.

▢ Done

Observe message throughput on routes and interfaces and compare with pre-upgrade statistics.

▢ Done

Document outcomes, changes and learnings for future upgrades.

▢ Done

Engage PSG?

▢ Yes

▢ No

Follow manual processes required, as reviewed previously.

▢ Done

▢ N/A (update only)

End-to-end testing: do end-results in downstream systems appear as expected?

▢ Yes

▢ No



Upgrade plan documented, including responsibilities and timing (change windows etc.), corporate policy and rollback plan.

▢ Done


Ensure that all stopped components were in the stopped state previously.

▢ Done



Current production state documented, including environmental info (usernames, datastore location etc.), PDF of configuration, stopped components, Error Queue count.

▢ Done





For a production upgrade, backup configuration.

▢ Done

▢ N/A (non-prod.)





For production upgrade, backup datastore.

▢ Done

▢ N/A (non-prod.)





For a non-production upgrade, import production configuration (changing environment variables as required).

▢ Done

▢ N/A (prod.)





Run a test message validation set with production data.

▢ Done





Record typical message throughput on routes and interfaces.

▢ Done