Subject: Re: Recommended way to define instance properties
@Stephen I would like to also point you to broker-properties.
you can start a broker with :
./artemis run --properties
Where BeanUtils can be used through the properties file to customize
anything on top of broker.xml
Some users have been
@Stephen I would like to also point you to broker-properties.
you can start a broker with :
./artemis run --properties
Where BeanUtils can be used through the properties file to customize
anything on top of broker.xml
Some users have been using that to have a single broker.xml on all
their
2.27.0 included the addition of JAVA_ARGS_APPEND for the command run
by the startup script. You should be able to use that env variable
more simply to make additions to the startup args, e.g inline before
calling the script, since it isnt used for anything else unlike the
JAVA_ARGS one.
On Fri, 18
You should either keep doing these changes manually after the upgrade,
or keep these variables in a calling script.
if you can think of a better way to do this? perhaps a new properties
files for custom modifications? but if you keep these variables in a
caller's that's pretty much all the sam
My organization had been using artemis.profile to define additional instance
parameters eg:
RAVE_MIRROR_CONNECTION_STR=tcp://artms1.atl.raveu.net:5672
RAVE_MIRROR_NAME=ATL
RAVE_MIRROR_USER=rave
RAVE_MIRROR_PASSWORD=password
RAVE_CONFIG_DIR=/rave/artemis/deploy/example
# Rave environment settings
