Nodes are NOT used in REST in PeopleSoft. If you are exploring REST, then you can safely ignore this section.
Integration Broker Nodes are a conceptual representation of an integration end-point. This end-point generally represents a target system or server that is integrating with PeopleSoft. A node can represent a PeopleSoft system like HCM or Finance. Alternatively, it could represent an external system like Salesforce, Workday or your SSO system. The node name is used as a parameter when submitting requests to the httplisteningconnector. It tells the integration broker how to route and authenticate the user. It generally resolves to a valid PeopleSoft user defined on the node.
Node are used in various aspects of the PeopleTools Stack including:
Configuring integration broker “routings” for external systems (except for REST)
This is the functionality we care about in this book.
Setting up PeopleSoft to PeopleSoft data syncs. (These are still routings but I will classify them differently)
Defining “Portal Content References” to organize component navigation in the menu.
Configuring SSO Trust between different PeopleSoft Systems.
There are 3 node types that you can use.
External - This is used to represent a non-PeopleSoft node. We are really going to spend most of our time talking about this type.
PIA - This is used to represent a PeopleSoft node
IcType (ignore) - This is to setup a really old PeopleSoft system. I doubt this is being used by anyone.
There are 3 types of “Authentication options” on a node.
None - Do not ever use this. It means that any system that can target your Integration Broker server and craft an HTTP message to send messages as this node with zero authentication. There are some rare edge cases where you don’t want any authentication.
Password - This authentication uses a password on the node itself. If the client specifies the correct password then all PeopleCode will execute with the security that the “Default User ID” has. So if the a system/user knows the node password, they can effectively call web services that the OPRID on the node has access to.
One point that is often confusing is that the “Default User ID” normally does not have a password. The client specifies the password on inbound
This password applies to inbound integrations NOT outbound integrations
Certificate - I have never seen this used with 3rd party integrations. If I find an example, I will come back and document this.