Configuring Nodes

Enter a descriptive name for the node.

Select from:

PIA: Designates the node as a PeopleSoft database that uses PeopleSoft Integration Broker. This is the default for a new node.

External: Designates the node as an entity that doesn’t use PeopleSoft Integration Broker.

ICType: A portal-specific setting that PeopleSoft Integration Broker doesn’t use.

Select from:

• Certificate: The current node uses a digital certificate to sign the messages it sends, and expects messages it receives to be signed by a complementary digital certificate. When a PeopleSoft Pure Internet Architecture node receives a service operation, PeopleSoft Integration Broker extracts the distinguished name from the certificate and validates it against the sending node's distinguished name retrieved from the default local node’s keystore. Service operations sent by the default local node have the digital certificate automatically inserted by Integration Broker. An external node is expected to respond to certificates outwardly the same way as a PeopleSoft Pure Internet Architecture node.

• None: No authentication is required. This is the default value.

  Warning! Single signon is not compatible with this option. If you select None for the default local node, and implement single signon on the same system, all transactions will fail. You must select either Password or Certificate when implementing single signon.

• Password: Two new fields appear:Password and Confirm Password. Enter your password in the first edit box, and confirm it in the second edit box. With a PeopleSoft Pure Internet Architecture node, PeopleSoft Integration Broker expects service operations, both outbound to and inbound from the current node, to include a password, which it validates against the password entered here. An external node is expected to respond to passwords outwardly the same way as a PeopleSoft Pure Internet Architecture node.

See Implementing Node Authentication.

Indicates whether the current node represents the database to which you are assigned.

Indicates that the current node is either a portal node or the default local node.

You cannot change this setting for the default local node.

Select to make the current node definition active, so it can be used by PeopleSoft Integration Broker.

Clear the box to inactivate the node.

Note the following points about inactivating a node:

• You cannot inactivate the default local node.

• Inactivating a node will inactivate related routing definitions. You must reactivate the routing definitions manually.

  See Activating and Inactivating Routing Definitions.

Select to activate nonrepudiation for the current node.

Note that to activate nonrepudiation for the current node you must also activate nonrepudiation in the service operation definition for which you want this feature.

Check the box to configure the node to handle message segments.

See Working With Message Segments.

Displays when the Authentication Option is Password.

Enter a node password. The limit for this field is 88 characters.

Reenter the node password you entered in the Password field.

This control appears only when the Authentication Option type is Password or Certificate.

Click the button to create a system-generated check tokenID for use in conjunction with single signon among PeopleSoft systems.

When you click the button, the system populates the Check TokenID field with the generated value.

See Implementing PeopleSoft-Only Single Signon for more information about check token IDs.

This field appears only when the Authentication Option type is Password or Certificate.

This field contains the check token ID value generated after clicking the Create CheckTokenID button. This ID is used in conjunction with single signon among PeopleSoft systems.

Alternatively, you can create a custom ID up to 256 characters.

See Implementing PeopleSoft-Only Single Signon for more information about check token IDs.

On inbound integrations, this is the user ID that the sender must specify to invoke a service operation, unless you have set up an external user ID for this purpose.

On outbound integrations, this is the default user ID sent with the service operation.

This field appears only when working with an External node type.

This field is used in conjunction with using introspection to create routing definitions.

Enter the WSIL URL for the target system to include in the routing definition.

Select the name of a node that will serve as a “gatekeeper” for the current node. You can select any existing PeopleSoft Pure Internet Architecture node for this purpose.

Not all node types are appropriate as hub nodes. Nodes of type ICType are portal-specific, and aren’t used by PeopleSoft Integration Broker. A node of type External typically isn’t an Integration Broker system, so it might not be usable as a hub node unless you’ve explicitly configured it to be compatible with Integration Broker.

This field is for information only. If the current node is used as a hub, you can indicate the target node with which it’s associated. If the current node represents a subordinate database, you can indicate the primary database.

Enter the name of the company or organization associated with the current node.

Set this parameter on a remote node definition to limit the number of requests sent to the node per dispatch. The setting is in minutes.

For slow-processing systems, this option can help to prevent saturating the targeting system with requests.

This parameter is used only for asynchronous integrations.

Select an image from the system database. Any application that uses images can use the selected image to represent the current node.

Select the codeset group to which you want the current node to belong. Transform programs invoked by service operations use this association to search for message data requiring translation.

See Performing Data Translation.

The Copy Node button displays after you have saved the initial node definition.

Click to define a new node with the same properties as the current node. The Default Local check box is cleared for all new nodes.

The Rename Node button displays after you have saved the initial node definition.

You can rename only the default local node.

Additional information about deleting nodes is contained elsewhere in this topic.

See Renaming or Deleting Nodes.

The Delete Node button displays after you have saved the initial node definition.

You cannot delete the default local node.

Additional information about deleting nodes is contained elsewhere in this topic.

See Renaming or Deleting Nodes.

This field appears only when working with an External node type.

This field is used for outbound integrations in conjunction with implementing WS-security.

See the Specifying External User IDs and Password section in the Implementing Web Services Security topic.

This field appears only when working with an External node type.

This field is used for outbound integrations in conjunction with implementing WS-security.

See the Specifying External User IDs and Password section in the Implementing Web Services Security topic.

This field appears only when working with an External node type.

This field is currently not used.

The name of the representative or administrator of the node, in standard PeopleSoft name format.

The Contact Manager’s email address, in standard PeopleSoft email address format.

The phone number of the contact manager.

The address of the Contact Manager’s support web site, if there is one.

Select from:

Category: The property is used for categorization.

Ident: The property is used for identification.

Search: The property is used for searching.

Enter a new property name or select an existing property of the selected name type.