Category: How To

With Pulse v5.3, you can now include or exclude feeder files before creating offline package.

The following procedure will demonstrate how to install the pulse license within your installation.

Pulse now enables you to customise the email that is generated based on alert criteria. This is useful if you want to integrate the Pulse alerts into an existing help desk/ticketing system that accepts email as a ticket input source.

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.