Xenbeat

Hi, Thank you very much for the clear explanation. We will continue with the workaround until we upgrade to 2.8.4 or 2.9.0, at which point the source-level fix will remove the need for it. This is fully resolved for us. We will close this ticket. Thank you again for the prompt and detailed response. Best regards

JOC startup log4j2 error: parent directory /var/sos-berlin.com/js7/logs is not created by installer

Hi, thank you very much for the clarification. Your explanation was very helpful. We now understand that both approaches are technically possible, but that using a shared group is the clearer and more maintainable option, and that the same ownership layout should be applied to both Controller and JOC Cockpit. Based on your advice, we plan to use the shared-group approach for both components. This answers our question, so this ticket can be closed. Thank you again for your support.

Thank you very much for the clarification. Just to confirm, would you recommend the same ownership model for JOC as well? In our environment, JOC currently works with: home-owner=root:root data-owner=scheduler:scheduler because jetty.sh is executable by the runtime user. However, based on your recommendation for Controller, we would like to understand whether the preferred setup for JOC is also: home-owner=root:scheduler data-owner=scheduler:scheduler Or is home-owner=root:root also considered appropriate...

Question about the recommended ownership and permission model for JS7 Controller when using js7_install_controller.sh

Automatic OAuth Token Refresh for SMTP