Pausing, Testing, and Pinging Nodes

This chapter discusses how to:

Click to jump to parent topicUnderstanding Pausing Nodes

A pause time is an interval of time during which the node becomes inactive. When the pause time begins, the node is shut down until the pause time is scheduled to end.

You might schedule a pause time to perform maintenance tasks or devote server resources to an important batch run. For example, say that you have a complex batch program that runs on the same server as a particular node every Monday morning from 12:05 a.m. to 3:30 a.m. To make sure that the batch program has enough memory devoted to it, you can set a pause time for the node that runs from 12 a.m. to 4 a.m.

During a pause time, transactions are not published or received by the local system. When the system is paused, the node cannot accept service operations sent to it. Consequently, the publishing node must attempt to send transactions again later. The publishing node continues to send transactions until it exceeds the local timeout period. When this happens, the transaction assumes a Timeout status in the publisher’s queue. The timeout period is an attribute of the publication queue, not the subscription queue.

If the system attempts to send a transaction while the node is paused, the system writes the transaction to the publication and subscription queues, but it cannot publish the transaction until the system is no longer in the paused state.

Note. Pause times do not appear in PeopleSoft Application Designer upgrade projects; you cannot upgrade them.

If you have domain failover configured for your integration system, it is disabled when a node is paused. However, there is a chance that failover could occur when you pause a node, due to the independent timing between domain failover logic and the PeopleSoft Integration Broker runtime environment. The chance of failover occurring during a node pause time increases if the failover time check (IB Failover Time) on the Failover Configuration page is set to a low number of minutes.

See Also

Setting Up Domain Failover

Click to jump to parent topicAdding Pause Times to Local Nodes

Use the Node Status page to add pause time to local nodes. The following example shows the page:

To add a node pause time:

  1. Click Add Pause.

  2. Select a day of the week in the Start Day drop-down list box.

  3. Enter a value in the Start Time edit box.

  4. Select a day of the week in the End Day drop-down list box.

  5. Enter a value in the End Time edit box.

  6. After you have entered the appropriate start and end values to define your pause interval, click OK.

Click to jump to parent topicDeleting Pause Times

To delete an existing pause time:

  1. In the pause time list, locate the pause time (interval) to delete.

  2. Click the Delete button to the right of the entry in the pause time list.

Click to jump to parent topicTesting Local Nodes

To test the local node:

  1. Make sure you are logged on to the node that you want to test.

  2. Click the Test Node button.

Click to jump to parent topicPinging Remote Nodes

A successful ping indicates that the remote node is available to receive transactions. An unsuccessful ping could indicate that the node, gateway, or both are not running.

To ping a remote node:

  1. In the Ping a Node to Determine Availability section, select the node in the Message Node Name drop-down list box to display a list of active nodes.

    The Location column in the grid below reveals the locations defined for the node.

  2. Click the Ping Node button.

    The Node Information Section displays connector information defined for the node.

You can also ping remote nodes from the Send Master utility as well as the Simple Post utility.

See Using the Send Master Utility, Using the Simple Post Utility.