The following blog will elaborate the steps required to integrate PeopleSoft to Oracle WebService Manager (OWSM). We are considering PeopleSoft running on PeopleTools 8.51 and OWSM associated with SOA Suite 11g PS2.
Assumptions PeopleSoft system and OWSM system are already insalled and up and running and the user has access to both the systems.
On OWSM environment:
1. Create Default-keystore.jks and orakey.cer by running the following command:
2. This creates the default-keystore in the directory as shown here:
3. Verify the contents on the keystore with the following command, make sure that the orakey is present there:
4. Export the orakey.cer from the Default-keystore.jks
On PeopleSoft Environment:
5. For this exercise, the interop.jks keystore will be used, which comes delivered with PeopleTools, as given here:
6. List PeopleSoft delivered certificates:
7. Log into PeopleSoft database where the integration is being setup and identify the Default Local Node as given below:
8. Create a key based out of the local node name (E910A24 in this example):
9. Make sure that the key is created:
10. Export rootca and the local node key into files as given below and verify the files:
11. Copy the orakey.cer from OWSM, created in step 4 mentioned above, into the PeopleSoft directory and copy the rootca.cer and e910a24.cer (local Node certificate), created in step 10 above into OWSM directory as given below:
12. Import orakey.cer into interop.jks (PeopleSoft keystore) using the command as given below and verify:
12 a. Make sure to bounce the PeopleSoft webserver for the changes to take effect.
13. Import rootca.cer and e910a24.cer (local Node cer) into OWSM keystore using the command below and verify:
Configuring cwallet.sso and jps-config.xml files on OWSM:
14. On the Enterprise Manager, Access the Credentials Menu through the WebLogic Domain as given below:
15. It should appear as follows, if it has oracle.wsm.security map already there, it can deleted, as it will be generated in the following steps:
16. Using EM as shown, access the Security Provider Configuration:
17. In the Security Provider Configuration page, expand the keystore link and click on the Configure button as given below:
18. Provide the values for the password and keys, and hit okay as given below:
19. Go back to Credentials menu to make sure that the oracle.wsm.security map is created there and additional key for the basic credentials as given below:
20. This configures the cwallet.sso and the jps-config.xml file. Make sure to bounce the WebLogic server for the changes to effect:
Setup Required on PeopleSoft system for SAML Tokens enablement:
21. Open the orakey.cer using a text editor and copy the text to the clipboard as given below:
22. Open the digital Certificate Page on PeopleSoft side and add an entry for Remote as given below:
23. Click on the hyperlinks, Add Root and paste the copied text from the step on 21, and click ok, as given below:
24. Hit the refresh button in the bottom:
25. Add another entry for Remote as given below:
26. Using the Import hyperlink, add the same text as done for Step #23.
27. Hit the refresh button and you should find two entries as follows:
28. Additional Setup required for SAML Inbound into PeopleSoft: Add a new value as given below: (make sure to use the appropriate value for the Subject Name/Mapping PeopleSoft UserId)
29. Additional Setup Required for SAML outbound of PeopleSoft: Either in the Node configuration or on the Service Routing Configuration:
Node Configuration: (use the appropriate encryption level as well as the option to use the Default UserId)
On PeopleSoft Environment:
5. For this exercise, the interop.jks keystore will be used, which comes delivered with PeopleTools, as given here:
11. Copy the orakey.cer from OWSM, created in step 4 mentioned above, into the PeopleSoft directory and copy the rootca.cer and e910a24.cer (local Node certificate), created in step 10 above into OWSM directory as given below:
12. Import orakey.cer into interop.jks (PeopleSoft keystore) using the command as given below and verify:
13. Import rootca.cer and e910a24.cer (local Node cer) into OWSM keystore using the command below and verify:
15. 
Configuring cwallet.sso and jps-config.xml files on OWSM:
14. On the Enterprise Manager, Access the Credentials Menu through the WebLogic Domain as given below:
15. It should appear as follows, if it has oracle.wsm.security map already there, it can deleted, as it will be generated in the following steps:
16. Using EM as shown, access the Security Provider Configuration:
17. In the Security Provider Configuration page, expand the keystore link and click on the Configure button as given below:
20. This configures the cwallet.sso and the jps-config.xml file. Make sure to bounce the WebLogic server for the changes to effect:
Setup Required on PeopleSoft system for SAML Tokens enablement:
21. Open the orakey.cer using a text editor and copy the text to the clipboard as given below:
27. Hit the refresh button and you should find two entries as follows:
29. Additional Setup Required for SAML outbound of PeopleSoft: Either in the Node configuration or on the Service Routing Configuration:
Node Configuration: (use the appropriate encryption level as well as the option to use the Default UserId)
Or Service Routing Configuration:
30. Modify the wssSAMLProperties file as given below:
