Category: Code
-
Pulse Monitor
Monitor all your servers on one screen Pulse gives you the confidence to handle the complexity that comes with expanded use of your applications. Monitor what’s happening Pulse allows you to monitor your system live in both the web interface and the rich Windows client. All of the important metrics second by second are in…
-
How to test the connection to TM1
Pulse needs to authenticate to IBM Planning Analytics (TM1) via the REST API. Pulse includes a script to test how long it takes to authenticate to TM1. Starting with Pulse v6.2.0, two powershell scripts are available in the utils folder: How to run the script When your TM1 application is setup with basic authentication (security…
-
Arc and Slice v4.0 is now available
A new version of Arc and Slice is now available to download. Version 4 is a big milestone in the history of Arc and Slice. You can now connect your Arc server to Pulse to unlock many new features in your Arc application, such as Instance/Server Monitoring, Full Model Search, Alerts and Change Tracking. We…
-
Pulse v6.2 is now available
Pulse v6.2 comes with many optimizations in the logic to determine the status of the TM1 instances. The main new feature is the connection with Arc.
-
Connecting Arc to Pulse
Pulse minimum version should be v6.1.2
-
Making it Easier to Write and Test MDX Queries with Arc
As we explained in a previous article, MDX is becoming more and more important in the IBM Planning Analytics / TM1 community and it is one of the key skills that any TM1 developer needs to have in order to make the most of the software.
-
How to Get the Most out of MDX Forms with Slice
MDX forms are an incredibly powerful add-on to the existing Excel reports in IBM Planning Analytics (TM1) and they offer a tremendous level of flexibility and customization to get you the results that you need. In this article, we’re going to go deeper into some of the more advanced use cases, so if you’d like…
-
Arc settings.yml file
Arc settings file can be found in folder where Arc was installed and it is called: settings.yml.
-
Applying your own naming conventions for parameters and variables in Arc
Process naming is used by Arc when adding prefixes to new parameters and variables. It is also used for matching variables against dimension in CELLGET and CELLPUT functions. For example a variable called vAccount will automatically be inserted into a CELLGET (using auto-complete) if it has a dimension named Account.
-
Pulse Transforms Cold Migration in TM1
We’ve all had that moment where we complete a migration of IBM Planning Analytics (TM1) objects and then when we start the TM1 instance, we realize that we forgot a dimension, an attribute cube, or a picklist cube. This can be very frustrating as it means that you have to stop everything and restart the…