|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Monitoring adapters |
« View previous topic :: View next topic » |
Author |
Message
|
ajomillar |
Posted: Fri Apr 01, 2005 8:30 am Post subject: Monitoring adapters |
|
|
 Centurion
Joined: 22 Aug 2003 Posts: 121 Location: Milwaukee, WI
|
We have several types of adapters in our integration architecture. In short, they either read/write from/to a database and read/write from/to a queue. However, there has been some differences in how to monitor these applications. We work in a distributed environment, primarily Windows and AIX. Candle is used for MQ monitoring but what about these adapters? Any thoughts or solutions? I know about the Java Service Wrapper. When adapters run unattended and a failure occurs, we'd like operations to receive the issue and respond to it. There is talk of using a scheduler (such as Control-m) to manage the execution of the adapters and, thereby, applying an operational harness to an adapter. Is this a best practice for a data center? |
|
Back to top |
|
 |
ajomillar |
Posted: Mon Apr 18, 2005 8:26 am Post subject: |
|
|
 Centurion
Joined: 22 Aug 2003 Posts: 121 Location: Milwaukee, WI
|
I suppose there are system management solutions available to monitor Java applications. Can anyone suggest a good one based on their experiences? Or is monitoring java apps still a challenge? |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Apr 18, 2005 8:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Depends on the Java application and the environment that app is running in.
If the app is running in WebSphere, there are a lot of performance/monitoring stuff available through JMX.
And these days, I think that a well behaved enterprise java app should have app specific information exposed through either a pub/sub or through JMX. But this is mainly my opinion. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
ajomillar |
Posted: Fri Apr 22, 2005 12:00 pm Post subject: |
|
|
 Centurion
Joined: 22 Aug 2003 Posts: 121 Location: Milwaukee, WI
|
The adapters run in a distributed environment (primarily, Windows and AIX). None running in WAS. For pub-sub, the adapter would publish errors to a consumer such as a web app or logging process. Correct? [I've seen an IBM article about pub-sub error logging.] As for JMX, I suppose we'd need to inquire if our monitoring tools have JMX capability. We use Candle to monitor certain apps on AIX. Might be a place to start. |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Apr 22, 2005 1:02 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Are these WBI Adapters, or home-grown?
If they are home-grown it is relatively trivial to add JMX capabilities to them, or likewise yes - publish the errors to an error topic hierarchy, and have a logging consumer write them to a database (and possibly instruct Candle to escalate the error). _________________ I am *not* the model of the modern major general. |
|
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
|
|
|
|