...
Stop the
Platform
by calling theoffline
script.Info title Example Code Block language text theme Eclipse $ ./offline <$JAVA_HOME> <$MZ_HOME> mzadmin platform Shutting down platform...done.
The Platform should be down, but to make sure it is completely down, call the
clean
script.Info title Example Code Block language text theme Eclipse $ ./clean <$JAVA_HOME> <$MZ_HOME> mzadmin platform
Start the Platform in an alternative Platform Container. The database, including its listener, must be started before the Platform, since the Platform depends on it. The CMS must execute the database
online
script in an alternative container.Info title Example $ ./online <$JAVA_HOME> <$MZ_HOME> mzadmin platform
Starting platform...done.
Note title Note! The database and its corresponding monitor/online/offline-functionality is not part of the HA solution.
- Due to the reconnection behavior of the EC/ECSAs, you do not need to restart these pico instances unless they are unavailable. However, it is recommended that you check that the workflows are behaving as expected.
Services, running in an SC (e.g. Kafka), must be restarted when the Platform has recovered. You can update the
online
script to do so by uncommenting the following line:Code Block #cmd=$cmd;mzsh service restart --publish-only
Scroll ignore scroll-viewport false scroll-pdf true scroll-office false scroll-chm true scroll-docbook true scroll-eclipsehelp true scroll-epub true scroll-html false Next: