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 5

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 #4—Create an Alternate Route into the Web Services Platform
There is one exception to the guideline for managing the platform only through SOAP messaging. When the processing of the SOAP messages themselves by the Web services platform is not functioning correctly, it should be possible to reach the Web services platform through an alternative mechanism.

This is a good argument to provide WMI-based or JMX-based management of the Web services platform alongside the SOAP-based mechanisms proposed in this article. Many Web services platforms are themselves J2EE application servers and use custom JMX MBeans, for example, to allow you to view their condition. There are comprehensive consoles available that make use of these JMX Mbeans to show the effects of the Web services on the underlying J2EE application server. These can be used in conjunction with the Web services management platform in normal operation to give another view of the system. The status of the Java beans or servlet objects that make up the implementation of the Web service at the J2EE level can be viewed through these tools. WMI-aware tools provide a similar capability in the .NET world.



Comment and Contribute

 

 

 

 

 


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

 

 

Sitemap