Migrating a Data Package
How you migrate a data package depends on your deployment type.
- For on-premise users: See the Operations Console Guide for IvantiNeurons for ITSMfor information about migrating data.
- For Neurons for ITSM Cloud users: To request a package be moved from the staging instance of the tenant to the UAT instance of the tenant or from the UAT instance of the tenant to the production instance of the tenant, contact Ivanti. Refer to the process described in the Customer Data Migration Guide for Ivanti Service Management.
Example: Migrating Request Offering Changes
This example describes how to make a change to a request offering in the staging instance of a tenant and then migrate the change to the production instance of the tenant.
Neurons for ITSM does not have a application for tracking request offerings, so to migrate a request offering from one environment to another, you must create and apply a package and also do a master data push using the Neurons for ITSM Operations Console. Creating and applying a package alone does not migrate the request offering change.
Before you begin, use the Neurons for ITSM Operations Console to refresh the staging instance of the tenant from the production instance of the tenant. This ensures that you have the same baseline in both environments before you make the change.
When you make changes to request offerings, Neurons for ITSM tracks the changes made to the request offering and associated workflows and quick actions, but does not track the changes made to some related content. Neurons for ITSM does not record changes for the organizational unit, configuration item service, location, or request offering links to organizational units, configuration item services, or locations. This can cause confusion when you move changes from one application to another.
The changes that the application records may differ depending on if you are logged in as an administrator or as another role when you make the changes.
- If you make the changes as a service owner, you cannot select the project to apply the changes to. Therefore, all changes are added to the default project.
- If you make the changes as an administrator, you can select the project to apply the changes to. Before you make the changes to the request offering, we recommend that you create a new project and apply the changes to that project. Refer to section Creating a Project in Managing Projects.
- (Optional. For administrators only.) Go to the Configuration Console, create a project, and then select it.
- Make the changes to the request offering. The application tracks the changes to the workflows and quick actions associated with the request offering.
- Create a package with the transaction sets associated with the changes that you made to the request offering. Ensure that the package contains all of the changes made to the application since you made the baseline, as described in Before you Begin, regardless of if they are related to your project.
- Log into the Neurons for ITSM Operations Console.
- Refresh the UAT instance of the tenant from the production instance of the tenant.
- From the Tenants tab, find the instance to migrate and click Manage Migration.
- At the top of the page, click Enable to enable the package migration feature. At the confirmation message, click OK.
- In the arrow going from the staging instance of the tenant to the UAT instance of the tenant, click Apply Package.
- Do the following:
- In the Source Package field, select the package to migrate.
- Check Skip Target Tenant Backup.
- Select Apply without validation. This allows you to apply the package even if there are errors. You may need to fix the errors after the change is applied, if you do not want to restore the database and fix the root cause.
- Click Execute.
The application migrates the package.
- In the arrow going from the staging instance of the tenant to the UAT instance of the tenant, click Push.
- Do the following:
- In the Operation field, select Copy Master Data Only.
- Check Delete data items in uat that do not exist in staging.
- Check Service request.
- Click Execute.
The application migrates all of the service requests.
If the target tenant instance does not have an equivalent request offering, (for example, if you are importing a package from the Ivanti App Store or a package from another application), you must manually link the configuration item service, organizational unit, and location.
- Log in to the application on the UAT instance of the tenant.
- Open the Request Offering workspace.
- Find and open the existing request offering.
- On the 1. Define request offering page, for the Service field, select the configuration item service associated with this request offering. Note that in many cases, the configuration item service is represented by a GUID and not by its name in the drop-down list. Be sure to select the correct configuration item service.
- Click Next twice until you reach the 4. Publish Action Access page.
- Click Add to add a new organizational unit and location. The application displays a new line.
- Click Any under the Team header and select the organizational unit associated with this request offering. Click OK. Note that in many cases, the organizational unit is represented by a GUID and not by its name in the drop-down list. Be sure to select the correct organizational unit.
- Click Any under the Location header and select the location associated with this request offering. Click OK. Note that in many cases, the location is represented by a GUID and not by its name in the drop-down list. Be sure to select the correct location.
- Click Save & Exit.
- Log into the UAT instance of the tenant and test the changes.
- If anything is wrong, perform the procedures in both Packaging the Changes Using Ivanti and Migrating the Data from the Staging Instance to the UAT Instance.
- When you are finished testing the change and are satisfied with the results, go back to the staging instance of the tenant and close the package. This ensures that no further changes in the application are added to the package.
- Log into the Neurons for ITSM Operations Console.
- From the Tenants tab, find the instance to migrate and click Manage Migration.
- At the top of the page, click Enable to enable the package migration feature. At the confirmation message, click OK.
- In the arrow going from the staging instance of the tenant to the production instance of the tenant, click Apply Package.
- Do the following:
- In the Source Package field, select the package to migrate.
- Ensure that Skip Target Tenant Backup is not checked.
- Select Apply without validation. This allows you to apply the package even if there are errors. You may need to fix the errors after the change is applied, if you do not want to restore the database and fix the root cause.
- Click Execute.
The application migrates the package.
You must publish the service request master data from the UAT instance of the tenant to the production instance of the tenant because the UAT instance has the tested service request data. (If you are sure that no changes were made to the staging instance of the tenant, you can push the service request data from there to the production instance of the tenant instead.)
- Log into the Neurons for ITSM Operations Console.
- From the Tenants tab, find the instance to migrate and click Manage Migration.
- In the arrow going from the UAT instance of the tenant to the production instance of the tenant, click Push.
If there is no Push link in the arrow, you must push the data from the staging instance to the UAT instance. In the Operation field, select No Op (Increase version only) and click Execute.
- Do the following:
- In the Operation field, select Copy Master Data Only.
- In the Additional Data section, select any or all of Service (CI.Service), Organizational Unit (OrganizationalUnit), and Location (Location).
- Check Skip target tenant backup before operation.
- Check Delete data items in production that do not exist in uat.
- Click Execute.
The application migrates all of the service requests.