As a first service we can build a simple service which returns a SOAP message with a HelloWorld text.
Drag the HTTP transport from the Technology palette to the SBProject Proxy Services lane (the left one).
The Create Proxy wizard will start and guide you to the settings.
First we choose a name for our service, comfirm the HTTP transport (the pulldown actually shows no choice) and leave Generate Pipeline enabled.
As service type we select the most easy option Any Soap, which allows us to use SOAP messages but spares us the part to configure a WSDL/XSD for now.
The pulldown shows us that both SOAP 1.1 and 1.2 are supported, but for this example we can use either.
The last step in the wizard is configuring the endpoint URI for your service. The endpoint determines the address our service consumers will have to use.
In our example: http://<servername>:<serverport>/SBProject/helloWorld
The wizard automatically generated the Pipeline so our project looks like this.
Since our HelloWorld service won’t access any back-ends we will not use the External Services lane of our project.
First we drag the Pipeline pair from the components to our pipeline
Our pipeline know shows a request and response pipeline where we can place our transformation logic.
Since we don’t access a back-end, we will just transform the SOAP message in the response pipeline.
Drag a Replace action from the components palette to the StageResponse.
Configure the Replace action to change the body (location), on root leven using the dot (.).
For Value we will use XML-content <message>HelloWorld</message> to make sure the SOAP message still contains a valid XML structure.
We select the Replace node contents, which is a best practice for SOAP messages.
This option will only replace the content of the SOAP body and prevent any namespace issues, avoid creating a non-valid SOAP body structure, etc.
The result is a simple SOAP/HTTP service which we can now deploy and test.