The Pulse thick client is designed to be the central point for monitoring all of your TM1 servers. It streams multiple Pulse servers into one convenient location so you can quickly diagnose issues, cancel threads, disconnect users and even start/stop your TM1 services remotely.

Pulse allows you to merge existing packages if they haven’t already been executed. This allows you to aggregate multiple changes into one large package that can be provided to your operations or run team to upgrade your test and/or production system.

Pulse stores all of the information in requires within the folders in the install directory. To back up this information in case of hardware failure or other misadventure you should copy the following directories.

Pulse makes it easy to compare two TM1 instances with the migration features:

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:

This article outlines the two security modes that can be used to either exclude or include access to TM1 instances within Pulse.

This article details the configuration of user credentials and security permissions, the reader of this article should have read the Pulse Security and Pulse Group Security articles.

This article details the Group security, the reader of this article should have read the Pulse Security article.

This article explains how to secure your Pulse system. This article starts with the security definition concepts with Pulse. At the end of this article the reader should understand of how the security of Pulse works and how to configure it according to the security requirements in their organization.