|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
BMC NODES FOR MQSI |
« View previous topic :: View next topic » |
Author |
Message
|
venkataramanan |
Posted: Wed Jul 02, 2003 10:37 pm Post subject: BMC NODES FOR MQSI |
|
|
 Apprentice
Joined: 18 Sep 2002 Posts: 47 Location: Chennai, India
|
Hi All,
Ia trying to implement BMC NODES in my Message flows . iam using mqsi 2.1.
I have already installed BMC patrol for Mqseries and it is already running in my environment.
Can anyone please tell me how to implement and it will be more usefull if provided with the links for reference documents.
Thanks in advance
Venkat  |
|
Back to top |
|
 |
Yanghui |
Posted: Thu Jul 03, 2003 12:03 am Post subject: |
|
|
Disciple
Joined: 08 May 2002 Posts: 151 Location: Dublin, Ireland
|
I just heard about BMC node. It seems it can help to collect some satistic data in msgflow. Do you mind to tell me what's the benefit of using this node? Thanks a lot in advance.
Sorry that I couldn't help for your problem.
Regards
-Yanghui |
|
Back to top |
|
 |
EddieA |
Posted: Thu Jul 03, 2003 10:22 am Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
The documentation that came with BMC should include instructions about how to add the Nodes to the Configuration Manager.
It involves copying a bunch of files to a few directories in WMQI. Adding the Node to your Workspace and Checking it back in. That takes care of the Control Cenre.
You then have to copy the lil files to a directory in the Broker.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
Lisa |
Posted: Thu Jul 03, 2003 8:46 pm Post subject: BMC |
|
|
Master
Joined: 07 Jun 2002 Posts: 287 Location: NJ
|
Hi All,
Where can I find the BMC nodes? Are they FREE?
Lisa |
|
Back to top |
|
 |
kirani |
Posted: Thu Jul 03, 2003 9:19 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
Lisa,
I dont think these nodes are available for free, They are bundled with the BMC Patrol for WMQI product. _________________ Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
Back to top |
|
 |
venkataramanan |
Posted: Tue Jul 08, 2003 11:56 pm Post subject: BMC NODES |
|
|
 Apprentice
