Advance Technical Course Content

Topic	Content	Duration
ExceltoCI	Excel to CI Introduction Business Scenarios where Excel to CI is used Uploading data through Excel to CI	1.11 Hours
BI/XML Publisher	Introduction to XML Publisher Advantage of using XML Publsher over SQR How XML Publisher Works How many ways we can call XML Publisher	2 Hours
BI/XML Publisher	Developing a complex business report using XML Publisher	2.11 Hours
PS Query	Introduction to PS Query Significance of PS Query in creating simple business reports The Power of PS Query How to Create a Simple business report with PS Query	3 Hours
PS Query	Creating a Complext PS Query for a business Requirement Avoiding auto generated row level security criteria in PS Query PS Query Security	2 Hours
AWE	Introduction to AWE Why AWE is so Important for Business Building blocks of AWE What are all the things we need to do to Setup up Approval Process thorugh AWE	2 Hours
AWE	Creating an Static Approval Process for a Business Requirement using AWE	4 Hours
	Creating an dynamic Approval Process for a Business Requirement using AWE
IB	Introduction to IB Understandng Messaging in IB Understandign CI Based Services Managing Service Operation Queues Where all the IB is used in internal PeopleSoft Applications	1 Hour
IB	Setting up a full sync between HCM and Finance	1.5 Hours
Classic to Fluid	Converting Pages in fluid	6 Hours
	Working on Page Layout in fluid
	Working on Scroll area in fluid
	Working on other page controls
	Create layout page
	Working on search record for fluid
	Creating Component
	Creating pivot grid for search functionality
Fluid	Tiles overview and Core Concepts	2 Hours
	Types of creating fluid tiles
	Creating tiles through Tile Wizard
	Creating tiles through Portal Registry
	Adding Tiles to homepage and the security configuration
Project Migration	Migration Overview and project life-cycle	2.5 Hours
	Understand the objects and their types
	Inserting objects into project
	Creating file references
	Understanding data migration
	Understanding DMS scripts and how to create them
	Upgrade flags and how they work
	Creating Change package
	Comparing and migrating the project in target instance
	Reviewing and updating upgrade flags
	Copying the project in the target instance
	Building the project
	Importing the data through DMS
Web Services	Overview of Web Services and integration with third party	2 Hours
	Configuring Local Gateway
	Creating WSDL node for external integration
	Setup integration through consume web service wizard
	Setup nodes and authentication if the third party requires authentication
	Business logic in PeopleCode for sending SOAP XML request and receiving response

PeopleSoft to Third Party Integration Through Web Services

This has been most challenging topic for many PeopleSoft professionals as it involves several elements when establishing such an integration. Lets demystify this today.

These are the steps to establish such an integration:

Related Articles:

PeopleSoft to PeopleSoft Integration through Integration Broker

Fundamentals Of PeopleSoft Integration Broker

1. Check Local Network Configuration

In this step, we need to ensure the Gateway is setup up properly and that we are able to ping the gateway successfully. This also involves setting up the password key in the gateway property.

2. Setup External Node (WSDL)

A new node needs to be created which will establish connection with external system. We would rather create a copy of the delivered WSDL node and provide all the connection information. The connection details can be found in the WSDL provided by the third party.

3. Consume Web Service

The WSDL provided by third party needs to be consumed into PeopleSoft which will create all the necessary Service Operations to read and write incomming and outgoing messages.

4. Enter Connection Information

Once the service operation has been created, we need to enter the connection information i.e the PeopleSoft Node and WSDL Node that we have created.

5. Configure Security

The user who would be triggering the external integration needs to have full access to Service Operations working underneath. The access need to be granted to this user via Service Operation security page.

6. Business Logic (PeopleCode)

The Peoplecode which will read the incomming message and write the outgoing message bundleled in SOAP protocol need to be written in the appropriate event such as FieldChange, FieldEdit, SavePostChange whereever applicable.

Related Articles:

PeopleSoft to PeopleSoft Integration through Integration Broker

Fundamentals Of PeopleSoft Integration Broker

PeopleSoft to PeopleSoft Integration through Integration Broker

Before you begin reading this article, you must know - Fundamentals of PeopleSoft Integration Broker

In this we will see what are the steps to integrate one PeopleSoft Application with another one and will do it for the same scenario we talked about in the article Fundamentals of PeopleSoft Integration Broker. In this example, the PeopleSoft FIN system is the source system and the PeopleSoft HCM system is the destination system.

On a very broad level, this is what we are going to configure:

• The integration gateway.

• The PeopleSoft Finance system.

• The PeopleSoft HR system.

Configuring the Integration Gateway

The only required property that you must set for the local gateway is the Oracle Jolt connect

strings that enable the gateway to find the PeopleSoft HR system. Set this property in the

