In my case, I think success has been limited.  On the bright side, the group within our operations area that are "managing" web services was responsible for our application servers, both for internal and external facing apps.  They are still taking a very application server centric viewpoint, however, and I think there's a lot more that can be done to manage the environment when a red light isn't going off.

As for the mainframe side of things, I've thought about this and there is one big advantage that may be out there for the taking.  If you have a large batch cycle that the mainframe people maintain, this is a big orchestrated process.  The model they have for managing that process may be exactly what is needed to manage the future world of BPM and orchestrated processes.  I haven't done any analysis to validate this theory, but I'm quite confident that there has to be applicable techniques for managing the BPM world.

-tb

On Aug 14, 2006, at 5:29 PM, Erik van Gilder wrote:

Hi,

Have you had much success including your existing 7x24 operations
staff in managing your "SOA" environment, and, if so, to what do you
attribute your success? I'm working in a large centralized IT
operations where the 7x24 monitoring and management of the computing
environment is the responsibility of an enterprise command center. The
command center has deep roots in a mainframe operations and continues
to struggle with the e-commerce infrastructure. I'd like to see the
operations staff help monitor and manage the environment otherwise the
developers will bear a heavy burden. Any thoughts?

In our case, the toolset includes WebMethods, WebSphere and Tivoli,
but I believe the problem to be tool-independent.

Thanks,
Erik


__._,_.___


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to