Joined: 18 Sep 2002 Posts: 47 Location: Chennai, India
|
HI All,
Finally i implemented BMC nodes for MQSI it is so easy . Hey yanghui as you requested iam here with providing the featues of BMC Monitor.
General Features of BMC MQSI Monitoring Node
Monitoring Features
• autodiscover WebSphere MQ Integrator components
• monitor and graphically display of the status of WebSphere MQ Integrator components through the PATROL Console, including message brokers, execution groups, message flows, the configuration manager, the user name server, and connections
• collect message flow statistics
• publish WebSphere MQ Integrator events through the PATROL Event Manager
• display Windows and Unix application events through the Event Viewer
• monitor application events through the Event Monitor
• monitor message flows for message retry looping
• monitor WebSphere MQ Integrator control, administration, and configuration queues
Management Features
• create message brokers, configuration managers, and user name servers via a graphical interface
• start, stop, change, and delete message brokers, the configuration manager, and the user name server
• start and stop execution groups, message flows, listeners, and channels
• stop message flows across the domain
• automatically restart message brokers, the configuration manager, the user name server, and listeners according to a schedule you specify
• create and manage MQ level communications between the configuration manager and message brokers and the user name server and message brokers
• tune performance via rules for monitoring of queues, message flow statistics, message flow retry loops, and traces
Reporting Features
• generate components, statistics summary, and usage summary reports for message flows
Detailed Info Of Possible BMC MQSI Monitoring Points
MQSI Application Class
· EventMonitor monitors specified application events and tracks events, warns, or alarms according to event monitor settings
MQSI_BROKER Application Class
· AdminQDepth monitors the number of messages on the admin queue of the queue manager associated with the message broker the command server must be running in order for this parameter to be updated properly
· Availability indicates whether the message broker is available (online) or not (offline)
· AvgMsgFlowDuration monitors the average message flow duration of the message flows under this broker; this average is measured over the last statistics collection discovery cycle
· AvgMsgFlowSize monitors the average message flow size of the input messages to the message flows under this broker; this average is measured over the last statistics collection discovery cycle
· CommandServer indicates whether the command server is available (online) to the message broker's queue manager or not (offline)
· ControlQDepth monitors the number of messages on the control queue of the queue manager associated with the message broker the command server must be running in order for this parameter to be updated properly
· MaxMsgFlowDuration monitors the maximum message flow duration of the message flows under this broker; the duration is measured over the last statistics collection discovery cycle
· MaxMsgFlowSize monitors the maximum size of the input messages to the message flows under this broker; the size is measured over the last statistics collection discovery cycle
· QMgrListener monitors whether or not the listener associated with the broker's queue manager is active
· StatsCollection collects the message flow statistics that are displayed by statistics parameters for message brokers, execution groups, and message flows
· TotMsgFlowCount monitors the total message flow count of the message flows under this broker; the count is measured over the last statistics collection discovery cycle
· TotMsgFlowDuration monitors the total message flow duration of the message flows under this broker; the duration is measured over the last statistics collection discovery cycle
· TotMsgFlowSize monitors the size of the input messages to the message flows under this broker; the size is measured over the last statistics collection discovery cycle
MQSI_EXEC_GROUP Application Class
· Availability indicates whether the execution group is available (online) or not (offline)
· AvgMsgFlowDuration monitors the average message flow duration of the message flows under this execution group; this average is measured over the last statistics collection discovery cycle
· AvgMsgFlowSize monitors the average message flow size of the of the input messages to the message flows under this execution group; this average is measured over the last statistics collection discovery cycle
· MaxMsgFlowDuration monitors the maximum message flow duration of the message flows under this execution group; the duration is measured over the last statistics collection discovery cycle
· MaxMsgFlowSize monitors the maximum size of the input messages to the message flows under this execution group; the size is measured over the last statistics collection discovery cycle
· TotMsgFlowCount monitors the total message flow count of the message flows under this execution group; the count is measured over the last statistics collection discovery cycle
· TotMsgFlowDuration monitors the total message flow duration of the message flows under this execution group; the duration is measured over the last statistics collection discovery cycle
· TotMsgFlowSize monitors the size of the input messages to the message flows under this execution group; the size is measured over the last statistics collection discovery cycle
· TraceActive indicates whether an execution group trace is active or not
MQSI_MSG_FLOW Application Class
· Availability indicates whether the message flow is available (online) or not (offline)
· AvgMsgFlowDuration monitors the average message flow duration for this message flow; this average is measured over the last statistics collection discovery cycle
· AvgMsgFlowSize monitors the average message flow size of the input message to this message flow; this average is measured over the last statistics collection discovery cycle
· LoopDetected indicates whether or not a message flow retry loop has occurred
· MaxMsgFlowDuration monitors the maximum duration of this message flow; the duration is measured over the last statistics collection discovery cycle
· MaxMsgFlowSize monitors the maximum size of the input message to this message flow; the size is measured over the last statistics collection discovery cycle
· TotMsgFlowCount monitors the total message flow count of this message flow; the count is measured over the last statistics collection discovery cycle
· TotMsgFlowDuration monitors the total message flow duration of this message flow; the duration is measured over the last statistics collection discovery cycle
· TotMsgFlowSize monitors the size of the input message to this message flow; the size is measured over the last statistics collection discovery cycle
· TraceActive indicates whether a message flow trace is active or not
MQSI_STATSLOG Application Class
· AvgDuration monitors the amount of time it takes a message to travel from the
· StartStats node to the EndStats node in a message flow; this duration is averaged over the last statistics collection discovery cycle
· AvgSize monitors the size of a message when it reaches the EndStats node in a message flow; the size is averaged over the last statistics collection discovery cycle
· Count monitors the number of times a message passes from the StartStats node to the EndStats node in a message flow during the statistics collection discovery cycle
MQSI_CONFIG_MGR Application Class
· Availability indicates whether the configuration manager is available (online) or not (offline)
· CommandServer indicates whether the command server is available (online) to the configuration manager's queue manager or not (offline)
· ConfigQDepth monitors the number of messages on the configuration queue of the queue manager associated with the configuration manager the command server must be running in order for this parameter to be updated properly
· QMgrListener monitors whether or not the listener associated with the configuration manager's queue manager is active
MQSI_USER_NAME Application Class
· Availability indicates whether the user name server is available (online) or not (offline)
· CommandServer indicates whether the command server is available (online) to the user name server's queue manager or not (offline)
· QMgrListener monitors whether or not the listener associated with the user name server's queue manager is active
MQSI_CONNECTION Application Class
· Availability indicates whether the connection is available (online) or not (offline)
With regards
venkat  |
|
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
|
|
|
|