/
Offline Migration (Cold Promote)

Offline Migration (Cold Promote)

Offline migration allows Pulse to integrate with the traditional method of copying TM1 objects between instances. Rather than applying changes to a live instance, object files are packaged, copied to the target data directory, and loaded when TM1 restarts.

Note: Offline migration is only available for IBM Planning Analytics (TM1) instances installed on-premise or on a private cloud.

Overview

The traditional offline migration process works 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 changed or created TM1 object files (.cub, .dim, .pro, .cho, .sub, etc.) from the data directory.

  3. Stop the target TM1 service.

  4. Copy all files from the source directory to the target data directory, overwriting existing files.

  5. Start the TM1 service.

Pulse enhances this process by:

  • Automatically tracking all changes in your model, eliminating the need to manually record what has changed.

  • Identifying all dependent objects related to your changes, so nothing is accidentally missed.

Creating an Offline Package

Offline packages are created using the same package creation methods as live packages (Source Control, Manual, or All). When saving the package, select the Offline Update (or Both) option.

Package Contents

An offline package contains two directories:

  • items/ β€” The core objects selected for migration. For example, selecting a dimension includes the .dim file as well as associated objects such as }ElementAttributes and }ElementSecurity cubes.

  • dependencies/ β€” Objects related to the selected items. For example, a process is included here if it is part of a chore or is called via ExecuteProcess in TI. Dependencies should generally only be copied to the target if they do not already exist there.

Steps to Apply an Offline Package

  1. Download the offline package file from Pulse.

  2. Copy the package to the target TM1 server.

  3. Unzip the package contents.

  4. Run Save Data on the target TM1 instance.

  5. Stop the target TM1 service.

  6. Copy the contents of the items directory to the target data directory. Replace any existing files.

  7. Copy the contents of the dependencies directory to the target data directory. Skip any files that already exist.

  8. Restart the TM1 service.

The migration is now complete.