Migrating Data using Heat Development Project
This is the recommended method for migrating data. See The Four Ways to Migrate Data for a list of the ways to migrate data.
For information about using the Ivanti Service Manager development project with packages that have been downloaded from the App Store, see Appendix D: Working with Packages from the App Store.
•About Using the Ivanti Service Manager Development Project to Migrate Data
•Cautions About the Ivanti Service Manager Development Project
•About the Ivanti Service Manager Development Project
•Using the Ivanti Service Manager Development Project to Create a Data Package
•Using the Ivanti Service Manager Development Project to Migrate a Data Package
•About Metadata Read-Only Mode
About Using the Ivanti Service Manager Development Project to Migrate Data
Use the Ivanti Service Manager development project in the Ivanti Service Manager Configuration Console (not within the Operations Console) to create packages to migrate data from one instance of a tenant (such as staging) to another instance of a tenant (such as UAT). In this way, you can pick and choose which data to migrate instead of migrating the entire system. The Ivanti Service Manager development project allows Ivanti Service Manager to maintain a history of changes in metadata, validation data, configuration settings, and a few specific master data business objects. It also allows you to package a unit of integral changes into a package for migration to another tenant instance.
Cautions About the Ivanti Service Manager Development Project
•The Ivanti Service Manager development project gives you the ability to update the production instance of your tenant with configuration changes made in the staging instance of the tenant. If these changes conflict in some way with your Ivanti Service Manager system, they cannot be undone.
•We recommend that you enable and use the Ivanti Service Manager development project to migrate data, and that you do not switch between enabling and disabling the Ivanti Service Manager development project. See The Four Ways to Migrate Data for a list and description of the four different ways that you can migrate data.
•We recommend that you plan and prepare for moving a package as described in this section. We strongly encourage you to make a complete backup of the target tenant instance and to create a procedure for restoring the backup if need be:
•If there is a problem with the UAT instance of your tenant, you can restore it from the production instance of your tenant using the Operations Console, by refreshing the UAT instance of your tenant.
•If there is a problem with the production instance of your tenant, you need to restore the production instance of the tenant from the backup as quickly as possible using Microsoft SQL tools, as any transactions that are created in the production instance of the tenant after a backup and before a restore will be lost.
•Before you enable and use the Ivanti Service Manager development project, check with Support by visiting https://support.ivanti.com .
About the Ivanti Service Manager Development Project
•About Using Your Named Account to Log In
Limitations
•The Ivanti Service Manager development project has not yet provided a way to validate package dependency. You need to ensure that if you make a change that depends on another change, you migrate both changes.
•Before handing out a package for migration, determine whether the package is complete and self-contained. The package should contain all dependent changes. Not having all the required changes in the package may cause the system to fail when you migrate the package and you may have to restore the target system from the back-up system.
•You cannot use the Ivanti Service Manager development project and Simple Mode or Advanced Mode at the same time. (See The Four Ways to Migrate Data for a list and description of the four different ways that you can migrate data.) To use Simple Mode or Advanced Mode, you must disable the Ivanti Service Manager development project.
•You cannot use the Ivanti Service Manager development project to migrate certain types of data. For a list of the data that cannot be migrated, see Items Excluded from Migration.
Terminology
The Ivanti Service Manager development project uses the following terms:
•Transaction: An individual change to the database.
•Transaction set: A group of transactions.
•Project: A group of transaction sets.
•Package: Contains the transaction sets from multiple projects.
•Aspect: Information about a feature, a component, a patch, or even a configuration. An aspect presence indicates the presence of the feature.
About Using Your Named Account to Log In
The first time that you log into Ivanti Service Manager as an administrator, the system displays a message stating that you are logging in as an administrator. This is not suitable for making configuration changes. If you make configuration changes while logged in as an administrator, you may not be able to package the changes properly.
We recommend that you no longer use a generic administrator account when you are in the Configuration Console. With the Ivanti Service Manager development project, the Ivanti Service Manager system tracks all the changes made and attributes them to the user who made the changes. If all users log in using the generic administrator account, there is no way to know who made the changes.
The system displays a message stating that the Configuration Console is in production metadata read-only mode. If you see this message, click OK and then log out as an administrator and log back in using your named account. See About Metadata Read-Only Mode.
Using the Ivanti Service Manager Development Project to Create a Data Package
See Appendix C: Using the ISM Development Project to Migrate Data for complete information about how to use the Ivanti Service Manager Configuration Console to create packages, which can be used when migrating data. You perform those tasks in the Ivanti Service Manager Configuration Console and not in the Operations Console. This is the same information that is found in the Ivanti Service Manager online help and is only copied here for your convenience.
Using the Ivanti Service Manager Development Project to Migrate a Data Package
•Enabling the Ivanti Service Manager Development Project
•Disabling the Ivanti Service Manager Development Project
Enabling the Ivanti Service Manager Development Project
To enable the Ivanti Service Manager development project, follow these steps:
1.Log in to the Operations Console and click the Tenants tab.
2.Navigate to the instance of the tenant for which you will perform the migration and click Manage Migration.
3.If the tenant is not part of a landscape, the system prompts you to add the tenant to a landscape to prepare it for migration. Click Proceed. The migration dashboard opens showing all of the tenants and tenant instances and available migration paths in the landscape.
4.To enable the Ivanti Service Manager development project, click Enable.
5.Click OK at the confirmation prompt.
The migration dashboard looks like this:
For customers who have been using HEAT Service Management since Release 2014.2 or earlier, you may not see the Apply Package link, even though you have enabled the Ivanti Service Manager development project.
If you do not see the Apply Package link, refresh the staging instance of the tenant by following the process in Creating the First Staging or UAT Instance of the Tenant from the Production Instance of the Tenant.
Migrating the Package
To migrate a package from the staging instance of a tenant to the production instance of a tenant, the package must be closed. You cannot move open packages to the production instance of a tenant. The package does not have to be closed, however, if you are migrating from the staging instance of the tenant to the UAT instance of the tenant.
The system displays an informational message if you migrate the same package to the same tenant instance more than once.
To migrate a data package, do the following:
1.Log in to the Operations Console and click the Tenants tab.
2.Navigate to the instance of the tenant for which you will perform the migration and click Manage Migration.
3.To migrate the data package, click Apply Package in the corresponding arrow. The system displays the Applying Package To page.
4.Enter selections as follows:
| a. | Select the name of the source package from the drop-down menu. |
| b. | We highly recommend that you do not check Skip Target Tenant Backup. |
| c. | Select Apply without validation to apply the package without first validating it. |
5.Click Execute to migrate the package or click Preview to create an XML file with changes that you can review before you migrate the data.
6.Click OK at the confirmation prompt.
When the migration is complete, the system displays a message that the package has been applied successfully. When you refresh the staging or UAT instances of the tenant, all transaction sets are cleared.
Checking the Data Migration
To check that the data migrated successfully, log in to the UAT instance of the tenant and search for the changes.
1.Log in to the Ivanti Service Manager system for the UAT instance of the tenant. The system displays a message stating that the UAT instance of the tenant is locked.
2.Search for the changes.
Disabling the Ivanti Service Manager Development Project
1.Log in to the Operations Console and click the Tenants tab.
2.Navigate to the instance of the tenant for which you will perform the migration and click Manage Migration.
3.If the tenant is not part of a landscape, the system prompts you to add the tenant to a landscape to prepare it for migration. Click Proceed. The migration dashboard opens showing all of the tenants and tenant instances and available migration paths in the landscape.
4.To disable the Ivanti Service Manager development project, click Disable.
About Metadata Read-Only Mode
When you use the Operations Console to migrate data, the production and UAT instances of the tenant are always in metadata read-only mode, which is equivalent to being locked. When the system is locked, you cannot make changes to most types of metadata in the Configuration Console. (You can only make changes to the following four items: saved searches, reports, quick actions, and dashboards.) While migrating data, the system temporarily unlocks the metadata on the target system.
You cannot import high-impact packages if your system is in metadata read-only mode.
To put a system into metadata read-only mode, do the following:
1.Log in to the Operations Console.
2.Click Tenant. The system displays the Tenants workspace.
3.Find the tenant to edit and click Edit Properties.
4.Check Metadata Locked.
5.Click Save.