Tip

Web services watchdogs


Guest Commentary

Web services watchdogs
Web services will only become the norm if the users can be assured a level of service. They will not be deployed in earnest unless the operations department is confident that they can provide this level of service. The operations department need tools to monitor the Web services and to react to a situation before the user becomes aware of a drop in the service level. This is complex when the total service is provided by a bevy (is that a suitable collective noun?) of Web services written by and provided by different departments and enterprises.

I have spent some hours today trying to find out why an e-mail a company sent me did not arrive; this is not a Web services problem, but it should be simpler to resolve than a Web services problem. As many of you will be aware, tracking missing e-mails is not a trivial problem. My machine did not receive it, the ISP did not bounce the message, nor it appears did they receive it, but the sender is certain they sent it so who is to blame? Several e-mails and phone calls between the three main parties confirmed several possible reasons that did not cause the problem. Several tests removed other possible reasons. The problem has not been resolved but there is a fair chance that it will not happen tomorrow and we will never know why it did not work today. This problem resolution is an expensive, time consuming and frustrating process.

    Requires Free Membership to View

It would not be practical to do it for a bevy of WS.

What tools does an operations manager need to automatically support Web services? Firstly, they need to be able to ensure that the individual Web service and the platform it sits on are performing correctly. This is really no different to system management of traditional applications and the same tool can still be used. The next level is monitoring the performance that one Web service supplies to another and checking that it meets the service level agreed between the two services. Actional Looking Glass and, the recently announced, CA Unicenter Web Services Distributed Management (WSDM) both assist in this space.

These tools measure the performance of running processes, so will only detect a problem when a new process runs. If the Web service is unavailable, the time to fix the problem will be considerably and will adversely affect the calling Web service or end user. This will mean at least one unhappy client but is likely to mean a lot more as new requests pile up. To be really effective there is a need for a monitoring tool to discover the problem before another service or user is impacted. The only way to do this is to run synthetic transaction that 'ping' the service to check that it is still there. Actional have just announced their Watchdog product that creates and monitors such synthetic transactions. It can be used in two ways, firstly just to ping a local service to ensure that it is still available. The second use is to initiate the 'ping' from a remote service to check that the service is accessible and has a response time within the SLA from the remote site.

Watchdog is just the latest in a series of new functions that are needed to fully manage Web services. We expect further functions to be added as Web services become mainstream. One obvious extension would be the ability to include business understanding in the monitoring, for example the SLA for a Gold Card customer would be different to a standard card.


Copyright 2004. Originally published by IT-Director.com, reprinted with permission. IT-Director.com provides IT decision makers with free daily e-mails containing news analysis, member-only discussion forums, free research, technology spotlights and free on-line consultancy. To register for a free e-mail subscription, click here.

For more information:

  • Looking for free research? Browse our comprehensive White Papers section by topic, author or keyword.
  • Are you tired of technospeak? The Web Services Advisor column uses plain talk and avoids the hype.
  • For insightful opinion and commentary from today's industry leaders, read our Guest Commentary columns.
  • Hey Codeheads! Start benefiting from these time-saving XML Developer Tips and .NET Developer Tips.

  • Visit our huge Best Web Links for Web Services collection for the freshest editor-selected resources.
  • Visit Ask the Experts for answers to your Web services, SOAP, WSDL, XML, .NET, Java and EAI questions.
  • Couldn't attend one of our Webcasts? Don't miss out. Visit our archive to watch at your own convenience.
  • Choking on the alphabet soup of industry acronyms? Visit our helpful Glossary for the latest lingo.
  • Discuss this article, voice your opinion or talk with your peers in the SearchWebServices Discussion Forums.

This was first published in March 2004

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.