Creating a Migration Package

Pulse has a number of methods for creating a migration package. Each one is important in certain circumstances. All of the options create a migration package that can be applied to multiple target servers. All options include the files that have been selected, dependencies and documentation that has been added to each object.

Pulse doesn’t migrate data with the exception of attribute values. If you want to migrate data you will need to export it to file (Bedrock.Cube.Data.Export) and then import into the cube (Bedrock.Cube.Data.ImportFromFile) after the migration has completed.

Terminology

• Source: Is the instance of TM1 you are moving the changes from.
• Target: Is the instance of TM1 you are going to apply the migration package against.

Source Control

Pulse has the ability to record every change that is made to objects within your TM1 environment. This allows you to easily identify what has changed over a given time period by developer.

The Source Control option allows you to first query for a list of changes based on a date range and also by developer/user (leave this blank for all users) and then select the items you want to migrate.

Once you have Pulse up and running and monitoring changes it is recommended that you use this method for creating migration packages.

Manual

The manual option allows you to select the objects you want to migrate. It is not restricted by changes that have been made, any object can be migrated.

Documentation Only

This option is useful if you want to copy the documentation you have entered in Pulse for each TM1 object from one instance to another. The TM1 objects themselves are not included so the documentation will only be applied to objects that exist on the target instance. 

This allows you to enter all of the documentation in one place and then propagate it to all of your TM1 instances.

All

The All option includes every TM1 object within the migration as well as the documentation for each object. Use this method to move all objects from one instance to another or if you want to compare two instances of TM1 (i.e. dev and prod).

As the package contains all objects from the source instance you can quickly identify what has changed by running the package against the target server. Pulse always performs a compare before any changes are applied to the target server.