integrationGateway.properties file.

So, open the integrationGateway.properties file on Web Server and update the Jolt Connect String. You can open this file from below highlighted link on Gateway Component in PeopleSoft Finance System.

Configuring the PeopleSoft Finance System

Perform the following tasks on the PeopleSoft Finance system:

Local Gateway

Define the local integration gateway in the PeopleSoft Finance system by using the

Gateways component.

Any integration gateway that you've installed and configured to find the PeopleSoft HR system can

serve this role. Specify the gateway's PeopleSoft listening connector as the gateway's URL.

Note that the Local Gateway setup will be same in both Finance and HR system.

Related Articles:

Fundamentals Of PeopleSoft Integration Broker

PeopleSoft to Third Party Integration Through Web Services

Message

Define the message from the navigation PeopleTools - Integration Broker - Integration Setup - Message. This should reflect the rowset structure of Bank Account component in HR system because this structure will be used to transmit data to HR.

Handler

Define the handler using Application Designer. Since in our case the Finance System is a sender and there is only one way communication so only a dummy Application Package and Class is required with no Processing Logic written in it.

Routing

Routing is where we define the following:

• One way communication or two way (In our case its One Way)
• Synchronous or Asynchronous (In our case its Asynchronous)
• The sender and receiver nodes (In our case PS Finance is Sender and PS HR is Receiver)

Navigation: PeopleTools -Integration Broker - Integration SetUp - Routing

Service Operation

It ties previous three elements - Message, Handler and Routing together and forms a mechanism for integration. Define the service operation and add those three elements in it.

Navigation: PeopleTools -Integration Broker - Integration SetUp - Service Operation

Node

Define two nodes, one for HR system and another for Finance system. The Finance Node in this case would be local and HR Node would be remote.

• Also mention followings in node definition:
• Connectors (Gateway and Target Connector)
• Portal URLs (PIA URL)
• Routing (Add the routing definition defined above)

The node definition can be same across PS to PS integration because it represents the whole system.
Navigation - PeopleTools -Integration Broker - Integration SetUp - Node

Configuring the PeopleSoft HR System

Perform the following tasks on the PeopleSoft HR system:

Local Gateway

As already mentioned, the Local Gateway in both systems will have same configurations.

Message 

Define the message from the navigation PeopleTools - Integration Broker - Integration Setup - Message. This should reflect the rowset structure of Bank Account component in Finance system because this structure will be used to read data sent from Finance system.

Handler

The handler in HR system would contain the actual processing logic since it has to read data sent from Finance and load into tables.
Its basically an application package containing a class definition which has the processing logic written in PeopleCode to read the data (Bank Account Changes).

Routing

Routing is where we define the following:

• One way communication or two way (In our case its One Way)
• Synchronous or Asynchronous (In our case its Asynchronous)
• The sender and receiver nodes (In our case PS Finance is Sender and PS HR is Receiver)

Navigation: PeopleTools -Integration Broker - Integration SetUp - Routing

Service Operation

It ties previous three elements - Message, Handler and Routing together and forms a mechanism for integration. Define the service operation and add those three elements in it.

Navigation: PeopleTools -Integration Broker - Integration SetUp - Service Operation

Node

Define two nodes, one for HR system and another for Finance system. The HR Node in this case would be local and Finance Node would be remote.

• Also mention followings in node definition:
• Connectors (Gatway and Target Connector)
• Portal URLs (PIA URL)
• Routing (Add the routing definition defined above)

The node definition can be same across PS to PS integration because it represents the whole system.
Navigation - PeopleTools -Integration Broker - Integration SetUp - Node

Related Articles:

Fundamentals Of PeopleSoft Integration Broker

PeopleSoft to Third Party Integration Through Web Services

Fundamentals Of PeopleSoft Integration Broker

I have been trying to push myself hard for a long time to publish this article but honestly, I have been way too lazy to do that. Well, now is the time.

A very important highlight of this article is we are going to talk about only absolutely relevant elements so that it becomes easier for you guys to get good understanding on Integration Broker because often times I find people being lost in the PeopleBooks trying to figure out what exactly they should refer to. 

Related Articles:

PeopleSoft to PeopleSoft Integration through Integration Broker

PeopleSoft to Third Party Integration Through Web Services

Lets start with Architecture which shows the elements of Integration:

This architecture clearly depicts the integration between PeopleSoft Finance and PeopleSoft HR system represented by Node A and Node B respectively where the changes made in former would be transmitted to latter through Integration Broker.

Lets assume that the integration is setup for the Bank Account changes done on Finance System which should ultimately be transmitted to HR System to keep both in sync. Now our rest of the discussion would be based on this scenario.

The very first thing we must talk about is the various elements involved in this Integration Setup.

Elements of Integration

