| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMBI logs / broker history / audit trail |
« View previous topic :: View next topic » |
| Author |
Message
|
| Ramphart |
 Posted: Wed Nov 25, 2009 1:54 am Post subject: WMBI logs / broker history / audit trail |
 |
|
Disciple
Joined: 21 Jul 2004
Posts: 150
Location: South Africa, JHB
|
Hi,
I'm in the process of migrating projects, deployed flows, deployed message sets in our production server environment to a new production server.
Old server :- Windows Platform
- Message Broker 6 (Ver 6.0.0.1)
- Toolkit 6.0.0.1
- Platform: Windows XP Professional
- DB2 Enterprise Server Edition 8.1.7
New Server:- Windows Platform
- Message Broker 6.1 (Ver 6.1.0.1)
- Toolkit 6.1.0
- Platform: Windows XP Professional
- DB2 Enterprise Server Edition 9.1.300.257
This migration has been running for a few month and as flows / messages sets are migrated to the new server, the excecution groups are being cleaned up / deleted from the old server.
Are there any Message Broker audit trails / logs / DB2 entries which I can pull from the two production servers? The information i'm looking for includes when certain execution groups stop running on one server and moved to the new server. When flows & message sets deployed within an execution groups were stopped or maybe removed from the execution groups etc
Any help will be much appreciated
Tx
_________________
Applications Architect |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Wed Nov 25, 2009 4:02 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
You should make sure you're on the latest fixpack - V6.1.0.1 is quite old. However, in that fixpack level, various messages will get published to the syslog when things happen (e.g. BIP2201 - execution group start).
As of v6.1.0.3, the syslog will also (by default) give you a lot more information - such as when execution groups and message flows are changed, started and stopped.
Finally, V7 contains an administration log, visible in the MBX and through CMP applications, which describes all attempted and applied changes to the broker's configuration, including starts and stops, and when they occurred and by whom. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
