Enterprise architecture teams overseeing SOA initiatives ideally should be working with the network operations side of the house, but it doesn’t always happen that way, says Jason Bloomberg, a senior analyst at ZapThink. “If the network and security people aren’t included on that enterprise architecture team, that can be a challenge.”

“Who’s in charge of that? It goes in the data center, so it has to be managed like any other box. But it’s an application-level device, so the application developers and enterprise architects want to be involved as well,” Bloomberg says.

It’s essential to give up some control, however, adds Ron Schmelzer, a senior analyst at ZapThink. “The network people don’t own the network, and the database people don’t own the databases: The business owns both of those things. It becomes counterproductive when issues of control over networks, applications, databases and infrastructure take precedence over meeting the needs of the business.”

Get involved early, Schmelzer adds. “Getting the network folks involved in the services definition process actually could facilitate the movement to an enterprise architecture and create a better sense of control and buy-in.”

Over the long term, network managers also can eye opportunities to move into strategic SOA roles, if they want to. ZapThink is predicting an imminent shortage of service-oriented architects who have the requisite technical and people skills needed to help their companies transform their businesses.

Architects will be in the catbird seat for the next few years, and enterprises that have SOA-savvy personnel should encourage and protect them, because other organizations will be eyeing the talent, Schmelzer and Bloomberg say.

Read more at: NetworkWorld