|
|
|
|
|
We are pleased to announce a new version of Pulse is now available for download from the Cubewise Forum: [forum.cubewise.com/t/pulse-release-v6-1-2](https://forum.cubewise.com/t/pulse-release-v6-1-2)
|
|
|
|
|
|
This new release comes with many optimizations to improve the connection between Pulse and TM1 and in the way Pulse manages its data. We highly encourage all our customers to upgrade to this version.
|
|
|
|
|
|
## Recommendations:
|
|
|
|
|
|
* 📢 The Pulse Monitor has been improved. It is highly recommended to upgrade the Pulse Monitor on all TM1 servers.
|
|
|
* ([Upgrading the Pulse Monitor](https://code.cubewise.com/docs/upgrading-the-pulse-monitor)).
|
|
|
* The ChoreLog and the ProcessLog tables are not going to be updated by Pulse anymore. These two tables are not used by Pulse 6 but if you are querying these tables, you can ask Pulse to continue updating them. To do that you need to update the setting **EnableProcessHistoryDB** to true (default is false) in the Pulse.cfg.
|
|
|
* It is recommended to Back-up Pulse before doing the upgrade.
|
|
|
* To use the migration features between two Pulse servers, the Pulse version needs to be the same in the two environments.
|
|
|
|
|
|
## Important information when upgrading from Pulse v5:
|
|
|
|
|
|
* It is highly recommended to read the Pulse 6 getting started guide: [code.cubewise.com/docs/getting-started-with-pulse-v6](https://code.cubewise.com/docs/getting-started-with-pulse-v6).
|
|
|
* You can’t run Pulse 5 and Pulse 6 side-by-side.
|
|
|
* The [TM1 REST API](https://code.cubewise.com/blog/enabling-the-tm1-rest-api) ports for all TM1 instances should be open and available to the Pulse Application Server.
|
|
|
|
|
|
## What's new
|
|
|
|
|
|
* The way Pulse determines the status of the TM1 instances has been optimized. To enable this enhancement, the Pulse Monitor will have to be upgraded on each server ([Upgrading the Pulse Monitor](https://code.cubewise.com/docs/upgrading-the-pulse-monitor)).
|
|
|
|
|
|
<center><img src="https://downloads.cubewise.com/web_assets/pulse-release-notes/v612/pulse-live-monitor-status.gif" style="width: 80%; height: 80%;text-align: center"/></center>
|
|
|
|
|
|
* A TM1 instance can be running but might not be monitored by Pulse due to wrong TM1 user credentials or port number not open ([Reasons why Pulse can't connect to an instance](https://code.cubewise.com/docs/reasons-why-pulse-cant-connect-to-an-instance)). A new icon showing the status of the connection from the TM1 instance to Pulse has been added to the Pulse Dashboard. Green means Pulse can connect to the TM1 instance and red means Pulse can't connect. Check the following article to understand the reasons why Pulse can't connect to a TM1 instance:
|
|
|
* [Reasons why Pulse can't connect to an instance](https://code.cubewise.com/docs/reasons-why-pulse-cant-connect-to-an-instance)
|
|
|
|
|
|
<center><img src="https://downloads.cubewise.com/web_assets/pulse-release-notes/v612/Pulse+Connection+Status.png" style="width: 80%; height: 80%;text-align: center"/></center>
|
|
|
|
|
|
* In the Pulse instance settings, it is now easier to see which TM1 instance is active or not. The Active Flag status can be seen in the list of instances. All instances with the Active flag set to false are not monitored by Pulse. It is recommended to set this flag to false for all instances which do not need to be monitored by Pulse, more information is in the following article:
|
|
|
* [Choose which instance should be monitored by Pulse](https://code.cubewise.com/docs/choose-which-instance-should-be-monitored-by-pulse)
|
|
|
<center><img src="https://downloads.cubewise.com/web_assets/pulse-release-notes/v612/Pulse+Active+Flag.png" style="width: 80%; height: 80%;text-align: center"/></center>
|
|
|
|
|
|
|
|
|
|
|
|
## Enhancements (17)
|
|
|
|
|
|
* [#2672](https://support.cubewise.com/code/pulse/issues/2672): Better management of the requests retrieved from TM1.
|
|
|
* [#3306](https://support.cubewise.com/code/pulse/issues/3306): Being able to re-run a migration package that had an issue during the execution.
|
|
|
* [#3363](https://support.cubewise.com/code/pulse/issues/3363): The way Pulse shows the TM1 instance status has been improved.
|
|
|
* [#3367](https://support.cubewise.com/code/pulse/issues/3367), [#3371](https://support.cubewise.com/code/pulse/issues/3371) & [#3565](https://support.cubewise.com/code/pulse/issues/3565): Improving the way Pulse determines the status information for instances delayed (Running, Stopped, Loading)
|
|
|
* [#3382](https://support.cubewise.com/code/pulse/issues/3382): Optimizations to handle slow-to-respond TM1 servers which contributes to the "freezing" of the dashboard.
|
|
|
* [#3499](https://support.cubewise.com/code/pulse/issues/3499): Add support for cubes and dimensions usage from Arc.
|
|
|
* [#3518](https://support.cubewise.com/code/pulse/issues/3518): The Pulse Monitor skips odd values coming from the OS.
|
|
|
* [#3612](https://support.cubewise.com/code/pulse/issues/3612): Optimizing the Pulse database by reducing the size of the CubeStats and PulseSession tables.
|
|
|
* [#3647](https://support.cubewise.com/code/pulse/issues/3647): Improving the way Pulse determines if a TM1 instance is offline.
|
|
|
* [#3635](https://support.cubewise.com/code/pulse/issues/3635): Add a warning message when TM1 instance is not supported.
|
|
|
* [#3632](https://support.cubewise.com/code/pulse/issues/3632): Cannot Migrate to PA Cloud Instance after the name change.
|
|
|
* [#3564](https://support.cubewise.com/code/pulse/issues/3564): Increasing the limit of character for the Context field.
|
|
|
* [#3540](https://support.cubewise.com/code/pulse/issues/3540): Added the Server Name of the Host Name to the pulse.log and monitor.log files.
|
|
|
* [#3536](https://support.cubewise.com/code/pulse/issues/3536): Added a ticked check box for active instances in the Pulse instance settings.
|
|
|
* [#3525](https://support.cubewise.com/code/pulse/issues/3525): Improving the error message with Pulse users does not have access to specific features.
|
|
|
|
|
|
## Fixes (11)
|
|
|
|
|
|
* [#2174](https://support.cubewise.com/code/pulse/issues/2174): Better exception handling when Pulse can't write to the Windows Event Log.
|
|
|
* [#3090](https://support.cubewise.com/code/pulse/issues/3090): Retrieval of TM1 version on New Installations or Upgrades has been fixed.
|
|
|
* [#3244](https://support.cubewise.com/code/pulse/issues/3244): Enhancements to the way Pulse handles warning messages during the execution of a package.
|
|
|
* [#3530](https://support.cubewise.com/code/pulse/issues/3530): The Pulse Monitor will create the backup folder if not there.
|
|
|
* [#3549](https://support.cubewise.com/code/pulse/issues/3549): Pulse records error logs but doesn't send an email alert.
|
|
|
* [#3556](https://support.cubewise.com/code/pulse/issues/3556): Element formatting was missing during migration.
|
|
|
* [#3575](https://support.cubewise.com/code/pulse/issues/3575): Pulse was not showing the right message when executing a migration package.
|
|
|
* [#3578](https://support.cubewise.com/code/pulse/issues/3578): When highlighting rows in Processes and Rules, the display looks misplaced.
|
|
|
* [#3624](https://support.cubewise.com/code/pulse/issues/3624): The charts' label format in the Pulse dashboard have been fixed.
|
|
|
* [#3638](https://support.cubewise.com/code/pulse/issues/3638): Credentials are not being auto-encrypted in Pulse.cfg file.
|
|
|
* [#3625](https://support.cubewise.com/code/pulse/issues/3625): The Email Alert Severity Label description has been fixed.
|
|
|
|
|
|
## Download
|
|
|
|
|
|
https://forum.cubewise.com/c/pulse/pulse-clients |
|
|
\ No newline at end of file |