What’s the state of operationalizing Service Oriented Architecture (SOA) monitoring and management tools? Are the typical network, systems, enterprise operations\/management centers (NOC\/SOC\/EOC\/EMC) up to speed on how to manage, monitor, triage, troubleshoot and in general understand how SOA is being used in companies that are adopting it? Should the operations center care that they have an event from something related to SOA infrastructure and respond differently than they would for a non-SOA event? Have SOA events, incidents, problems, process and workflow been thoroughly implemented in such a way that “it just works” like traditional enterprise monitoring and management? Or, are these fancy SOA monitoring and management solutions really reserved for those applications experts responsible for complex application support and development? <\/p>\n
If a client continues to struggle with fundamental e2e service monitoring and management, transaction monitoring and management or even batch job monitoring and management, what will their chances of success be for SOA monitoring and management? Could SOA and associated “service or transaction oriented monitoring” be a catalyst to shore up these other areas? Should one be tackled\/improved before starting on another? At a minimum, instituting a “service oriented” organizational structure and mentality is certainly something I’d recommend for anyone adopting broad based SOA principles.<\/p>\n
Eric Roch<\/a> offers some solid advice on SOA Monitoring and Management which highlights that there’s more need for doing the fundamentals of systems, application and service management and monitoring really well as a foundation for SOA Monitoring and Management.<\/p>\n Others (and my preferred focus area) feel that monitoring SOA should really be more closely related to monitoring what this SOA initiative and deployment’s all about – the business. Business Service Management (BSM), Business Activity Monitoring (BAM) and Business Process Management (BPM) all play a key role in helping understand how IT infrastructure, systems, applications, etc. support and impact the business’s goals and objectives. The fairly new buzzword Business Transaction Management (BTM) spearheaded by Correlsense<\/a> and OpTier<\/a> really speaks to the desired need here.<\/p>\n I feel that it’s got to be a focus on both of these areas, but with a strong preference to the “B” buzzword set since most IT organizations are likely using the “improve\/standardize\/reuse\/efficiency\/time-to-market” spin to aide in business support and justification for their SOA initiatives. That said, you’d BETTER focus on the things that the business cares about and show them tangible evidence that your SOA initiative is making things better for them. This is very possible by adopting a BSM, BAM, BPM, BTM (or a preferred combination) strategy that focuses on providing the right level of business visibility into the SOA environment and more importantly the e2e business services, applications, transactions, processes and activities. It ultimately all ties back to the service level agreements<\/a> delivered to the business anyway right?<\/p>\n What’s on the market these days for SOA Monitoring and Management? Should you get your monitoring and management tooling from your core SOA platform vendor or should you take a third party, “best of breed” approach? Are there true “vendor neutral” solutions out there? Are clients implementing SOA architectures based on multiple vendor’s technology, solutions and products?<\/p>\n\n