Offline Migration (Cold Promote)


Offline migration allows you to fit Pulse into the traditional method for copying or migrating objects between TM1 instances. The process can be summarised as follows:

  1. While making changes in your development environment keep a record of what has been changed.
  2. Create a "source" directory and copy all of the objects (cub, dim, pro, cho, sub, etc) that have been changed or created from the data directory.
  3. Stop the target TM1 service.
  4. Copy all of the files in the source directory to target Data Directory overwriting file if they exist.
  5. Start the TM1 service.

 Pulse greatly enhances this process by providing two important features:

  1. Changes are automatically tracked in your model so you no longer need to record what changes you have made.
  2. Pulse will identify all of the dependent objects related to these changes and include them in the package so that nothing is missed.

Create a Package

You create an offline package in the same way as Pulse "Live" packages:

All you need to do is select the Offline Update (or Both) option when you save the package:



What is in the Package

Pulse contains a package with two directories: items and dependencies. These directories contain the files you need to copy to your target server. The items directory contains the core objects that you need to copy. For example if you select a dimension it will include the dim file but also }ElementAttributes cube, }ElementSecurity cube, etc.


The dependencies directory contains objects that are related to object selected, i.e. a process will be included in the dependencies directory if it is part of a chore or is called using the ExecuteProcess function in TI. The dependencies as a rule should only be copied to the target data directory if they do not exist.

Steps to Update the Data Directory

  1. Download the Offline package file from Pulse.
  2. Copy the package to your target TM1 server.
  3. Unzip the contents of the file.
  4. Run Save Data on the TM1 instance you are going to update.
  5. Stop the target TM1 service.
  6. Copy the contents of the items directory to the target Data Directory. If the item exists replace the file. 
  7. Copy the contents of the dependencies to the target Data Directory. If the dependency exists chose to skip the file.
  8. Restart the TM1 service.
  9. The migration is complete.