This topic containsan overview and discusses:
Configuring an applicationserver domain for push notifications.
(Optional) Configuringthe Process Scheduler domain for push notifications.
(Optional) Completing inter-domainconfiguration.
(Optional) ConfiguringProcess Scheduler system settings for push notifications.
(Optional) Adding a PeopleToolsoption to disable and re-enable push notifications.
(Optional) Configuringpush notifications in a cluster.
Troubleshooting the notificationsconfiguration.
To receive push notificationson a PeopleSoft system, you have to enable push notifications forthe server domains where the events are being published. Events arepublished from the application server domain and optionally from theProcess Scheduler domain. By enabling push notifications within adomain, the Tuxedo Event Broker will be started in the domain, whichis the TMUSREVT server process.
As of PeopleTools 8.58,you do not need to explicitly configure the web server for push notifications.The EnablePNSubscriptions custom web profile property is no longerused, and is ignored regardless of its setting.
Note: Events raised in a ProcessScheduler domain are ultimately routed through an application serverdomain. For these inter-domain events, you have to set inter-domainconfigurations for both the application server and the Process Scheduler.
This topic assumes youhave a working knowledge of PeopleSoft server administration. Formore information on managing PeopleSoft servers, see Using PSADMIN.
Each application serverdomain that will trigger and publish events must be configured forpush notifications using psadmin.
To enable push notificationsin an application server domain:
Run psadmin.exe.
Select the applicationserver domain.
Select Configure this domain.
Enter 13 (Push Notifications)to enable push notifications from the Quick-configure menu.
The push notificationsoption is set to No (disabled) by default.
Optionally, if the ProcessScheduler domain will also trigger and publish events, then inter-domainconfiguration between the server domains is also required. Enter 12 (Domains Gateway)on the quick-configure menu.
Enter 14 to load themodified configurations settings.
Boot (or reboot) the domainand verify that the TMUSREVT server process starts along with theother domain server processes. In addition, if the domains gatewaywas enabled, verify that the GWTDOMAIN process is also started.
Each Process Schedulerserver domain that will trigger and publish events must also be configuredfor push notifications using psadmin.
To enable push notificationsin a Process Scheduler domain:
Run psadmin.exe.
Select the Process Schedulerdomain.
Select Configure this domain.
Enter 4 (Domains Gateway)on the quick-configure menu.
Enter 5 (Push Notifications)to enable push notifications from the Quick-configure menu.
Enter 6 to load themodified configurations settings.
Boot (or reboot) the domainand verify that the TMUSREVT and GWTDOMAIN server processes startalong with the other domain server processes.
Note: After the Process Schedulerserver is configured with a Domains Gateway, additional configurationof both servers is required to complete inter-domain configuration.
To complete the inter-domainconfiguration, you need to copy the Process Scheduler access pointID to each application server’s configuration. Then, you need to copythe application server access point ID to the Process Scheduler’sconfiguration. By default on PeopleSoft systems, the Process Schedulerlistens on port 8988 for inter-domain connections; and the applicationserver listens on port 7988. After rebooting both domains, check theTuxedo log files to ensure that the inter-domain connection has beenestablished.
An application serverdomain can be configured to receive push notification events fromone or more Process Scheduler domains simultaneously. While a ProcessScheduler domain can be configured with more than one applicationserver domain, the Process Scheduler domain connects to only one applicationserver domain the when the Process Scheduler domain is booted. Theother configured application server domains remain available as fail-overservers. However, the configuration does not specify a primary serverand fail-over servers explicitly. When the Process Scheduler domainis booted, a connection is established by Tuxedo to one of the availableservers.
As a first step as describedin previous tasks, you must configure the application server and ProcessScheduler domains to generate the inter-domain events configuration(interdom.gbb files for each domain).
This example illustrateshow the configuration settings for inter-domain events can be copedfrom a Process Scheduler domain to an application server domain andvice versa. The access point IDs and port values must match on bothdomains to ensure successful transactions.
Configuring theApplication Server Domain for Inter-Domain Events
Note: When your environmentconsists of multiple application server domains, you can configureany one of the application server domains for inter-domain events.
To configure inter-domainevents for the application server domain:
Run psadmin.exe.
Select the Process Schedulerdomain.
Select Configure this domain.
Enter the 15 the Customconfiguration option.
Press the Enter key for Do you want to change anyvalues (y/n/q)? [n], and continue to press the Enter keyuntil the Valuesfor config section – Inter-Domain Events appear.
Review and modify as neededthe values in inter-domain events:
Process Scheduler Credentials=PRCS1|localhost:8988Application Server Port=7988Field or Control
Description
Process Scheduler Credentials
Specify the credentials for each Process Scheduler domain from which notifications will be received in the format:
Process Scheduler Credentials=ACCESSPOINTID|HOST_NAME:PS_portACCESS_POINT_ID: Open the PS_CFG_HOME\appserv\prcs\DOMAIN_ID\interdom.gbb file for the Process Scheduler domain. Locate the section in the file that is similar to the following::
*DM_LOCAL"PRCS" GWGRP=GWTGROUP1 ACCESSPOINTID="PRCS_SERVER01_PSNT1234"Note: The ACCESSPOINTID must be 30 bytes or fewer in length—that is, it must be 30 characters or fewer (including the trailing Null character).
HOST_NAME: The host name of the machine that is running Process Scheduler domain.
PS_port: The port number provided in the interdom.gbb file for the Process Scheduler domain. Each Process Scheduler domain must have a unique port number.
The completed configuration values for the Process Scheduler domain will look similar to the following example:
Process Scheduler Credentials=PRCS_SERVER01_PSNT1234|SERVER01:8988Note: If there are multiple Process Scheduler domains from which you want to receive push notifications, then provide the configuration for each domain separated by a comma. For example:
Process Scheduler Credentials=PRCS_SERVER01_PSNT1234|SERVER01:8988,PRCS_SERVER01_PSNT5678|SERVER01:8999Application Server Port
You can retain the portnumber as is.
Enter q to returnto the PeopleSoftDomain Administration menu, and load any configurationchanges.
Boot the application serverdomain.
Configuring theProcess Scheduler Domain for Inter-Domain Events
To enable inter-domainevents for a Process Scheduler domain:
Run psadmin.exe.
Select the Process Schedulerdomain.
Select Configure this domain.
Enter the 7 the Customconfiguration option.
Press the Enter key for Do you want to change anyvalues (y/n/q)? [n], and continue to press the Enter keyuntil the Valuesfor config section – Inter-Domain Events appear.
Review and modify as neededthe values in inter-domain events:
Values for config section - Inter-Domain Events Process Scheduler Port=8988 Application Server Credentials=APPDOM1|localhost:7988Field or Control
Description
Process Scheduler Port
Specify the port throughwhich this Process Scheduler domain sends event notifications.
Note: You can leave the portvalue as is if you are configuring a single Process Scheduler domain.If you are configuring inter-domain events for multiple Process Schedulerdomains on the same machine, then specify a unique port number foreach domain.
Application Server Credentials
Specify each applicationserver domain to which this Process Scheduler domain can connect inthe following format:
Application Server Credentials=ACCESSPOINTID|HOST_NAME:AS_portACCESS_POINT_ID: Open the PS_CFG_HOME\appserv\DOMAIN_ID\interdom.gbbfile for the application server domain. Locate the section in thefile that is similar to the following:
*DM_LOCAL"AS_T85704AA_41162" GWGRP=GWTGROUP ACCESSPOINTID="T85704AA_41162"Note: The ACCESSPOINTID mustbe 30 bytes or fewer in length—that is, it must be 30 characters orfewer (including the trailing Null character).
HOST_NAME: Thehost name of the machine, which is running application server domain.
AS_port: Theport number provided in the interdom.gbb file for the applicationserver domain. You can leave the default value of the port as is.
The completed configurationvalues for the application server will look similar to the followingexample:
Application Server Credentials=T85704AA_41162|SERVER01:7988Enter q to returnto the PeopleSoftDomain Administration menu and load any configurationchanges.
Boot the Process Schedulerdomain.
View the TUXLOG files toverify that the inter-domain configuration is valid and that the domainsare connected to each other:
PS_CFG_HOME\appserv\DOMAIN_ID\LOGS\TUXLOG.TODAYPS_CFG_HOME\appserv\prcs\DOMAIN_ID\LOGS\TUXLOG.TODAY
Search for GWTDOMAIN nearestthe end of the log file and evaluate the log entry to determine thestatus of the connection. The following examples are from a ProcessScheduler log file:
Success:
192615.EDVMR1P0!GWTDOMAIN.4560.2512.0: LIBGWT_CAT:1129: INFO: Connection established with domain (domainid=<T1B85701_42446>)Failure:
192356.EDVMR1P0!GWTDOMAIN.6700.6724.0: LIBGWT_CAT:1073: ERROR: Unable to obtain remote domain id (T1B85701_32872) information from shared memory192356.EDVMR1P0!GWTDOMAIN.6700.6724.0: LIBGWT_CAT:1509: ERROR: Error occurred during security negotiation - closing connection
Note: If you have multipleProcess Scheduler domains on the same machine, then this configurationneeds to be completed on each of the Process Scheduler domains.
Related Links
PTPNInterdomainConfig
Note: If you do not createthis personalization option, push notifications remain enabled systemwide.
You can add a PeopleToolspersonalization option to disable or re-enable push notificationssystem wide:
Select PeopleTools > Personalization > PersonalizationOptions.
Search for and select PPTL.
Add a row to the grid withthe following values:
Field or Control
Description
User Option
PNSUBSCR
Description
Push Notifications Enabled
Option Category Group
PS Internet Architecture
Option Category
General Options
User Option Type
System
Record (Table) Name
PSXLATITEM
Field Name
PSYESNO
Option Default Value
Click the Set OptionDefault Value link and select:
Yes — Pushnotifications remain enabled system wide.
No — Push notificationsare disabled system wide until they are re-enabled by this personalizationoption.
Save your changes.
Use the NotificationConfiguration page to enable or disable notifications for specificProcess Scheduler status changes on a system-wide basis.
Navigation:
PeopleTools > Process Scheduler > Process SchedulerSettings > Notification Configuration
This example illustratesthe fields and controls on the Process Scheduler - Notification Configurationpage. You can find definitions for the fields and controls later onthis page.
When a status optionis enabled and inter-domain communication has been configured, the notificationsfor that status change are propagated from the Process Scheduler serverthrough the application server to the following channels: Notificationwindow, pop-up notifications, and email.
For pop-up notifications,in addition to system-wide settings, each user must enable pop-upnotifications as well as specific status options in My Preferences.However, each user does not need to configure the Notification windowto receive notifications from the Process Scheduler.
Related Links
Defining Notification Configuration
Specifying General Settings in My Preferences
A cluster of PeopleSoftsystems consists of:
A system designated asthe portal (or hub).
One or more content providersystems.
As of PeopleTools 8.56,any PeopleSoft application can be designated the portal system forconfiguration of unified navigation. PeopleSoft Interaction Hub isno longer required.
To create a clusterconfiguration:
Configure the integrationgateway on each system.
Configure the integrationnetwork on each system.
Configure single signon(SSO) on each system.
See the steps outlinedin Configure Unified Navigation Fluid Navigation Collection for information on how to create a cluster configuration.
Then, configure thecluster so that push notifications are propagated from the contentproviders to the designated portal system:
Add the ps_theme customproperty to the active web profile on each content provider systemto 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 informationon setting custom web profile properties, see Configuring Custom Properties,
Configure routings forthe PTPN_ASYNC_PUBLISH service operation on each system:
On each content providersystem, outbound routing as local to the portal system.
On the portal system, inboundrouting as any to local.
For more informationon configuring service operations, see Adding Routing Definitions.
Finally, synchronizenotification preferences across the cluster:
Configure the PTPN_NOT_PREF_ASYNCservice operation on each system:
Add the PTPT1000 permissionlist for service operation security.
On the portal system, configureoutbound routings to be local (portal system) to each content provider;inbound routing as any to local.
On the each content providersystem, configure the outbound routing to be local to the portal system;inbound routing as any to local.
On each content providersystem only, run the PTPN_NOTCONF Application Engine program usingthe System Process Requests page.
If events are not appearingin the Notification window, check the following items:
Verify that the web profilepasswords are consistent between the web server domain and the applicationserver domain.
Verify that your browser,web server, and any reverse proxy servers used all support WebSockettechnology.
To troubleshoot thenotification configuration for push notifications published from aProcess Scheduler domain, you also need to consider the following:
After booting up the domains,you can verify the configuration by ensuring that the domains haveconnected to each other. To verify the connection, you need to openthe TUXLOG file for application server and Process Scheduler domainsfrom their respective domain LOGS folders. You will see an entry inthe file that the connection is established between the domains.
If you do not see connectionsbeing established, then reboot the domains after clearing IPC resourcesfor the domains. Use the Clean IPC resources of this domain optionin psadmin and then reboot the domains.
Testing Push NotificationsPublished from the Application Server Domain
To test the push notificationspublished from an application server domain:
Select PeopleTools > Portal > Inter WindowCommunication.
Search and select PortalObject Name: PTSVRTESTEVENTS_GBL.
In the Content ReferenceMessage Events grid, click the Map icon for SERVEREVENTTESTA.
On the Map Event Data toPage Elements Modal window, click OK, and click Save.
Note: You need to completethis only once on a new installation.
Using two different browsersessions navigate to PeopleTools > Utilities > Debug > Server SideEvents Test Page.
Enter test values in theEvent Data field and click Publish on one browser session.
On the other browser session,confirm that the values you just entered appear in the Event Targetsfields.
