Although all enterprises are different, a good rule of thumb is to staff each integration server required with one administrator...somebody who can change and maintain the server as the enterprise's needs grow or change.
Re: the second part of your question, wow, don't panic. If you are talking all new applications, then you'll have to build in the resources to Web service-enabled those applications at the start of their life, and then a layer of staff to deal with the inevitable issues as they function in run-time. The more applications linked using Web services, the more maintenance resources you'll need.
The introduction of Web services, as far as predicting the number of resources, is easy. It's just simple application development metrics, predicting the amount of time required to design, build and test an application. Building Web services into applications is nothing more than an application development exercise.
In some cases you'll have existing applications where you can't justify the amount of work required to expose its services as Web services, or it's just impossible. In those cases you'll need middleware to translate the application services. Work with the vendors, they will guide you as to the amount of maintenance required.
Dig Deeper on Topics Archive
Related Q&A from David Linthicum
David Linthicum explains what advanced business application programming (ABAP)/4 means. Continue Reading
David Linthicum defines Service Component Architecture (SCA) and Service Data Objects (SDO) and explains how to best build these components to enable... Continue Reading
David Linthicum explains how it is possible that Apache Tomcat is both a Web server and an application server. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.