This article is a mirror article of machine translation, please click here to jump to the original article.

Architect_Programmer_Code Agriculture Network»Architect › Programming › Other programming › Set the user name and password for the ACTIVEMQ theme and queue
View: 8303|Reply: 0

Set the user name and password for the ACTIVEMQ theme and queue

[Copy link]
Posted on 11/21/2017 1:53:20 PM | | | |
Modify the file %ACTIVEMQ_BASE%/conf/activemq.xml, the username and password are stored in the file %ACTIVEMQ_BASE%/conf/credentials.properties,



activemq.xml details are as follows:

<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- START SNIPPET: example -->
<beans
xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">

<!-- Allows us to use system properties as variables in this configuration file -->
<bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property name="locations">
<value>file:${activemq.conf}/credentials.properties</value>
</property>
</bean>

<!-- Allows log searching in hawtio console -->
<bean id="logQuery" class="org.fusesource.insight.log.log4j.Log4jLogQuery"
lazy-init="false" scope="singleton"
init-method="start" destroy-method="stop">
</bean>

<!--
The <broker> element is used to configure the ActiveMQ broker.
-->
<broker xmlns="http://activemq.apache.org/schema/core" brokerName="localhost" dataDirectory="${activemq.data}" useJmx="true">

<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry queue=">" producerFlowControl="true" memoryLimit="1mb">
<!-- The constantPendingMessageLimitStrategy is used to prevent
slow topic consumers to block producers and affect other consumers
by limiting the number of messages that are retained
For more information, see:

http://activemq.apache.org/slow-consumer-handling.html

-->
<!-- Distribution strategy - >
<dispatchPolicy>
<!-- Distribute sequentially - >
<strictOrderDispatchPolicy/>
</dispatchPolicy>
<!-- Recovery Strategy - >
<subscriptionRecoveryPolicy>
<!-- Recover only the last message -->
<lastImageSubscriptionRecoveryPolicy/>
</subscriptionRecoveryPolicy>
<pendingQueuePolicy>
<!-- First saves the message reference in memory, and if the memory usage is maxed out, the message reference is saved in a temporary file -->
<fileQueueCursor/>
</pendingQueuePolicy>
<pendingMessageLimitStrategy>
<constantPendingMessageLimitStrategy limit="1000"/>
</pendingMessageLimitStrategy>
</policyEntry>

<!-- Resume – >
<policyEntry queue="PER.>" producerFlowControl="true" memoryLimit="10mb">
<!-- The constantPendingMessageLimitStrategy is used to prevent
slow topic consumers to block producers and affect other consumers
by limiting the number of messages that are retained
For more information, see:

http://activemq.apache.org/slow-consumer-handling.html

-->
<!-- Distribution strategy - >
<dispatchPolicy>
<!-- Distribute sequentially - >
<strictOrderDispatchPolicy/>
</dispatchPolicy>
<!-- Recovery Strategy - >
<subscriptionRecoveryPolicy>
<!-- Recover only the last message -->
<lastImageSubscriptionRecoveryPolicy/>
</subscriptionRecoveryPolicy>
<pendingQueuePolicy>
<!-- First saves the message reference in memory, and if the memory usage is maxed out, the message reference is saved in a temporary file -->
<fileQueueCursor/>
</pendingQueuePolicy>
<pendingMessageLimitStrategy>
<constantPendingMessageLimitStrategy limit="1000"/>
</pendingMessageLimitStrategy>
</policyEntry>

<!-- Enterprise - >
<policyEntry queue="COM.>" producerFlowControl="true" memoryLimit="10mb">
<!-- The constantPendingMessageLimitStrategy is used to prevent
slow topic consumers to block producers and affect other consumers
by limiting the number of messages that are retained
For more information, see:

http://activemq.apache.org/slow-consumer-handling.html

-->
<!-- Distribution strategy - >
<dispatchPolicy>
<!-- Distribute sequentially - >
<strictOrderDispatchPolicy/>
</dispatchPolicy>
<!-- Recovery Strategy - >
<subscriptionRecoveryPolicy>
<!-- Recover only the last message -->
<lastImageSubscriptionRecoveryPolicy/>
</subscriptionRecoveryPolicy>
<pendingQueuePolicy>
<!-- First saves the message reference in memory, and if the memory usage is maxed out, the message reference is saved in a temporary file -->
<fileQueueCursor/>
</pendingQueuePolicy>
<pendingMessageLimitStrategy>
<constantPendingMessageLimitStrategy limit="1000"/>
</pendingMessageLimitStrategy>
</policyEntry>

<!-- Job fair – >
<policyEntry queue="RECR.>" producerFlowControl="true" memoryLimit="10mb">
<!-- The constantPendingMessageLimitStrategy is used to prevent
slow topic consumers to block producers and affect other consumers
by limiting the number of messages that are retained
For more information, see:

http://activemq.apache.org/slow-consumer-handling.html

