Focus on the manageability of enterprise-level services

Http://spaces.msn.com/members/flierlu/Blog/cns! 1pQ1oe7hJhEc4MgjNgGwRvvA! 131. entry

Enterprise Services with the. NET Framework actually misses a very important topic, that is, the manageability support for Enterprise-level Services. One of the most important improvements in JSE 5 is the direct integration of support for the JMX standard, which greatly enhances service availability. JBoss designers once commented that JBoss 4's success depends largely on the JMX-based microkernel structure design, JMX also plays a role in the actual service container and management mechanism in the JBoss implementation. Although general enterprise-level applications do not have to be flexible enough to be managed by similar JMX mechanisms, it is indeed necessary to provide monitoring and management support for services based on the JMX mechanism. The vast majority of engines and services in the Java camp are successively providing JMX support and integration; almost all of the server-side products of the MS itself are also embedded with the support of WMI and Performance Monitor.

On Windows, JMX corresponds to the WMI architecture. It defines its Metadata model through a mechanism similar to the snmp mib table at the underlying layer, and provides access and query through a mechanism similar to LDAP at the upper layer. It also provides a flexible event notification mechanism and a variety of auxiliary development tools. For concepts and Applications of WMI, see A Simple, Powerful Tool for Scripting Windows Management Administering Windows and Applications development SS Your Enterprise. NET provides very easy-to-use encapsulation and supports System. management Lets You Take Advantage of WMI APIs within Managed Code Instrument and Monitor Your ASP. NET Apps Using WMI and MOM 2005 but WMI lacks good support for Distributed System Monitoring compared with JMX. I don't know if it's because the MS has put this feature in a separate MOM (Microsoft Operations Manager) product for sale, so deliberately don't add support: S Monitoring in. NET Distributed Application Design uses Microsoft Operations Manager 2005 for monitoring. NET application but the overall MS to people's feeling is, in the enterprise application level think not quite clear, often see JEE camp what is good stuff, just copy it to achieve it. However, I have never figured out a problem. It is totally different for enterprise-level applications that have functions and can be used. After all, it is unrealistic to expect every MS architecture designer to be familiar with all of its technologies. Despite the seemingly convenient and complicated packaging and tools, they can alleviate this problem. However, in the long term, they will only make everyone lazy to use the default configuration, although the efficiency is low, I am able to work, but I don't know why. Windows enterprise applications, from DNA to the present, is still a half-dead (at least in China), MS should be a good review of their related strategies.