Skip to main content

Environment Restart Initiators

  • Updated

In the context of configurations, there are multiple reasons your BOC Management Office Product needs to be restarted to apply certain executed changes.

How to restart your Environment​

There are multiple ways to restart your BOC Management Office Product to apply an array of configuration changes. A restart can be triggered via Webclient or a Service restart.

Overview​

Action Additional Information Application Server Restart Web Server Restart
Adding File Types into Tomcat   ❌ ✔️
SSL Tomcat Configuration Upload of Java Keystore Files (jks) ❌ ✔️
REST Activation in Tomcat for Basic Authentication Applies only below ADONIS 14.1.14 / 15.0.9 and ADOIT versions 15.1.13 / 16.0.8 ❌ ✔️
Licence updates   ✔️ ❌
Mail Configuration Changes   ✔️ ❌
Changes in "Common" Component Settings   ✔️ ❌
Start Model Changes   ✔️ ❌
Metamodel Changes   ✔️ ❌
Confluence Cloud: Activating "CORS" Activating "CORS" during the setup process. Applies only below ADONIS 14.1.14 / 15.0.9 and ADOIT versions 15.1.13 / 16.0.8 ✔️ ❌
Management Office Integration (MOI) Interface Adaptations ✔️ ❌
Process Manager for Sharepoint: Activating "CORS" Activating "CORS" during the setup process. Applies only below ADONIS 14.1.14 / 15.0.9 and ADOIT versions 15.1.13 / 16.0.8 ✔️ ❌
Activating iFrame Feature   ✔️ ❌
System Setting Except for web module assignments ✔️ ❌
Changes in ISAPI Configuration If IIS is used ❌ ✔️
Changes on File Level   See "Changes on File Level" See "Changes on File Level"
Updates of your BOC Management Office Product A full restart is part of the regular update process of ADONIS, ADOIT or ADOGRC. ✔️ ✔️

Changes on File Level​

Any configuration changed in the following Files needs a restart:

Need Web Server Restart:

web.xml, server.xml, adoxx_web.properties

Need Application Server Restart:

adoxx_web_conf.js, server.conf

Related articles