Category: Product
-
Troubleshoot Faster by Analysing the tm1server.log in Pulse
Every IBM Planning Analytics (TM1) developer will be familiar with the tm1server.log – a file that contains important details about activity including executed processes, chores, loaded cubes, and much more…
-
TM1py v1.10 is now available
Since its first release in 2016, TM1py has now established itself as the most popular scripting framework for IBM Planning Analytics (TM1). Most things that you can’t do out of the box with TM1 you can do easily with Python and TM1py. TM1py makes TM1 works like a charm with Python.
-
Enabling Chore and Process History in the database.
The information you see in the Chore and Process history feature of the Pulse Web client is coming from the Pulse Elasticsearch data:
-
How does Pulse determine if a TM1 instance is offline
It might happen that you are receiving an offline alert from Pulse but the TM1 instance is still running.
-
Migrating dimensions live with Pulse for TM1
Pulse can migrate all IBM Planning Analytics (TM1) objects using two modes: Live (without having to restart the TM1 instance) or Offline (cold-promote).
-
Hiding attributes values in Pulse for TM1 Model Spotlight
By default Pulse is going to store the attributes’ values for all dimensions with less than 5,000 elements in the vcs folder.
-
Converting Perspectives Action Buttons into Slice Buttons
Actions buttons created with TM1 Perspectives will need to be converted before they can be used in Slice. To convert all buttons from all spreadsheets, you can use the Convert Buttons button available in the Slice ribbons: A pop-up window will open as below: You can either convert the buttons from the Active Workbook or…
-
Reasons why Pulse can’t connect to an instance
This article explains the different reasons why Pulse can’t connect to a TM1 instance.
-
Using the HTTP Strict Transport Security (HSTS) response header
To enable the HTTP Strict Transport Security (HSTS) response header. Open the settings.yml file located in the Arc installation directory and add the following parameter:
-
Using TLS protocols v1.2+ with Arc
To enable Arc to use only TLS protocols (v1.2+) and ciphers that are known to be secure: