Biggest challenge I've seen is when you start having Async processes or having elements (such as Spring) that use a lot of config/meta-data to drive the environment. This makes it very difficult to apply traditional IT solutions of step through debugging et al into problem resolution.

I don't have a solution (yet) but its a significant challenge that shouldn't be overlooked.

There is one concept however around dynamic Services (those which are changed on a regular basis) that these shouldn't be maintained in a traditional way but continually modified by a development team as a series of Service mini-projects.

It is a bit fustrating that while companies have focused on getting new products out the door for developers but haven't solved the testing and maintainance challenge.

Steve


On 15/08/06, Gregg Wonderly <[EMAIL PROTECTED]> wrote:

Erik van Gilder wrote:
> 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?
...

> 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.

What problems are they having? Not reacting? Not interpreting information
correctly for root cause analysis? Tools which can not be altered to depict new
information forms which are learned about after each failure senario is
understood? Something else?

Gregg Wonderly


__._,_.___


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to