Generating Component Interface APIs

By mymithraa -
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 API files for the following generic component interface properties:

CompIntfcPropertyInfo
CompIntfcPropertyInfoCollection

You may select these items in the same step as the component interface build, or you may select them separately.
Click OK.

Once Java files are created , execute the below script to create Jar file.

javac -classpath .\psjoa.jar PeopleSoft\Generated\CompIntfc\*.java
jar -cvf PSFTCI.jar PeopleSoft\Generated\CompIntfc\*.class





Comments

Post a Comment

Popular posts from this blog

Peoplesoft Error: All Processing Suspended: Restart OPRID=PS, RUNID=RUN01, PI=5000(108,503)

By mymithraa -
All Processing Suspended: Restart OPRID=PS, RUNID=RUN01, PI=5000(108,503) What is this about and what should be done? This error can occur when Application Engine programs are restartable and run via the Process Scheduler, and the last run was No Success - And an attempt re-run, rather than re-start will produce error as well The cause of this message is that previously this same AE program was run using the same OPRID=PS & RUNID=RUN01. It was not Successful on initial run, and now an attempt to RUN the same program has occurred, instead of an attempt to RESTART the original that failed. Whether this error Happened in Development??? This message happened while the Customer was in Development phase of this AE program. It could have happened when this AE was in Production as well. However, what to do would have completely different emphasis depending on if this happens in Development or Productions. During the development cycle, we would expect that this AE would have to run many tim...
Read more

Peoplesoft SFTP

By -
Image
Transferring a file using SFTP to specified target location: (Thanks to Jawahar who helped me in this article) A lot has been mentioned about sFTP support in PT 8.51. Below gives clear idea on SFTP. Are there any specific pre-requirements for using file transfer protocols? Yes. Though FTP can be used directly by giving the URL as a string to the peoplecode method, other protocols (ftps, sftp, http and https) require the URL to be passed as a URL identifier only. When an URL identifier is created, URL properties link on the page gets enabled. Users need to provide the URL properties specific to the protocol they are using on this "URL properties" page. The URL properties differ based on the protocol choosen. Once URL Identifier is ready, it can be used in any of the file attachment peoplecode methods just like the existing way.   What are the authentication methods supported for sftp? Password and Public Key authentication are supported. ...
Read more

Error: Think-time PeopleCode event (Exec), but a SQL update has occurred in the commit interval.

By -
Think-time PeopleCode event (Exec), but a SQL update has occurred in the commit interval. Faced above error after tools upgrade. Custom Application Engine (AE) program. PeopleCode step uses Exec() function with the intention of Syncronous execution of the command. When the AE runs it failed with this, or similar Think-Time error; Solution: There are Restrictions on Use of the Exec() Funtion in PeopleCode Events - and there is also a Restriction in Application Engine programs. This is based on whether the execute of the external program is Synchronous, or Asynchronous. If Asynchronous execution is selected - the execution is not 'tied' directly to the continuing execution of the running AE program, so no Think-time error results from this choice. With Synchronous execution it is different - the AE program will wait for the exectution of the command before continuing with the current process. In order for this to work with no error - a Commit has to happen before the Exec ...
Read more