Just wanted to say "Thanks" for posting this. I was looking for a good way to test a Web Service before just dumping on the third-party for testing and the only thing I could find was Oracle's JDeveloper. Then I found this. It was quick and easy to get setup and running. I am still having trouble figuring out the security, where I want the connection to go through as a specific user, not the "default" App Server user or XMLLINK user.
Glad this helped you out.
You should be able to pass the (simple) authentication information through the SOAP request header, something like:
<wsse:Security soap:mustUnderstand="1" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <wsse:UsernameToken> <wsse:Username>PS</wsse:Username> <wsse:Password>PS</wsse:Password> </wsse:UsernameToken> </wsse:Security>
You can generate the request message with the correct security settings using the generate SOAP template functionality:
PeopleTools > Integration Broker > Service Utilities > Generate SOAP Template
We are trying to integrate PS with Sharepoint. I have created the CI-Based web services and generated WSDL. The ASP.net team is able to consume the WSDL and can invoke Get/Add/Update methods. Could you please let know how to access the Delete method. I find it difficult to get any reference on this Delete. Im talking in particular about the Delete buttons we have on the PS ESS page - Phone/Email. Thanks
Hi inba
i am facing webservices UpdateData method problem
as u stated u have successully using Get/Add/Update method.
can u help me out for this problem
when i am calling UpdateData Method of Webservice in Asp.Net
getting response as 1 but respository not updated
Can u help me out for this problem.
Thanks and Regards
Ganesh
By the way you can also do this in the request properties in soapUI. Select the request then look at the bottom left - there should be a bunch of request properties available including Username and Password.
Praj, I tried using an invalid UserName and Password using the Request Properties and it has no affect on the Request results.
My real question is how you get the UserName and Password elements to appear in the header of the SOAP envelope. These elements appear when you generate the SOAP from PeopleSoft, but they do not appear when 3rd party apps such as SoapUI generate the SOAPs from the WSDL URL.
One thing I've noticed is that the web service authentication information is not shown in the XML view for the request. Try switching to the Raw view and check if it appears there? These are the two tabs on the left hand side.
Thanks for this guide. I tried doing that but credentials are missing even in RAW tab. I have tested this in SendMaster utility and their I could see credentials tab and it was working fine.
Thanks for the post about soapUI. PushToTest TestMaker is an open source test platform that repurposes soapUI tests to be functional tests, load and performance tests, and business service production monitors. A tutorial on using soapUI in TestMaker is at http://www.pushtotest.com/tutorials/soapuitutorialfull
Thanks!
-Frank
Hi
Does any body know what would be best way to delete data through Web Service? We used to do it Collection.deleteItem(i) for CI but with CI-Based Web Service am unable to find a delivered way to do it? Will I have to write and expose custom method? Any suggestion would be appreciated.
I used the instructions provided in the article "Component Interface based Web Services" (http://www.peoplesoftwiki.com/component-interface-based-web-services) and was able to successfully provide a web service and view the WSDL for interfacing with the PeopleSoft delivered Message Catalog component.
I was also able to create a new project in soapUI after using the URL to the WSDL provided by PeopleSoft.
However when I double-click on the generated request for the get method the SOAP envelope, that looks like the one below, is missing the MESSAGE_SET_NBR tags where I can enter test data.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:m14="http://xmlns.oracle.com/Enterprise/FSCM/schema/M141479.V1">
<soapenv:Header/>
<soapenv:Body>
<m14:GetCompIntfcHD_MSGCTLG_CI/>
</soapenv:Body>
</soapenv:Envelope>
I was able to add the Message Tag (as shown below) and test successfully
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:m14="http://xmlns.oracle.com/Enterprise/FSCM/schema/M141479.V1">
<soapenv:Header/>
<soapenv:Body>
<m14:GetCompIntfcHD_MSGCTLG_CI>
<m14:MESSAGE_SET_NBR>1</m14:MESSAGE_SET_NBR>
</m14:GetCompIntfcHD_MSGCTLG_CI>
</soapenv:Body>
</soapenv:Envelope>
But I am still interested in finding out why the tag did not get self-created when I imported the WSDL. It would be helpful especially when I have a CI that has a lot of data elements. Any help or comments are appreciated.
I believe the numbers that appear for each request relate to the input messages for that method. For example, in the Get method above, the input message might be M149999.V1. That is, it takes the first 3 characters of the message name.
Now if you have a look at your your WSDL through the Interface Viewer - right click on your service, Show Interface Viewer you can go to the WDL content and look at the relevant items - see screenshot below. This might help to explain it, or at least give you some clues?
![]() |
As suggested above, I add the following to my SOAP request header
<wsse:Security soap:mustUnderstand="1"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken>
<wsse:Username>PS</wsse:Username>
<wsse:Password>PS</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
But when I use soapUI to make the request, I get the following error:
…
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>PeopleSoftTargetConnector:Unable to decrypt the password</faultstring>
…
and the only way to get things working again is to roll the server processes on the integration gateway machine. Any ideas how to resolve this?

