Software AG strongly recommends that you upgrade in a controlled test environment and test that environment for proper operation before promoting to your production environment.

Provision new environments to support the upgrade. Environments in which you conduct testing should mirror the production environment.

Obtain test data from the source environment and establish baseline test results.

Many upgrade issues are caused by forgotten environmental settings. Plan, document, and test these thoroughly.

Identify test tools for unit, functional, and non-functional regression testing.

Define acceptance and sign off criteria.

Automate a core set of regression tests for the upgrade. Software AG recommends focusing your tests most heavily on product areas that have undergone the most change. The readmes and release notes provide all product change information (see Preparation and Planning for details).

If upgrading to new machines, make sure connections and firewalls are open to back-end systems before starting any system testing.

Use an issue management system to track defects and issues.

If code freeze of the old environment during test is not possible, merge code changes from the old environment into the baseline and re-test the new baseline.

Look in log files.

Go to the Knowledge Center on the Empower Product Support Website and search using keywords such as upgrade.

Go to the Software AG TECHcommunity and:

Join the upgrade discussion forum (Forums > webMethods > Upgrade).

Read and share tips and tricks and other information in the upgrade wiki (Wiki > webMethods > Upgrade).