How to Isolate Applications Manager Environments for Upgrade Testing (Applications Manager)

Products

• Automic Applications Manager

Issue/Introduction

This article provides best practices for testing upgrades of the Applications Manager master server. It outlines how to isolate a test instance to ensure the production environment remains unaffected while allowing for thorough validation of upgrades.

Environment

Applications Manager (All Versions)

Cause

When deploying a new Applications Manager master server, the application will affect the existing production environment if it is pointed to the same production database schema during installation. Proper isolation is required to prevent cross-contamination.

Resolution

To test upgrades or isolate the Applications Manager environment without affecting production, perform the following steps:

1. Perform a full Oracle export (.dmp) of the current Applications Manager schema.
2. Import the exported schema data into a separate, isolated Oracle database instance.
3. Install Applications Manager on the new test server.
4. Point the installation to the newly imported, cloned database schema.
5. Disable all schedules in the new environment immediately after installation to ensure no jobs run unintentionally. See article 93172 for more info.
6. Verify the installation and configuration of any integrations (such as DNA) required for testing purposes.

Additional Information

For detailed technical steps on copying and moving instances, refer to the official documentation.