Nodes represent any organization, application or system that will play a part in integrations.
For example, nodes can represent customers, business units, suppliers, other trading partners, external or third-party software systems, and so on.
Node definitions define the locations to or from which messages can be routed.
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
Local and Remote Nodes
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.
For example, if the following definitions exist in the Node A database:
NODE_A (default local)
The following definitions must exist in the Node B database for it to integrate with Node A:
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.
This section discusses nodes that are delivered with PeopleTools.
The AIA node is used for Oracle Application Integration Architecture (AIA) integrations, and represents an AIA integration partner.
Warning! Do not modify or delete the AIA node.
The Anonymous node is designated as the requesting node within PeopleSoft Integration Broker for third-party integrations that do not pass in a requesting node, but do have a defined any-to-local routing definition enabled on the service operation to be invoked.
Warning! Do not delete the Anonymous node.
You must modify the Anonymous node and define a Default User ID. The Default User ID that you specify is the ID that the system assigns to transactions that do not pass in a user ID.
The Atom node is used in association with PeopleTools feeds functionality.
You can use the Atom node only with asynchronous service operations. You cannot use the Atom node as the sending node. When the Atom node is the receiving node, the sending node must be the default local node.
Warning! Do not delete the Atom node.
Feeds are described elsewhere in product documentation.
PeopleSoft delivers a node with the name BPEL specifically for integrations with BPEL process-based integrations when you are using Oracle BPEL Process Manager as the runtime engine. If you are using Oracle BPEL Process Manager, you must configure this node.
Information about configuring this node is described elsewhere in the product documentation.
Default Local Node
The Default Local Node represents the system on which the application database is installed.
PeopleSoft Integration Broker is delivered with one node predefined as the default local node. You can't change which node is the default local node, but you can rename it to a more appropriate and meaningful name for your application or system.
The IB_Network node is delivered with PeopleTools and is used to perform functionality across all nodes in the integration network, including registering network nodes on participating systems. The password set for this node must be identical on all systems participating in the network.
Warning! Do not delete the IB_Network node.
The WSDL node is the default node used by the Consume Web Service wizard.
Warning! Do not modify or delete the WSDL node.
The WADL node is the default node for REST consumer services.
Warning! Do not delete the WADL node.