Hi Jean-Baptiste,

Thanks a lot for your answer.

Our ActiveMQ installation won't use any TLS, but will have authentication 
(using the simple authentication plugin) and authorization. Which additional 
configuration files would be required in such a setup?

Thanks a lot for your help!

  Fabrice

________________________________
From: Jean-Baptiste Onofre <j...@nanthrax.net>
Sent: 12 June 2021 05:37
To: users@activemq.apache.org <users@activemq.apache.org>
Subject: Re: Roundup of the configuration files

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.


Hi,

Basically, for a simple bin/activemq console start, by default (without 
authentication), you just need

- activemq.xml (broker config)
- jetty.xml (jetty container used by admin web console)
- log4j.properties (for logging config)
- logging.properties (can be removed if you don’t use JUL)

All the rest is used when SSL is enabled, when authentication is enabled.

I’ve started some cleanup for 5.17.0 having dedicated folders per "use".

Regards
JB

> Le 11 juin 2021 à 18:20, Fabrice Triboix <fabrice.trib...@armedia.com> a 
> écrit :
>
> Hello everyone,
>
> I am looking at the official ActiveMQ tarball 
> (https://archive.apache.org/dist/activemq/5.16.2/apache-activemq-5.16.2-bin.tar.gz)
>  and I would like to understand how ActiveMQ is configured.
>
> In the "conf" directory, I can see the following files:
>
>  *   activemq.xml
>  *   broker.ks
>  *   broker-localhost.cert
>  *   broker.ts
>  *   client.ks
>  *   client.ts
>  *   credentials-enc.properties
>  *   credentials.properties
>  *   groups.properties
>  *   java.security
>  *   jetty-realm.properties
>  *   jetty.xml
>  *   jmx.access
>  *   jmx.password
>  *   log4j.properties
>  *   logging.properties
>  *   login.config
>  *   users.properties
>
> I would like to know what each of these configuration files do, and whether 
> they are required or not.
>
> Many thanks,
>
>  Fabrice

Reply via email to