Pulse can migrate all IBM Planning Analytics (TM1) objects using two modes: Live (without having to restart the TM1 instance) or Offline (cold-promote).

If you are using the offline migration, Pulse gathers the files (.dim for dimensions) into a folder that you can copy in production and restart the instance. As you’re copying the .dim file, the dimension will be the same between your source and target instance.

The advantage of using Pulse instead of doing is manually is that Pulse gathers all the files related to the dimension such as the attributes and security cubes.

By default Pulse does not track element changes in dimensions. You will need to enable element changes tracking by turning on Source Level for the specific dimensions before being able to migrate elements dimensions. In the example below, Source Level is activated only for the Account dimension:

If Source Level is not enabled for a dimension, migrating a dimension via Pulse’ Live migration package creates an empty dimension with all attributes.

If Source Level is enabled for a dimension, Pulse is going to check for changes at the elements level between the source and the target instance and apply the changes. If there are no changes Pulse is not going to do anything.

The fastest way to migrate large dimensions (more than 5,000 elements) using a live package is to ask Pulse to execute a process during the execution of the package.

• Executing processes during the migration

After the creation of the dimension and the attributes, Pulse is going to execute the process to populate the elements and attributes’ values.

The fastest way to create elements in a dimension is to execute a process. Pulse can create elements in a dimension but it is going to be slower than executing a process.

Source Level needs to be enabled for the dimension both on the source and the target instance.

• Pulse Migration