Necessary Actions When Updating or Upgrading to 6.12
Necessary Actions When Updating/Upgrading
This page describes the actions that you must manually execute when updating from version x.y.z to a newer version. It also lists things that you must pay special attention to. An update to a new version that skips some previous versions is possible and does not require updating to each version in between. However, in this case you must carry out all the actions from your previous version to the target version in the order listed here.
5.20 --> 6.0
For systems that have been upgraded from enaio redline 4.x to enaio redline / yuuvis®RAD 5.x: Before upgrading to yuuvis® RAD 6.0, you must have upgraded to the last hotfix of version 5.20 (see Necessary Actions When Updating or Upgrading to 5.20).
- Further manual steps are mandatory. See How To Upgrade To yuuvis RAD 6.0 for a step-by-step guide.
6.2 --> 6.4
- The default transaction timeout of the JBoss needs to be raised:
- Edit the file <core-service>\standalone\configuration\standalone-full-ha.xml.
- Find the subsystem 'transactions:5.0' and there the 'coordinator-environment'.
- Add the parameter 'default-timeout="86400"' to the 'coordinator-environment'.
- The section should now look as shown below:
- The default transaction timeout of the JBoss needs to be raised:
6.10 --> 6.12
- The usage of the root user for connecting the microservices to the core-service has been replaced by a shared secret API key that is used to authenticate for the core-service's internal system user that always has full rights.
Please see "How to enable system user login for microservices" for instructions on configuring the shared secret API key.
- The usage of the root user for connecting the microservices to the core-service has been replaced by a shared secret API key that is used to authenticate for the core-service's internal system user that always has full rights.