<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?

Do you get any rows returned checking for duplicated data using this SQL?

 select OPRID, LOGIPADDRESS, LOGINDTTM from PSACCESSLOG group by OPRID, LOGIPADDRESS, LOGINDTTM having count(*) > 1; 

&YourCookie.Domain = %Request.AuthTokenDomain;

I'm using the PeopleTools 8.51 and PA 9.1 (which is not relevant i guess…). I cannot reproduce your exemple due to the fact that PSACCESLOG doesn't have an unique index. So… in the step "Create the Archive Object" I cannot save the archive object, due to this error. What can I do? Is there any work around?

Thanks for the answer.

Hope this helps.

The WSDL URL will be provided when you use the provide web service wizard, and looks something like this:
http://<machine>:<port>/PSIGW/PeopleSoftServiceListeningConnector/EXAMPLE.1.wsdl

PeopleSoft Integration Gateway
PeopleSoft Listening Connector
Tools Version : 8.49.28

Can anyone please let me know why the wsdl code is not showing?

Thanks in advance

Links to PeopleBooks (8.51)

• SetTraceSQL

• SetTracePC

For peoplecode tracing, you set the trace flags using the SetTracePC() function. e.g
SetTracePC(3596);
… will set the trace flags as per the defaults on the Trace Peoplecode page. These are the settings I usually use.
SetTracePC(0);
… will turn peoplecode tracing off.

The function for SQL tracing is SetTraceSQL().

There's more useful info on this in the Peoplecode Language Reference peoplebook, including what each of the trace flags do.

I'd say running stats/analysis is always going to be helpful. I don't recall if any of the steps in data archive manager do this for you, but it wouldn't hurt to do again.

There was an error during service introspection.
cvc-complex-type.5.2: In element 'wsp:Policy', attribute 'Id' is a Wild ID. But there is already an attribute 'Id' derived from ID among the {attribute uses}.

This is might be a Flex builder issue.. I think this error has to do something with Policy section in the WSDL. Please find the details below.

<wsp:Policy xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="UsernameTokenSecurityPolicyPasswordRequired">
<wsp:ExactlyOne>
<wsp:All>
<wsse:SecurityToken xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" wsp:Usage="wsp:Required">
<wsse:TokenType>wsse:UserNameToken</wsse:TokenType>
<Claims>
<SubjectName MatchType="wsse:Exact"/>
<UsePassword wsp:Usage="wsp:Required"/>
</Claims>
</wsse:SecurityToken>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>

Excellent article.

Also, I feel that the comments above (with all due respect) are exceptional cases. Usually, in a Production Environment, we would be looking at Archiving Data which has unique keys anyway.
Another thing is we can convert the history table into flat files using PeopleTools > Archive Data > Export History Files to Flat Files. This becomes handy when we dont want to store the history in the database.

Question for you:
Do we need to run stats or analyze the main table after we run the delete process?
Thanks.

Just out of curiosity, do you need any security at all? I mean the error is just saying the PSADMIN user does not exist. I thought maybe, once you created that user even with the most basic security, it would just work? If you clear out the primary permission list, HCPPALL do you get an error?

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?