PeopleSoft - PeopleTools Configurations Records or Meta Tables

-
PeopleSoft - PeopleTools Configurations Records or Meta Tables PeopleSoft records/metadata tables, often referred to as "meta tables," store information about various PeopleSoft objects and configurations.  1. Object Definition Tables: PSRECDEFN : Contains definitions of records (tables) used in the application, including details like record type and description. PSDBFIELD : Stores field definitions, detailing the attributes of each field such as data type and length. PSPNLGROUP : Holds information about components, which are collections of pages that function together. PSPNLDEFN : Contains definitions of pages (interfaces) within the application. PSMENUDEFN : Stores menu definitions, organizing how components are presented to users. 2. Security Tables: PSOPRDEFN : Maintains user profile information, including user IDs and associated roles. PSROLEDEFN : Defines roles that group together permissions for easier security management. PSCLASSDEFN : Holds permission li...
Post a Comment

Integrating PeopleSoft applications using JSON

-

Integrating PeopleSoft applications using JSON

Integrating PeopleSoft applications using JSON involves leveraging PeopleSoft Integration Broker's capabilities to handle JSON-formatted data, facilitating seamless communication with external systems through RESTful web services. 

Key Steps for JSON Integration:-

Document Object Creation:

Utilize the Document Builder to define the structure of your JSON data. This involves creating a document object that maps to the desired JSON schema, ensuring proper alignment between PeopleSoft and external data formats. 

Message Definition:

Create messages based on the document object. Navigate to PeopleTools > Integration Broker > Integration Setup > Messages and define new messages of type 'Document'. Ensure that the message structure aligns with the JSON data you intend to process.

Service and Service Operation Configuration: 

Define a REST service and associate service operations corresponding to the HTTP methods (e.g., GET, POST) you plan to support. For each service operation, specify the appropriate message and handler to process incoming or outgoing JSON data. 

PeopleCode Handlers: 

Develop PeopleCode handlers to parse incoming JSON requests and construct JSON responses. Starting from PeopleTools 8.55.11, PeopleSoft provides a built-in JSON Parser (JsonParser) to facilitate JSON processing. However, earlier versions may have limitations or bugs in JSON handling. 

Considerations: 

PeopleTools Version: 

Ensure your PeopleTools version supports the required JSON functionalities. Notably, versions prior to 8.55.11 may have limited or buggy JSON support. 

Content-Type Configuration:

Set the Content-Type header to application/json in your REST service operation definitions to indicate that the service processes JSON data. 

Testing and Validation: 

Utilize tools like Postman to test your RESTful services, ensuring that JSON data is correctly processed, and that the integration behaves as expected.

By following these steps and considerations, you can effectively integrate PeopleSoft applications with external systems using JSON, enabling efficient data exchange and enhancing interoperability.

Comments

Post a Comment

Popular posts from this blog

PeopleSoft Meta Tables

-
Application Engine Meta Data PSAEAPPLDEFN AE header record; 1 row per app engine PSAEAPPLSTATE AE state records (shows which one is the default) PSAEAPPLTEMPTBL AE temp tables assigned PSAESECTDEFN AE sections: public or private PSAESECTDTLDEFN AE section: descriptions, market, DB Type, EFFDT, EFF_STATUS, and auto commit PSAESTEPDEFN AE steps within section: description, market, DB Type, EFFDT, EFF_STATUS PSAESTMTDEFN AE actions within AE step: Step type (SQL, Do Select, etc.) with SQLID. PSAESTEPMSGDEFN AE message (parameters in each step) AEREQUESTPARM AE request parameters table behind the AE run control page. Find All Records Referenced in App Engine 1. Find the Temp Records (TAO) that are used: SELECT RECNAME FROM PSAEAPPLTEMPTBL WHERE AE_APPLID = 'MY_APP_PROGRAM_NAME' 2. If there are records, find the number of instances: SELECT TEMPTBLINSTANCES FROM PSAEAPPLDEFN WHERE AE_APPLID = 'MY_APP_PROGRAM_NAME...
Read more

Peoplesoft Application Package, Application Class and Application Method Implementation

-
Application Classes in PeopleSoft Defining and Importing packages or classes in PeopleCode <Pacakge name>:<Subpacakge name>:<…>:<Class name or wild card> Class Extensions represents the “is-a” relationship.   When a class extends another class, it’s called a subclass of that class. No Multiple inheritances or Concept of interface in Application classes. Instance variables in the class are accessible in all the objects of that class. Application programs generally pass parameters by value, which is not the same as for existing functions. Parameter passing with object data types is by reference. When the objects are passed to method and it reassign the object with new object it will not reflected in the calling method. Application Programs use the out specifier to pass a parameter by reference. Method increment (&Value as number out); rem passed by reference.   Create is the key word used to create the class object.  ...
Read more

Peoplesoft Application Package - Application Class/Application Package peoplecode and Calling them anywhere

-
Peoplesoft Application Package - Define Application Class and Calling Application class and Application Class Method from any Peoplecode event:  Step 1: Create New Application Package - MYPACKAGE Step2: Add a new application class in it. - MyClass Step 3: Defining Class and methods inside (Public or Private) 1. We can define classes here 2. We can define methods here 3. We can define Class Property Code to write inside a class to define class and its method: class MyClass method MyMethod (&smyInput as String, &nmyInput as Number) returns string; private method MyPrivateMethod (&sInput as String) returns boolean; property string &sVar; property number &nVar; end-class; method MyMethod /*+Method Body+*/ returns &sVar; end-method; method MyPrivateMethod  /*+Method Body+*/ returns &bVar; end-method; Code to write call a class and run its method: import MYPACKAGE:MyClass; Local string &sGetMethodData; Local MYPACKAGE:MyClass &oClassObjectVar...
Read more