Release Management Tool

The Release Management Tool is a utility that lets you move ALM content from a test machine to a production machine and then back again. It is a self-extracting executable that runs on the core. This utility works with any version of ALM (from 3.5 to 5.0). The utility prevents other users from modifying either the production or test databases so users can't change the database while the process is taking place.

If you are going from test to production, the utility brings over all definitions (form definitions, asset definitions), but does not bring over individual instances of the definitions. You can choose to bring over roles (but not users), integration servers, and user/group repository settings.

If you are going from production to test, you can bring over individual instances (but not the users associated with those instances). You must have a clean database (i.e., restoring a database that was backed up immediately after an installation, or a clean reinstallation).

NOTE: In all versions of ALM, the target must be licensed and configured before running the utility.

NOTE: Windows Firewall must be turned off for the utility to work. Remember to turn it back on after the utility has completed.

1. In the Release Tool folder, double-click LANDesk.ServiceManagement.ReleaseTool.exe.
2. Click Test to production or Production to test, depending on which operation you wish to execute.
3. Under Test database, enter the database credentials (name of server, user name, password, and database). Once the utility completes successfully, it remembers both the test and production database information so it will not be necessary to re-enter it.
4. Under Production database, enter the database credentials.
5. Click Options to choose the objects to synchronize between the test and production databases. Select the All roles, All integration servers, All user/group repository settings, and Move Form/Asset instances and All contacts (production to test only) check boxes to synchronize.

   In test to production environments, workflows will not function if there are exception contacts configured. For such a workflow to function, you must select All contacts to import contacts from the test system to the production system.

6. Click Changes to view the proposed changes to the databases before continuing. The Changes button displays the parts of the database (schema and data instance changes) that will be made to the target database. This includes everything under the Process tab and the Settings dialog box (workflows, event listeners, e-mail templates, schedules, fields, and settings changes such as roles, scopes, and so forth).
7. Click Go! to begin the synchronization process. The process may take some time, as the utility is completing analysis between two databases.

When finished, the utility will prompt you, stating that the changes have been successfully completed. The Proposed changes dialog box should be empty.