Page Five

 
 
By eweek  |  Posted 2003-06-30 Print this article Print
 
 
 
 
 
 
 


Hartman: [Id make] similar points to a CIO/CEO—that you have pain points today integrating with your customers, partners or even your internal systems, and you have already adopted Web services, most likely, and you may not know it. Were beyond the plumbing stage; now its time to look for new ways to drive innovation, efficiencies and opportunities that create business value for their enterprise longer term.

Van Huizen: Id like to talk to the CIO after these guys have spoken to the CEO. Or it could be a message to the CEO to reinforce with the CIO. Its definitely true that applications will be built to integrate. Its definitely true that itll be much more cost-effective and much easier to connect applications across the enterprise, and its time to begin considering what the infrastructure ramifications of that are—that there is an infrastructure that needs to be in place, that pulls all this together. It wont come for free, but itll be a lot less expensive than traditional integration approaches. Start thinking about the consequences of that and building out for it.

What are some of the basic components of that infrastructure that you feel are absent or are not sufficiently robust to do what youre talking about?

Van Huizen: A global communications infrastructure that actually connects these services together, dealing with administrative and security boundaries that are already present within the enterprise, ability to get a global view of service interactions across the enterprise and effectively manage such an infrastructure.

Given the environment as it exists today, given what you see out there, whats the mistake thats most likely to be made by an enterprise that believes it needs to adopt Web services? And what is the best way to avoid making that mistake?

Bjork: I think the biggest mistake that we could conceive of—and I think its probably one that gets made fairly consistently with new technology—is when youve got a hammer, it all looks like a nail. Bite the stuff off in chunks, get definable projects where you believe there could be a rapid return on investment in terms of what youre trying to get accomplished with Web services, implement a project and then measure the results of that project. If youve gained what you should have been gaining—and we certainly believe you will—then move it on to a broader rollout and certainly look at an enterprise-level [rollout] at some point along the way.

Farrell: One thing we didnt talk about today or that was just hinted on briefly is management of all this. Now I have these Web services and theyre running. How am I keeping track of them? How am I managing that?

At Oracle, for example ... were extending functionality and adding Web services. Our Enterprise Manager, for example: Its the same program you use to manage your database clusters, the same program you use to manage your application servers, and your Web services are right there, too.

Charney: I think one of the mistakes would be to assume that Web services are not there yet and its OK to sit this one out and wait and see what happens.

It is time to start understanding that model and the level at which you invest in it—the depth and the breadth is really up to you and what makes sense for your business.

Norsworthy: I think we all sort of agree. You start small, you grow fast and you use WebSphere [laughter from all].



 
 
 
 
 
 
 
 
 
 
 

Submit a Comment

Loading Comments...
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
Rocket Fuel