Category: How To
-
Including control objects and bedrock processes to source control and dependencies
Control objects and Bedrock processes are not included by default in the source control and in the dependencies (when using the migration).
-
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.
-
Allowing Pulse to redirect host
The default URL for the Pulse Web Client is http(s)://localhost:8099 or http(s)://serverName:8099.
-
Changing the frequency of the Pulse Elasticsearch indices
This article is only relevant if your server is running short of disk space and that you want to reduce the size of the Pulse Elasticsearch cluster.
-
Mastering conditional feeders in TM1
This article gathers everything you should know about conditional feeders in IBM Planning Analytics powered by TM1.
-
Deleting Pulse Elasticsearch indices
The size of the Elastic Cluster can be found in the Pulse About page:
-
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.
-
Connecting a TM1 instance
To connect to a TM1 instance with Pulse 6 or later, Pulse uses the TM1 REST API, you need to make sure first that the TM1 REST API is enabled for each instance and accessible from the Pulse server, more information here: