**Pulse** version 6 is now available for [download](https://forum.cubewise.com/c/pulse/pulse-clients).
This release is the most important release of Pulse since it's creation in 2014. It was rebuilt using the REST API allowing a single Pulse 6 application server to monitor many TM1 servers. This version includes many new features such as the Pulse Explorer (bringing a new way to easily view what is happening on all your TM1 instances second per second) and support for hierarchies.
* Running documentation will be **slower** in Pulse 6 than Pulse 5. Pulse 5 had direct access to the data directory, Pulse 6 instead uses the REST API and therefore information needs to be sent over the network.
* Pulse 6 **migration packages** are **_not_** compatible with Pulse 5 or earlier. This is due to format changes between the TM1 C and REST APIs.
* The **cold promote** option is no longer available as Pulse 6 doesn't have direct access to the data directory and the therefore TM1 files (.dim, cub, etc).
* You **_cannot_** run Pulse 5 and Pulse 6 side-by-side.
* A small **monitor** program is required to be installed on each TM1 server. This programs provides Pulse with information about installed TM1 services and server metrics such as CPU, memory and disk space.
* Minimum IBM Planning Analytics version is v2.0.8 (TM1 v11.6).
* This is a major update of Pulse. It is recommended to [back-up Pulse](https://code.cubewise.com/docs/backing-up-pulse) before doing the upgrade.
* Pulse 6 uses the REST API, you need to make sure the TM1 REST API ports for all TM1 instances are open and available to Pulse.
* The Pulse 6 Quick Start Guide gathers everything that you should know before installing Pulse 6. It is highly recommended to read this document before upgrading your environment. The QuickStartGuide.pdf is available in the download file.
* To use the migration features between two Pulse servers, the Pulse version needs to be the same in the two environment.
## One centralized Pulse server connected to many TM1 servers
When working with multiple TM1 servers, you can choose between installing one Pulse 6 server that will monitor many TM1 servers or installing Pulse 6 on each server. There are many advantages of a centralized Pulse server such as:
* Pulse configuration is managed in one location.
* All information about all TM1 instances are stored in the same database.
* Migration can happen between TM1 servers without having to download from one Pulse server then to upload the package to another.
* Upgrading will be quicker as only one Pulse server will need to be upgraded.
Pulse 6 fully supports hierarchies. Hierarchies are now processed by Pulse as separate dimensions. All features that can be applicable to dimensions are available to hierarchies such as documentation, change tracking and migration.
The Pulse Dashboard shows the key information about the server selected from the dropdown. A new feature called the **Dashboard Editor** has been added to edit the dashboard. For example you can choose to show the data from multiple servers instead of only the ones from the server selected:
Pulse 6 makes it easier to migrate TM1 objects between servers. As Pulse can monitor many TM1 servers, there is no need to download and then upload a migration package to migrate objects between servers. When creating or executing a migration package, you will have to choose the target server and then the target instance.
To help you in making sure that Pulse is correctly monitoring all the TM1 servers, a new alert called **Enable Pulse Monitor Connectivity Alert** can be turned on per server. Once the alert is enabled, Pulse will send an alert if the connection is lost to your TM1 servers.