| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| How to increase MQ error log file after creating qmanager |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vitor |
 Posted: Fri Mar 20, 2015 6:38 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| amitjain wrote: |
Hi Vitor,
Thanks for suggesting best practices for capturing authority events.
I am planning to do following things.
1) Enable authority events for queue manager
/app/mqm/bin/runmqsc TEST_QM
display QMGR ALL
ALTER QMGR AUTHOREV(ENABLED)
end
2)Enable application to consume messages SYSTEM.ADMIN.QMGR.EVENT
and raise alerts. |
I think you'll find this a much better solution to the requirement in the long run.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| amitjain |
| Posted: Fri Mar 20, 2015 6:42 am Post subject: |
|
|
Apprentice
Joined: 14 Jan 2015
Posts: 39
|
|
| Back to top |
|
|
| amitjain |
| Posted: Fri Mar 20, 2015 6:44 am Post subject: |
|
|
Apprentice
Joined: 14 Jan 2015
Posts: 39
|
Thanks Vitor.
Could you please suggest me some link for best practices for MQ setup and development. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Mar 20, 2015 6:49 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| amitjain wrote: |
| Could you please suggest me some link for best practices for MQ setup and development. |
Generally? That's a very broad set of topics, given the number of ways you can deploy the MQ software, and the number of use cases for applications. Want to narrow it down a bit?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| amitjain |
| Posted: Fri Mar 20, 2015 7:27 am Post subject: |
|
|
Apprentice
Joined: 14 Jan 2015
Posts: 39
|
Can you suggest best practices for auditing and monitoring.
From forum I have learned below best practices , sharing here for other people reference and correct me if it is not the best practice or correct way
1) what message sent/receive [ I have create alias queues so keeping copies of each message sent/receive and reading it in Splunk application as in /out queue]
2) what authorisation failing [I have enabled authority events and reading it in splunk application]
3) what groups [ I have created one group of sender application users and one group for receiving application users , one group for IT people to monitor]
4) monitoring [ I have created shell scripts to monitor
mq_channel_status.sh
mq_sneder_app.sh
mq_sender_ip.sh
mq_sender_user.sh
mq_listenerport.sh
mq_receiver_app.sh
mq_receiver_ip.sh
mq_receiver_user.sh
mq_qm_status.sh
mq_receive_unprocess_msg_count.sh
mq_send_unprocess_msg_countsh
and integrated in nagios tool to check in every 5 minute.
] |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