-->
<!-- Distribution strategy - >
<dispatchPolicy>
<!-- Distribute sequentially - >
<strictOrderDispatchPolicy/>
</dispatchPolicy>
<!-- Recovery Strategy - >
<subscriptionRecoveryPolicy>
<!-- Recover only the last message -->
<lastImageSubscriptionRecoveryPolicy/>
</subscriptionRecoveryPolicy>
<pendingQueuePolicy>
<!-- First saves the message reference in memory, and if the memory usage is maxed out, the message reference is saved in a temporary file -->
<fileQueueCursor/>
</pendingQueuePolicy>
<pendingMessageLimitStrategy>
<constantPendingMessageLimitStrategy limit="1000"/>
</pendingMessageLimitStrategy>
</policyEntry>

<!-- Micro-recruitment -->
<policyEntry queue="MCOM.>" producerFlowControl="true" memoryLimit="10mb">
<!-- The constantPendingMessageLimitStrategy is used to prevent
slow topic consumers to block producers and affect other consumers
by limiting the number of messages that are retained
For more information, see:

http://activemq.apache.org/slow-consumer-handling.html

-->
<!-- Distribution strategy - >
<dispatchPolicy>
<!-- Distribute sequentially - >
<strictOrderDispatchPolicy/>
</dispatchPolicy>
<!-- Recovery Strategy - >
<subscriptionRecoveryPolicy>
<!-- Recover only the last message -->
<lastImageSubscriptionRecoveryPolicy/>
</subscriptionRecoveryPolicy>
<pendingQueuePolicy>
<!-- First saves the message reference in memory, and if the memory usage is maxed out, the message reference is saved in a temporary file -->
<fileQueueCursor/>
</pendingQueuePolicy>
<pendingMessageLimitStrategy>
<constantPendingMessageLimitStrategy limit="1000"/>
</pendingMessageLimitStrategy>
</policyEntry>

<!-- Micro job search - >
<policyEntry queue="MPER.>" producerFlowControl="true" memoryLimit="10mb">
<!-- The constantPendingMessageLimitStrategy is used to prevent
slow topic consumers to block producers and affect other consumers
by limiting the number of messages that are retained
For more information, see:

http://activemq.apache.org/slow-consumer-handling.html

-->
<!-- Distribution strategy - >
<dispatchPolicy>
<!-- Distribute sequentially - >
<strictOrderDispatchPolicy/>
</dispatchPolicy>
<!-- Recovery Strategy - >
<subscriptionRecoveryPolicy>
<!-- Recover only the last message -->
<lastImageSubscriptionRecoveryPolicy/>
</subscriptionRecoveryPolicy>
<pendingQueuePolicy>
<!-- First saves the message reference in memory, and if the memory usage is maxed out, the message reference is saved in a temporary file -->
<fileQueueCursor/>
</pendingQueuePolicy>
<pendingMessageLimitStrategy>
<constantPendingMessageLimitStrategy limit="1000"/>
</pendingMessageLimitStrategy>
</policyEntry>

<!-- Backend - >
<policyEntry queue="ERP.>" producerFlowControl="true" memoryLimit="10mb">
<!-- The constantPendingMessageLimitStrategy is used to prevent
slow topic consumers to block producers and affect other consumers
by limiting the number of messages that are retained
For more information, see:

http://activemq.apache.org/slow-consumer-handling.html

-->
<!-- Distribution strategy - >
<dispatchPolicy>
<!-- Distribute sequentially - >
<strictOrderDispatchPolicy/>
</dispatchPolicy>
<!-- Recovery Strategy - >
<subscriptionRecoveryPolicy>
<!-- Recover only the last message -->
<lastImageSubscriptionRecoveryPolicy/>
</subscriptionRecoveryPolicy>
<pendingQueuePolicy>
<!-- First saves the message reference in memory, and if the memory usage is maxed out, the message reference is saved in a temporary file -->
<fileQueueCursor/>
</pendingQueuePolicy>
<pendingMessageLimitStrategy>
<constantPendingMessageLimitStrategy limit="1000"/>
</pendingMessageLimitStrategy>
</policyEntry>
</policyEntries>
</policyMap>
</destinationPolicy>


<!--
The managementContext is used to configure how ActiveMQ is exposed in
JMX. By default, ActiveMQ uses the MBean server that is started by
the JVM. For more information, see:

http://activemq.apache.org/jmx.html
-->
<managementContext>
<managementContext createConnector="false"/>
</managementContext>

<!--
Configure message persistence for the broker. The default persistence
mechanism is the KahaDB store (identified by the kahaDB tag).
For more information, see:

http://activemq.apache.org/persistence.html
-->
<persistenceAdapter>
<kahaDB directory="E:/activemq_data"
enableJournalDiskSyncs="false"
indexWriteBatchSize="1000"
indexCacheSize="10000"
journalMaxFileLength="32mb"
/>
</persistenceAdapter>