Integration Engine

The integration engine as you can see in the architecture above, is something that ties all the elements like Service Operation, Message, Routing etc... together which ultimately creates a mechanism for integrating two systems.

The integration engine runs on the PeopleSoft application server. Rather than communicating directly with other applications, the integration engine sends and receives messages through one or more separately installed integration gateways.

The integration engine:

• Uses a modular architecture, so it can treat gateways as black boxes and communicate with them using standard connectors.
• Handles messages containing data in a variety of formats. Formats include the PeopleSoft rowset-based message format, and nonrowset-based message structures including, XML document object model messages, Simple Object Access Protocol (SOAP) messages, and non-XML files.
• Sends and receives messages asynchronously (like email) or synchronously (suspending activity to wait for a response).
• Applies message transmission type and routing based on specifications that you define in a PeopleSoft Pure Internet Architecture component.

Gateway

The integration gateway is a platform that manages the receipt and delivery of messages passed among systems through PeopleSoft Integration Broker. It supports the leading TCP/IP application protocols used in the marketplace today and provides extensible interfaces to develop new connectors for communication with legacy, enterprise resource planning, and internet-based systems.

Additional features include:

• Listening connectors and target connectors that transport messages between integration participants and the integration engine.
• Basic logging information concerning message receipt, delivery, and errors.
• Connection persistence with continuous open feeds to external systems through connectors, with full failover capabilities.
• Transport protocol and message format management so that when messages reach the integration engine, they have a PeopleSoft-compatible message format.

Connectors

Listening Connectors

Listening connectors receive requests from integration participants, send them to the gateway manager, and deliver responses back to the integration participants.

Target Connectors

Target connectors generate requests, send them to integration participants, wait for responses from participants, and deliver the responses back to the gateway manager.

Related Articles:

PeopleSoft to PeopleSoft Integration through Integration Broker

PeopleSoft to Third Party Integration Through Web Services

Message

Message definitions provide the physical description of the data that is being sent, including fields, field types, and field lengths. You create message definitions in the PeopleSoft Internet Architecture. In other words Messages are shapes that describe the contents of a service operation transaction.

In our scenario the message definition would contain the information about the table structure used in the component 'Bank Account' i.e the records used in the component and their hierarchy. This information will be used by Integration Engine to transmit the data when there is a change in employee's bank accounts. 

Message Type	When to Use	Details
Rowset-based messages	All PeopleSoft-to-PeopleSoft integrations	For hierarchical data that is based on PeopleSoft records, you create a message definition by assembling records, organizing them into a hierarchy, and selecting fields from those records to include in the message.
Nonrowset-based messages	Integrations with third-party systems	These messages can have virtually any structure and content. You create a message definition, but you do not insert any records. The message definition serves as a placeholder for the actual message.

Handler

It contains the processing logic for finally writing the data into tables/components of the receiving node. It is combination of Application Package, Class, Method created in the application designer.

In our scenario the handler defined on HR Node would contain the business logic written in PeopleCode to write the Bank Account changes received from Finance Node, to the corresponding tables/components. 

Routing

A routing definition specifies the direction of the integration (inbound or outbound), routing alias names, transformations, and more. 

In our scenario, the routing on HR Node would be Inbound and on Finance Node it would be Outbound.

Service Operations

This element forms for overall processing logic by combing following elements:

• Message
• Handler
• Routing

Node

Nodes represent any organization, application or system that will play a part in integration.

In our scenario there are two nodes:

1. One that represents PeopleSoft FIN System
2. Another that represents PeopleSoft HR System

Because an application can send messages to itself, a default local node definition that represents the application is delivered as part of the integration engine.

Each PeopleSoft installation must have one, and only one, default local node.

Each PeopleSoft Integration Broker database involved in an integration must contain a default local node definition for itself, and a remote node definition for each of the other nodes involved.

Local and remote nodes are concepts relative to the database in which the nodes are defined. If you’re signed on to Database A which has Node A defined, then Node A is local. If you’re signed on to Database B, Node A is defined as remote.

In our scenario if we are in the Node A - PeopleSoft FIN System then:

·        Node A (default local)

·        Node B (remote)

The following definitions must exist in the Node B - PeopleSoft HR Systen for it to integrate with Node A:

·        NODE A (remote)

·        NODE B (default local)

In practice, only portals use nodes designated simply as Local. The only local node definition used by PeopleSoft Integration Broker is the one designated Default Local, which represents the database onto which you are signed.

Want to learn PeopleSoft technical module thoroughly? I have several videos with total duration of over 50 hours.

Following is the link to the YouTube videos Technical
Click here to see course contents

Click here to know how it works

However, if you want to save money by purchasing whole module instead of in parts then visit this page to get more details PeopleSoft Functional and technical online training