18
Simple Example to Transfer Data from HRMS to FSCM Using Integration Broker Step1: Verify Default Gateway Status to “Active”

Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances

Embed Size (px)

Citation preview

Page 1: Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances

Simple Example to Transfer Data from HRMS to FSCM

Using Integration Broker

Step1: Verify Default Gateway Status to “Active”

Step1: Setting up Nodes

Page 2: Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances

For Example, we are going to transfer data from HRMS to FSCM

In HRMS,

Default node (Sender Node)-PSFT_HR

Remote Node (Receiver Node)-PSFT_EP

In FSCM,

Default node (Sender Node)-PSFT_EP

Remote Node (Receiver Node)-PSFT_HR

First we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances.

In HRMS,

Page 3: Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances

In FSCM,

Page 4: Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances
Page 5: Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances
Page 6: Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances

Step2: Setup Gateway Properties by PeopleSoft Node Configuration—Ping both sender and receiver nodes to get the status to “Success”.

In HRMS,

In FSCM,

Page 7: Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances

Step3: Creating Messages (rowset-based) for your component structure in both HRMS and FSCM Instances. In this Example, I have added only single Record

(Note: You have to create Messages with same structure in both HRMS and FSCM)

In HRMS,

In FSCM,

Page 8: Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances

Step4: Creating Queues in both HRMS and FSCM.

Here, first you have to create queue with Name and Description and Queue status set to “Run” then save it. After add this queue to your Service operation Explained in below step.

Below Screen-print shows after adding the Queue to Service operation.

In HRMS,

In FSCM,

Step5: Creating Service

Page 9: Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances

In HRMS,

Next, Add Service Operation with your own Name and Operation Type then click on “Add” button showed above.

Now, the page will be redirected to below page. In “General” Page provide your message information and routing status.

In HRMS,

Page 10: Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances

Handlers Page: Here, you have to provide Handler Details (In this example, I have created one Simple handler with message in OnNotify Method, Within the OnNotify method you can write your own logic)

Page 11: Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances

Routings Page: Here, you have to provide your Routing with sender as PSFT_HR and Receiver as PSFT_EP (Outbound Request).

Let’s see how to create Routing below,

Page 12: Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances

Next, after creating routing with specified service operation then automatically this routing will added to the service operation.

In FSCM,

Page 13: Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances
Page 14: Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances

Here, I have created simple App Package for updating data into table.

Routings Page: Here, in FSCM you need to create one routing to receive the data from HRMS with inbound request. (Sender: PSFT_HR, Receiver: PSFT_EP) as explained Earlier, by providing the service operation automatically tis routing will added to your service operation.

Creating Routing:

Page 15: Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances

Component Structure:

Page 16: Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances

In HRMS,

Add details for your component in HRMS then save it.

Page 17: Web viewFirst we have to ping the statuses to “Success” for both sender and receiver nodes in both HRMS and FSCM Instances

In HRMS,

Now these values are transferred to FSCM as shown below.