Journey on Peoplesoft

Build Peoplesoft JAVA API: 1.        Open the PeopleSoft Application Designer. 2.        From the PeopleSoft Application Designer, open a component interface. 3.         Click the right pane and select  PeopleSoft APIs  from the Build menu. ( Before using your component interface, you must apply security to it and test it.) 4.       The Build PeopleSoft API Bindings dialog box prompts you for the types of bindings to create. Ensure you deselect COM Type Library Build, because you are creating Java files. To create APIs for a specific component interface or interfaces, click None. This clears the selected APIs, so you can select the appropriate APIs for your component interface. These APIs begin with the name of your component interface. In addition to the APIs for the selected component interface, you also must generate the ...

Performing the GET call on the  component interface using a Java client fails, despite all security being set correctly. In this case you would be able to do GET  using the CI tester in three tier, which indicates that security is not the issue.   The problem here was that the package structure of the API classes got changed from PeopleSoft.Generated.CompInfc to myNewpackage.Test.peoplesoft.   If you change the package structure of the API classes in anyway, e.g., you create different folder names other than what is generated during the API build, the Session object which controls all access, security, and errorLoging, will be unable to find the CI interfaces. The underlying JOA layer expects the following package structure:"PeopleSoft.Generated". The PeopleSoft Package structure should not be altered in either the directory structure or through the use of the package statement in the java classes.

a) Log into PIA (PeopleSoft Internet Architecture) via the browser, and navigate to PeopleTools > Security > Permission Lists.   b) Open the appropriate permission list.   c) Click on the Component Interface tab and enter the CI name.   d) Then click on the Edit link and add access to the CI's methods. Then click Ok.   e) Save the change on the permission list page.   f)  Test access to the CI again. In some cases you may need to delete the appropriate cache for the change to take effect.