+ 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 versions of TM1 does Pulse support?
Pulse supports all versions of TM1 from 9.5 onwards.
+ WHAT ARE THE PULSE SYSTEM REQUIREMENTS?
- Windows 2008 or later
- .NET Framework 3.5
- 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 3.5 Framework
- 50mb disk space
- 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.
- Changes to the TM1 models are stored in Git (http://git-scm.com/) repositories.
All historical changes are kept within the repository.
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 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.
+ 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.
All of the requirements for Pulse are bundled and installed automatically except for the .NET Framework.
+ 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.
+ 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.
+ 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.