Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


advertisement
 

Learn the Eight Principles of Web Services Management : Page 7

So now that you know how important foresight and planned management are to the success of your organization's Web services transition, the next step is knowing what you need to squeeze out of your management platform. We give you practical advice in eight easy steps.


advertisement
Principle #6—Distinguish Platform Management Issues from those that are Specific to the Web Service
Whether J2EE or .NET is used as the platform, there are many parts that must perform properly for a Web service to function. Should there be a problem with the Web services platform environment, such as running out of memory or disk space, the Web services in that environment would likely begin to fail. Therefore, any overall management strategy must first conclude whether the Web services platform is running correctly before diagnosing the state of the Web services within it. J2EE and .NET management consoles go part of the way to fulfilling this requirement. However they do not have visibility of individual services within their containers today.

This can only be achieved if the issues of managing the Web services platform (such as a J2EE server with its SOAP handlers) are separate from that of the Web service itself. To achieve this separation, separate instrumentation of the platform itself is required. This instrumentation should be based on the types of issues described in Principle #1 above. With confidence in the healthy state of the Web services platform, the operator can move on to diagnosing the condition of each Web service hosted on that platform.



Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap