Troubleshooting

Unable to generate the Validation Report

For very large TM1 and Planning Analytics models the validation report can run into 1000's of pages, this can cause issues with the rendering the report.

If the report returns the following message, Unable to generate report: Failed loading..., you will need to turn off the headers and footers.

To turn off the header and footers for all reports you can change the setting in the Pulse.cfg file.

  1. Go to the Pulse.cfg file that is located in the conf directory where Pulse is installed (default: C:\Program Files\Pulse for TM1\conf).
  2. Edit the file with Notepad.
  3. Change 2 settings to true:

    [PDF]
    DisableFooter = true
    DisableHeader = true
     
  4. Save the file. You may need to save the file to your Desktop first and then copy the file to the conf directory due to Windows file restrictions.
  5. Restart the Pulse for TM1 Application Server Windows service.
  6. Run the report again.

What's behind the execution of a migration package

Pulse helps you to migrate TM1 objects from one TM1 instance to another. If you want to know how to create a migration package in Pulse, you should check the following How to.

This article describes what's happening in the background when Pulse executes a migration package.

The execution of a migration package is split in two phases, first the deletions and then the insertion of changes.

Deletions

Pulse driven by Source control, will detect the difference between the source and target and remove the objects which are no longer required to be in the target.

For example if you delete a cube in the source instance and then you create a migration package by source control, Pulse will delete this cube in the target instance.

Or if you want to migrate a measure dimension which has 2 elements and in the target this dimension has 5 elements. Pulse will first delete all unnecessary elements.

Insertion of changes

Once Pulse has finished the deletion, it will start to insert or create the new TM1 objects by following this order.

1. Metadata

Pulse will first create all new dimensions as empty dimension. Then it will create the attributes, creates the elements and finally create the consolidations.

Note that Pulse will create first leaf elements and then consolidations, it means that the element index might not be the same between the source and the target dimension.

2 Cubes

Once the metadata step is done, Pulse will create the cubes, then the system cubes like picklist cubes or drill cubes and then finally attach the rules for cubes and element attribute cubes.

3 Processes, Chores, applications and documentation

Pulse will then create or update processes, chores, applications and finally create or update the Pulse documentation.

FAQ

Question+Mark.jpg

General

+ How often do you release new versions of Pulse?

In the past we have released major version of Pulse every 6 months, this will be moving to every quarter in 2015 due to number of enhancements being added at the request of customers.

+ How long does it take to install Pulse?

Pulse can be installed in a under 5 minutes and requires no TM1 downtime to get it up and running. You will need to restart your TM1 services before the documentation and change tracking will be fully operational. It is recommended this happens out of business hours.

+ How is Pulse upgraded?

The Pulse upgrade process takes less than 10 minutes and is managed by the Pulse installer. All you need to do is install the new version in the same location as the existing install and Pulse will manage the rest including any uprgrades to the database.

Configuration

+ What versions of TM1 does Pulse support?

Pulse supports all versions of TM1 from 9.5 onwards.

+ What are the Pulse system requirements?

SERVER REQUIREMENTS

  • Windows 2008 or later
  • .NET Framework 4.6.1
  • Min 300mb of disk space
  • Max 1.1 GB of RAM
  • CPU: < 1% during normal operations.

RICH CLIENT REQUIREMENTS

  • Windows XP, 7, 8 or 10.
  • .NET 4.6.1 Framework
  • 50mb disk space

WEB BROWSER

  • Internet Explorer 9+
  • Any other modern browser: Firefox, Chrome, Safari, etc.

DATA STORAGE AND RETENTION

  • Data is stored in embedded databases.
  • Pulse minimises the amount of data stored by only storing aggregate data (by default in 15 minute blocks)
  • Data growth is dependent on the number of TM1 users. Expect yearly data growth of approximately 50-100mb per 100 users per annum.
  • All data historical data is kept in the databases by default.

SOURCE CONTROL

  • Changes to the TM1 models are stored in Git (http://git-scm.com/) repositories.
  • All historical changes are kept within the repository.

+ Can I use LDAP / Active Directory for Pulse authentication?

Yes, Pulse supports CAM authentciation which allows any LDAP directory to be used including the Active Directory, see Pulse Authentication Using CAM / Active Directory. Starting now with Pulse v5.7.3, you can now use Windows (SSO) Authentication for Pulse.

Technical

+ Can I use my own RDBMS to Store Pulse data?

No, Pulse uses embedded databases to make the installation and configuration as easy as possible. Upgrading is seamless and there is no requirement to open ports or get a DBA involved in the management of Pulse. Since Pulse v5.6, you can choose to use MS SQL Server (2012 and onwards) instead of the default H2 database.

+ What programming language is Pulse written in?

Pulse uses a number of program languages / frameworks:

  • The core low level monitoring and thick client is written in C# on .NET 3.5.
  • The application server, documentation and change tracking is written in Java hosted in a Tomcat Application server.
  • The web frontend is written in JavaScript using AngularJS, Bootstrap, etc.

Pulse features

+ What Are Insertions and Deletions in Pulse Change Tracking?

The Insertions and Deletions represent the number of lines that have been changed. Insertions are the lines that have been added and Deletions the ones that have been removed. When a line is updated the existing line is "deleted" and replaced by a new line resulting in 1 Insertion and 1 Deletion.

+ What is the maximum size of dimension stored in Pulse?

By default Pulse when documenting dimensions will only export the elements and attributes for dimensions with less than 5000 elements. This is to reduce the size of the source control system and to allow Pulse to efficiently document the whole TM1 Model.

This value can be adjusted to include larger dimensions, see this article.

+ Can I compare two TM1 instances with Pulse?

Yes, you can compare two instances by creating an "All" migration package and then starting the execution wizard on the target instance. All changes will then be listed. See Compare Two TM1 Servers Using Pulse for more information.

+ Reasons why you can't see a TM1 instance in Pulse?

  1. Check TM1 bin directory
  2. Check user profile settings
  3. Check SSL certificates
  4. Check the user account which is running Pulse services
  5. Check AutoStartServicesOnly parameter in Pulse.cfg

More information in this blog post

+ Reasons why Pulse would not be able to run the update documentation?

  1. Check User name and password in Pulse instance settings
  2. Check CAM Namespace (It is case sensitive)
  3. Restart Pulse services if you added a new TM1 instance.
  4. Pulse version prior 5.4.2 does not support new SSL certificates
  5. Pulse may not be able to reach the TM1 data folder
  6. Pulse can't find TM1 bin folder

More information in this blog post

 

 

Pulse System Requirements

Server Requirements

  • Windows 2008 or later
  • .NET Framework 4.6.1
  • Min 300mb of disk space
  • Max 1.1 GB of RAM
  • CPU: < 1% during normal operations.


Rich Client Requirements

  • Windows 7 or later
  • .NET 4.6.1 Framework
  • 50mb disk space


Web Browser

  • Internet Explorer 9+
  • Any other modern browser: Firefox, Chrome, Safari, etc.

Data Storage and Retention

  • Data is stored in embedded databases.
  • Pulse minimises the amount of data stored by only storing aggregate data (by default in 15 minute blocks)
  • Data growth is dependent on the number of TM1 users. Expect yearly data growth of approximately 50-100mb per 100 users per annum.
  • All data historical data is kept in the databases by default.


Source Control

  • Changes to the TM1 models are stored in Git (http://git-scm.com/) repositories.
  • All historical changes are kept within the repository.