Home >> Information Architecture >> Service Oriented Architectures

Finger-pointing inevitable without SOA management

Finger-pointing inevitable without SOA management By:  Rafael Ruffolo On: 11 May 2009 For: ComputerWorld Canada Creator

Speaking at an IBM Impact session on SOA management, Humana Inc.’s head of IT services outlines why proper management tools are the only way to avoid finger-pointing and confusion in today’s SOA environment



Email a friend   |  









Print   |   Text + / -   |  Add a Comment   |   Views: 469   |   Rating:offoffoffoffoff  (0 votes)
Rate this article on a scale of
1 to 5 stars,5 being the best.




In order to successfully manage a service-oriented architecture, IT shops need to stop playing the blame game when a problem arises, according to an IT manager at Louisville, Ky.-based Humana Inc.

The problem with most SOA environments — especially those that are mixed with legacy system environments — is the lack of insight IT administrators have when trying to manage their composite applications, said Craig Whitaker, technology manager of technical services at the health care insurance firm.

“The real change with SOA is that you don’t have the control you used to have,” he told conference attendees at last week’s IBM Impact 2009 in Las Vegas. Each application doesn’t performance one function, but rather multiple functions with dozens of other interconnected applications, Whitaker said.

More from IT World Canada

Don't tell IBM that SOA is dead

When faced with a crisis in the early days, he added, his IT shop often resorted to “problem-solving by committee.”

At Humana, it has been common to have 40 or 50 support people on troubleshooting conference call when faced with a technical issue, Whitaker said, with vendors and senior vice-presidents sometimes joining the call.

“Everybody has a stake in solving the problem and every tier support group has its own tools,” he said.

“Often times, somebody on the call will mention that ‘six months ago we had this problem and it was DB2’ and that gives everybody something they can start blaming,” Whitaker added. “If you’re a (database administrator), you might know that it’s not DB2, but because everybody thinks it is, you spent all your time trying to defend your part of the network.”

For Whitaker, instead of pointing fingers and being reactive, IT departments must be predictive and proactive.

More from IT World Canada

Five ways to avoid SOA failure

Humana has recently partnered with Melville, N.Y.-based Nastel Technologies Inc. in order to gather operational, transactional and business metrics using one tool that monitors the overall health of the IT environment.

Nastel’s AutoPilot M6 suite, which includes transaction, business activity, application performance and middleware management capabilities, aims to give IT administrators a way to find and fix problems quickly without disrupting services.


Sign up for our Newsletters
Rafael Ruffolo Rafael Ruffolo joined ComputerWorld as a staff writer in June 2007 and was the winner of a Kenneth R. Wilson award for business journalism. He is interested in government IT, copyright, virt... more

Related Articles

Related Blogs

Comments (0)

No Comments!
You are currently not logged in: Register | Login

You must be logged in to submit a comment.