Our Web Service is complete – now we can use soapUI to test it.
- First up, make sure everything is deployed:
- SRF - compiled and deployed to the server
- Workflow Process – Deployed through Tools and Activated through the Web Client. Double check that the Integration Object property has been set against the ‘SiebelMessage’ process property
- Web Service – click the ‘Clear Cache’ button in the Inbound Web Services view to ensure Siebel can process incoming requests
- Launch soapUI and create a new project via File > New soapUI project
- Give the project a name of ‘My Siebel Web Service’ and browse for the WSDL file that we generated last time. Leave the ‘Create Requests’ checkbox as the only one checked for now
- In the navigator on the left you’ll see you project. Beneath that, you’ll see your Web Service and the ‘port’ that we exposed in Siebel – getCustomerDetails. Beneath that is a sample request called ‘Request 1′. Double click it
- soapUI will use the WSDL to construct a SOAP message in the format Siebel will expect. This includes a handy placeholder for the ‘CustNum’ input property. Populate this will a ROW_ID of a Contact from your server environment
- Click the green ‘Submit Request’ button in the top left of the window. soapUI will use the URL that you gave in the Web Service definition, as it’s now part of the WSDL. It will submit the package via HTTP to your Siebel Web Server
- On receipt, the SWE will pass the message contents on to the appropriate object manager for processing, returning the response back to the caller
- In the right side pane of soapUI, you should shortly see a response in the format defined in the IO that we created in Part 1!
- If the response looks garbled, go to File > Preferences, HTTP Settings and uncheck ‘Accept compressed responses from hosts’
And that, as they say is that.
I hope you have enjoyed this series of articles and that you have learned a little about Web Services and their application in Siebel.
Next time, we’ll take a look at Outbound Web Services, where Siebel can be configured to consume functionality exposed through external applications.
