(Optional) Configuring Push Notifications in a Cluster

A cluster of PeopleSoft systems consists of:

  • A system designated as the portal (or hub).

  • One or more content provider systems.

As of PeopleTools 8.56, any PeopleSoft application can be designated the portal system for configuration of unified navigation. PeopleSoft Interaction Hub is no longer required.

To create a cluster configuration:

  1. Configure the integration gateway on each system.

  2. Configure the integration network on each system.

  3. Configure single signon (SSO) on each system.

See the steps outlined in Portal Technology: Configure Unified Navigation Fluid Navigation Collection for information on how to create a cluster configuration.

Then, configure the cluster so that push notifications are propagated from the content providers to the designated portal system:

  1. Add the ps_theme custom property to the active web profile on each content provider system to point to the default local node and URL for the portal system. Use the following format to set the value of this property:

    DEFAULT_LOCAL_NODE:http://my_server.my_domain:port_no/psp/SITE_NAME/

    For example:

    PS_NODE:http://server01.example.com:8000/psp/MYSITE01/

    For more information on setting custom web profile properties, see Portal Technology: Configuring Custom Properties,

  2. Configure routings for the PTPN_ASYNC_PUBLISH service operation on each system:

    • On each content provider system, outbound routing as local to the portal system.

    • On the portal system, inbound routing as any to local.

    For more information on configuring service operations, see Integration Broker: Adding Routing Definitions.

Finally, synchronize notification preferences across the cluster:

  1. Configure the PTPN_NOT_PREF_ASYNC service operation on each system:

    • Add the PTPT1000 permission list for service operation security.

    • On the portal system, configure outbound routings to be local (portal system) to each content provider; inbound routing as any to local.

    • On the each content provider system, configure the outbound routing to be local to the portal system; inbound routing as any to local.

  2. On each content provider system only, run the PTPN_NOTCONF Application Engine program using the System Process Requests page.