Pinging Nodes

This section discusses how to:

  • Ping a node using the Nodes–Connectors page.

  • Ping a node using the Node Status page.

This section describes the processing that takes place when you ping a node from the PeopleSoft Pure Internet Architecture.

  • The system uses the application server URL, user ID and password specified in the Jolt connect string settings section in the integration gateway properties file to establish a connection to the target database.

  • The system verifies that the user ID and password are valid on the target system.

    The destination node must match the defined local node on the target system, otherwise the system displays the following error:

    Destination node does not match local node.

    When pinging remote nodes, if the source node defined on the target is defined as a PeopleSoft node and an authentication token is passed, then the authentication option on the node must be either Node Password or Certificate. The system then compares the passwords or certificate.

    In the following cases, if node authentication is defined, you cannot ping a node:

    • The source node defined on the target system is not a PeopleSoft node.

    • The source node defined on the target system is a PeopleSoft node, but no authentication option, for example Node Password or Certificate, is selected.

You can ping a node using the Nodes-Connector page in PeopleSoft Integration Broker.

To ping a node:

  1. Access the Nodes-Connectors page (select PeopleTools > Integration Broker > Configuration > Nodes and click the Connectors tab).

  2. Click the Ping Node button.

You can ping a node using the Node Status page in the Service Operations Monitor.

To ping a node:

  1. Access the Node Status page (select PeopleTools > Integration Broker > Service Operations Monitor > Administration > Node Status).

  2. Click the Ping Node button.