Setting Up PeopleSoft Integration Points
This section discusses how to set up PeopleSoft integration points.
Note: For more information and technical details about these integration points, and for information about how and with what applications to use them, consult the relevant application documentation.
Page Name |
Definition Name |
Usage |
---|---|---|
EOIU_SOPUBATCH |
Set up publication rules. You must activate a publication rule for the publication messages that you create to follow. This rule includes instructions on message chunking. |
|
EOIU_ADNODECHUNK_PNL |
Map PeopleSoft message nodes to chunking rules. |
|
Batch Publish Page |
EOIU_BATCHPUB |
Create the run control for the batch publish process. |
Use the Batch Publish Rules page (EOIU_SOPUBATCH) to set up publication rules.
You must activate a publication rule for the publication messages that you create to follow. This rule includes instructions on message chunking.
Navigation:
This example illustrates the fields and controls on the Batch Publish Rules page. You can find definitions for the fields and controls later on this page.
![Batch Publish Rules page](img/i-1de106ban-7f07.png)
If the data that you’re transmitting does not fit in a single message, or if you want to send different parts of the message to different target systems, set up the rules to chunk the message and associate it with the publish rule. The business unit and setID chunking rules are standard in PeopleSoft applications, but you can configure chunking rules.
Field or Control |
Description |
---|---|
Publish Rule ID |
Select the name of the message for which you’re setting up rules. |
Status |
Select Active to activate this publish rule definition for this message. Select Inactive to prevent this rule from applying to this message. |
Chunking Rule ID and Alternate Chunk Table |
Enter the unique chunking rule name that is set up when you created the chunking rule. The message that you publish is routed based on this field. If necessary, enter an additional field in the Alternate Chunk Rule ID field by which to chunk the message. |
Message Options
Many PeopleSoft systems rely on a message header and message trailer to trigger subscription PeopleCode to discard old table data and insert the new incoming data. As a general rule, all FullSync messages should use a header and trailer. Sync messages don’t need headers and trailers.
Output Format
The Application Engine program used to chunk messages can create either an XML message that flows through messaging architecture or a flat file that is generated in PeopleSoft Process Scheduler and not published elsewhere. Always select Message as the format when you send data to PeopleSoft systems.
Use the Add Nodes to Chunk Rule page (EOIU_ADNODECHUNK_PNL) to map PeopleSoft message nodes to chunking rules.
Navigation:
This example illustrates the fields and controls on the Add Nodes to Chunk Rule page. You can find definitions for the fields and controls later on this page.
![Add Nodes to Chunk Rule page](img/i-1de106ban-7ec4.png)
To map nodes to a chunk rule:
In the Add column, select the check box next to the nodes that you defined earlier.
After you select a node, use the Add button in the Add Chunk Values column to open the Quick Map page for the message you defined earlier.
Click Save.
Create a service operation handler to route the message chunk to the correct subscriber node.
To do so, extend the IRouter application class and use the OnRouteSend method. Then in the appropriate service operation, define a handler and specify the application class.