Channels ▼
RSS

JVM Languages

ESG Suggests Modeling in Dynamic SOA Apps


Application Service Management (ASM) tools typically monitor services and the underlying code components that support those services. But according to ClearApp, a vendor of ASM tools for J2EE-based composite applications, the lack of business context is the biggest limitation in today's enterprise systems and applications management solutions. The solution to this problem, says ClearApp, is the adoption of application service modeling. ClearApp is basing its position in part on the paper What's Next in Application Management: Using Modeling to Optimize Composite Applications in Dynamic Environments written by industry analyst firm Enterprise Strategy Group (ESG).

According to ESG analysts Bob Laliberte and Brian Babineau, there is a need to automate service discovery and dependency mapping to ensure that complex business services are viewed holistically within heterogeneous, n-tier application environments. In ESG's view, this gap between services and infrastructure will only become more acute as additional layers of abstraction are added by tomorrow's server virtualization and SOA middleware advances.

In the paper, ESG examines the limitations of alternatives to application service modeling. From transaction tracing to business process management to configuration management databases (CMDBs), the report argues that all fail to deliver a complete, consolidated map of the service dependencies shared among complex composite applications, their code, and infrastructure components -- from top to bottom. Similar to how modeling has been successfully deployed in network management, it now should be leveraged in application management as well. The ESG paper concludes that such a maturation of application management would provide clearer root cause analysis, swifter problem resolution, effortless change management, and improved service-level management.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video