Chris Malek is a PeopleTools® Technical Consultant with two decades of experience working on PeopleSoft enterprise software projects. He is available for consulting engagements.About Chris Work with Chris
Introducing a small but powerful PeopleSoft bolt-on that makes web services very easy. If you have a SQL statement, you can turn that into a web service in PeopleSoft in a few minutes.Read More & Purchase
This section will cover some high level planning steps, questions and estimates to give the reader an idea of the process to develop new web services.
There are several high level steps that generally occur to create new web services.
We will break those out and a few more in the section below.
For the early planning phase, there are some decisions and questions to asks.
For greenfield web services, the design is often an iterative process between the team developing the web service and the team consuming the web service. That is assuming the server team is developing web services for some specific use case and the client is already known. There are other cases where you may be developing services that are going to be used by some future unknown client(s) and you have to answer these with your own judgement.
Here are some high-level questions.
It is very important that you document these decisions in a design document to guide the development team on the vision and purpose of the web services. What is developed might be based on certain constraints that were in place. Future team members may not be aware of those constraints.
The development is where all the work happens. There are several hurdles that you have to overcome:
We touched on a few different security points in the design section. Security is very important in any application. PeopleSoft carries sensitive information. The code must be “secure”.
The testing phase can be complex depending on who and what you are integrating with.
If you are developing a web service for a client, the documentation can be extremely important for the client developers. You should document the oddities of the web service that things like schemas do not begin to be able to approach. This might be things like “cascading” prompts and interrelated fields.
Many large organizations have formal and informal code reviews. These take time but generally don’t get in the way of development other than getting them scheduled. You need to be sure you account for this in your timeline.
The actual move to production can take a few days to get done and coordinate especially if your organization has strict change control procedures.
When you are creating web service, the question is always asked: How long will it take?
This is an important planning question. The answer depends on man factors including:
First let’s assume the deliverable is a web service with medium complexity which may combined a “GET” and an “POST” (update). I put together some rough timelines in the amount of days it might take for a beginner, intermediate and expert to get that done.
|Phase||Beginner Estimated Days||Intermediate Estimated Days||Expert Estimated Days|
|Development & Unit Testing||25||10||5|
|Move to Production||1.5||1.5||1|
These numbers should give you an rough estimate of start to finish web services. I have seen these come in way over and way under this depending on many factors.