Prevent EAP 7 calling jboss-cli.sh in EAP container

Environment

• Red Hat JBoss Enterprise Application Platform (EAP)
  • 7.x
  • 8.x
• Red hat OpenShift Container Platform (OCP)
  • 4.x

Issue

• How to prevent EAP 7 calling jboss-cli.sh in EAP container?
• How to prevent the EAP 7 start scripts not to overwrite the custom changes made?

Resolution

As explained on the solution EAP 7/8 CONFIG_IS_FINAL on Galleon Build for image building, EAP 7 initial scripts might change the configuration on runtime when the image starts running.
For instance, if jgroups is in the config, the server will add protocols, for instance KUBE_PING.
That's because the image must have a discovery protocol in the stack, and a CLI script is run to add it - the default scripts do this (i.e. bin/launch/ha.sh).

Therefore, by setting the environment variable CONFIG_IS_FINAL=true it prevents calling jboss-cli.sh in EAP container startup scripts - and those start-up scripts won't impose some properties.

This can be disabled by setting CONFIG_IS_FINAL for true, CONFIG_IS_FINAL=true. Given a disabled automatic configuration setting, one can set LOCAL_PING instead of KUBE_PING to disable clustering.

Related solutions

EAP 7 image clustering in OCP 4

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.