At first sight, the TM1's file-based architectural makes TM1 migration from one instance to another quite straight forward:
Even if it looks easy, you have to make sure that you picked all the files from the source instance. For example if you are migrating a cube, all dimensions have to be included and to migrate a dimension with its attributes you have to include all control objects.
If you miss one TM1 object, you will have to restart the target instance again. It might not be a big deal if you are working on development but if you are in production it might be difficult to find a new time-slot.
The Pulse migration feature overcomes TM1's file-based architectural limitations with a centralized model that reduces risk of mistakes.
Advantages of using Pulse for TM1 migration
- Never forget a TM1 object: When migrating a TM1 object, Pulse finds all dependencies which should be included during the migration.
- View changes before migration: Pulse tells you exactly what is going to be updated in the target instance. You can view in details the exact lines of code which are going to be updated.
- Automatically back-up the database folder.
- Very robust: It is used by many clients for the past years. With Pulse v5.5, we optimized the migration to make it even faster.
How it works?
Pulse provides a structured approach to migration, which follows two important steps:
- Create migration package: Gather all TM1 objects you want to migrate into one package from one source instance.
- Execute migration package: Import all TM1 objects from the package to the target instance.
Each package contains all the information and files required to update a target instance.
Pulse has several methods for creating a migration package. The two main methods are source control and manual migration:
- The Source Control option allows you to 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.
- The Manual option allows you to pick the objects you want to migrate manually. It is not restricted by changes that have been made, any object can be migrated (except views and subsets). Pulse will then find all dependencies of the TM1 objects selected:
Types of packages
Once you picked which methods you want to use to create the package, you will then have to decide the package type:
- Live Update: The execution of packages can be performed while the server is still running.
- Offline Update: Pulse will create a folder with the TM1 object files. You can then copy the files manually into the target instance.
Pulse provides enterprise grade migration features allowing you to easily move changes in your TM1 models between servers.