<plugins>
<!-- Configure authentication; Username, passwords and groups -->
<simpleAuthenticationPlugin>
<users>
<authenticationUser username="${activemq.username}" password="${activemq.password}" groups="admins"/>
<authenticationUser username="${per.username}" password="${per.password}" groups="personal"/>
<authenticationUser username="${mper.username}" password="${mper.password}" groups="mpersonal"/>
<authenticationUser username="${com.username}" password="${com.password}" groups="company"/>
<authenticationUser username="${mcom.username}" password="${mcom.password}" groups="mcompany"/>
<authenticationUser username="${erp.username}" password="${erp.password}" groups="erp"/>
<authenticationUser username="${recr.username}" password="${recr.password}" groups="recr"/>
</users>
</simpleAuthenticationPlugin>

<!-- Lets configure a destination based authorization mechanism -->
<authorizationPlugin>
<map>
<authorizationMap>
<authorizationEntries>
<authorizationEntry queue=">" read="admins" write="admins" admin="admins" />
<authorizationEntry queue="PER.>" read="personal, mpersonal, company, mcompany, erp, recr" write="personal" admin="personal" />
<authorizationEntry queue="MPER.>" read="personal, mpersonal, company, mcompany, erp, recr" write="mpersonal" admin="mpersonal" />
<authorizationEntry queue="COM.>" read="personal, mpersonal, company, mcompany, erp, recr" write="company" admin="company" />
<authorizationEntry queue="MCOM.>" read="personal, mpersonal, company, mcompany, erp, recr" write="mcompany" admin="mcompany" />
<authorizationEntry queue="ERP.>" read="personal, mpersonal, company, mcompany, erp, recr" write="erp" admin="erp" />
<authorizationEntry queue="RECR.>" read="personal, mpersonal, company, mcompany, erp, recr" write="recr" admin="recr" />

<authorizationEntry topic="ActiveMQ.Advisory.>" read="personal, mpersonal, company, mcompany, erp, recr" write="personal, mpersonal, company, mcompany, erp, recr" admin="personal, mpersonal, company, mcompany, erp, recr" />
</authorizationEntries>
</authorizationMap>
</map>
</authorizationPlugin>
</plugins>

<!--
The systemUsage controls the maximum amount of space the broker will
use before disabling caching and/or slowing down producers. For more information, see:
http://activemq.apache.org/producer-flow-control.html
-->
<systemUsage>
<systemUsage>
<memoryUsage>
<memoryUsage percentOfJvmHeap="100" />
</memoryUsage>
<storeUsage>
<storeUsage limit="1 gb"/>
</storeUsage>
<tempUsage>
<tempUsage limit="100 mb"/>
</tempUsage>
</systemUsage>
</systemUsage>

<!--
The transport connectors expose ActiveMQ over a given protocol to
clients and other brokers. For more information, see:

http://activemq.apache.org/configuring-transports.html
-->
<transportConnectors>
<!-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB -->
<transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
<transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
<transportConnector name="stomp" uri="stomp://0.0.0.0:61613?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
<transportConnector name="mqtt" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
<transportConnector name="ws" uri="ws://0.0.0.0:61614?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
</transportConnectors>

<!-- destroy the spring context on shutdown to stop jetty -->
<shutdownHooks>
<bean xmlns="http://www.springframework.org/schema/beans" class="org.apache.activemq.hooks.SpringContextHook" />
</shutdownHooks>

</broker>

<!--
Enable web consoles, REST and Ajax APIs and demos
The web consoles requires by default login, you can disable this in the jetty.xml file

Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details
-->
<import resource="jetty.xml"/>

</beans>
<!-- END SNIPPET: example -->

credentials.properties:

## ---------------------------------------------------------------------------
## Licensed to the Apache Software Foundation (ASF) under one or more
## contributor license agreements. See the NOTICE file distributed with
## this work for additional information regarding copyright ownership.
## The ASF licenses this file to You under the Apache License, Version 2.0
## (the "License"); you may not use this file except in compliance with
## the License. You may obtain a copy of the License at
##
## http://www.apache.org/licenses/LICENSE-2.0
##
## Unless required by applicable law or agreed to in writing, software
## distributed under the License is distributed on an "AS IS" BASIS,
## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
## See the License for the specific language governing permissions and
## limitations under the License.
## ---------------------------------------------------------------------------

# Defines credentials that will be used by components (like web console) to access the broker

activemq.username=***
activemq.password=***

per.username=***
per.password=***

mper.username=***
mper.password=***

com.username=***
com.password=***

mcom.username=***
mcom.password=***

erp.username=***
erp.password=***

recr.username=***
recr.password=***

The above configuration found that there was an abnormality in the queue monitoring today, and finally found that the problem appeared here:



Since the account used in the queue monitoring project admin is system/manager(webapps\admin\WEB-INF\webconsole-embedded.xml



admins group, which requires permissions






Previous:activemq modifies the website management password
Next:.net/c# activemq to set the connection account and password

Related Posts
Disclaimer:
All software, programming materials or articles published by Code Farmer Network are only for learning and research purposes; The above content shall not be used for commercial or illegal purposes, otherwise, users shall bear all consequences. The information on this site comes from the Internet, and copyright disputes have nothing to do with this site. You must completely delete the above content from your computer within 24 hours of downloading. If you like the program, please support genuine software, purchase registration, and get better genuine services. If there is any infringement, please contact us by email.
Mail To:help@itsvse.com