Category: Pulse
-
Troubleshooting Pulse documentation update
When setting up a new TM1 instance, it is important to execute the documentation. To execute the documentation, go to Administration > Update Documentation:
-
Getting started with Pulse on the Cubewise Cloud
This article gathers the steps that need to be completed when using Pulse on the Cubewise cloud monitoring IBM Planning Analytics SaaS:
-
What’s new in Pulse v6
This release is the most important release of Pulse since it’s creation in 2014. Pulse was optimized for the TM1 REST API, enabling one single application server to monitor many TM1 servers.
-
Choose which instance should be monitored by Pulse
Pulse v6.0.1 introduces a new Active flag per TM1 instance. By default all TM1 instances will be set to Active. Pulse monitors all TM1 instances with Active flag set to true.
-
Set the maximum minutes of data cached in the browser
By default Pulse keeps 15 min of history in the browser to enable the playback feature from the Live Monitor page.
-
Exporting changes by users to CSV file
Pulse will log all of the changes whether they are through a migration package or manually. This information can be easily retrieved from the Pulse web client (go to Change Tracking > Change History and then choose the instance):
-
Including control objects and bedrock processes to source control and relationship diagrams
Control objects and Bedrock processes are not included by default in the source control and the relationship diagrams features.
-
Migrating Pulse v5.x history into Pulse v6.x
This article explains the steps to migrate Pulse 5 data from one server to a new server where Pulse 6 is installed.
-
Enable TM1 Web Logging to Pulse v6.x
Pulse for TM1 allows you to track how TM1 Web is being used, each time a user moves between web sheets and cube views it is logged to the Pulse database. Quickly see the current open web sheets so you can determine what is causing long running queries or slowing the system.
-
Connecting a Pulse Monitor
Once the Pulse Monitor has been installed on a separate server, the next step is to connect it to the main Pulse Application Server.