|
|
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-0](https://forum.cubewise.com/t/pulse-release-v6-1-0/5028)
|
|
|
|
|
|
## Important information when upgrading from Pulse v5:
|
|
|
## Important informationv5:
|
|
|
|
|
|
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 ports for all TM1 instances should be open and available to the Pulse Application Server.
|
|
|
* 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 ports for all TM1 instances should be open and available to the Pulse Application Server.
|
|
|
* A backup of the server.xml is created by Pulse in the conf folder. If you are using custom SSL certificates, you will have to bring these changes back manually after the upgrade.
|
|
|
|
|
|
## Recommendations:
|
|
|
|
|
|
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.
|
|
|
* 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.
|
|
|
|
|
|
|
|
|
## What's new
|
... | ... | |