| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Monitor the proxy servlet & http listener? |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqwbiwf |
 Posted: Mon Feb 23, 2009 3:17 pm Post subject: Monitor the proxy servlet & http listener? |
 |
|
Centurion
Joined: 21 Jul 2006
Posts: 126
|
Hi,
We are trying to monitor the connectivity between the proxy servlet and the broker in production, but none of the http traffic monitoring tools are useful so far (as it's not like monitoring a typical URL).
Client uses ExternalURL to post -> !!!!Internet!!!!! -> Our F5 -> ProxyServlet(web & app server) -> WBI
If I try to hit just the 'ExternalURL' from browser(without URI), it obviosuly returns a msg saying no matching URI. This atleast proves that the connectivity is fine. I would like to monitor this piece. When used the tools that we have, it's treating the SOAP response as a HTTP failure message and alerting us.
Could you guide me the best wy of monitoring the external url that our clients use to post data to WBI? Let me know if my question isn't clear enough! |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Feb 23, 2009 3:58 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Create a little flow that you can ping. |
|
| Back to top |
|
|
| mqwbiwf |
| Posted: Tue Feb 24, 2009 8:30 am Post subject: |
|
|
Centurion
Joined: 21 Jul 2006
Posts: 126
|
| Well, we even tried to hit an existing flow which accepts data. If it's invalid data (or even a blank), it throws a soap exception response message back. It's again being treated as a http error message. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Feb 24, 2009 8:55 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
There are monitoring statistics or events that you can monitor out of band, using whatever you use to monitor your other servlet containers, that will tell you if the ProxyServlet is active. Likewise with Broker and the bipHTTPListener.
Instead of using those, you can try to monitor things in band by calling a flow that does not do what you want in your particular situation. (this apparently is where you started and it did not work.)
You can do as I already said, and write a flow that specifically does what you want it to do from a monitoring point of view.
As a third option, you can continue asking for more help. I suspect that won't be as productive as the other two choices. |
|
| Back to top |
|
|
| bloomy |
| Posted: Tue Feb 24, 2009 11:26 am Post subject: |
|
|
Acolyte
Joined: 11 Feb 2009
Posts: 61
Location: Bloomington, IL USA
|
We had a problem of biphttplisteners going down. We had a flow in for monitoring, the flow would call https through http. In this way we could check for both http and https ports and even the httplistener is active or not.
The flow was simple http flow
httpinput------->httprequest------------>httpreply
This flow was kept in for monitoring, our automation team had written a script which would call trigger this flow periodically and when we have failure it would send out an alert.
we hit an URL and URL should should give us an output something like this
<FromWebSphereMessageBroker>You reached BRK at TIME '13:28:52.905891'</FromWebSphereMessageBroker> |
|
| 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
|
|
|
|
