#78 – Cloud Manager and Certifications w/ Mark Hoernemann

This week Mark Hoernemann joins us to talk about platform certifications with PeopleTools. Mark explains how the PeopleTools team determines what platforms to support and how the support policies work. Then Mark gives us more details on the PeopleSoft Cloud Manager.

Show Notes

  • Bringing App Engine to an SQR Discussion @ :45
  • Overriding Facter Facts @ 5:00
  • COBOL DPK and Unicode @ 7:45
  • Mark Hoernemann Interview @ 9:30
    • Deciding what platforms to support @ 11:45
    • SQL Server 2016 certification @ 15:30
    • Why platforms are dropped from support @ 18:00
    • Supporting frequent browser releases @ 20:00
    • 8.56 certification changes @ 24:00
    • Cloud Manager @ 24:45
    • Self Service Environment Administration @ 28:30
    • Getting Started with Cloud Manager @ 29:45
    • Building environments with Cloud Manager @ 37:00
    • Applying PeopleTools patches when provisioning environments @ 40:15
    • New PeopleTools features between releases @ 43:30

Configure Push Notifications

Thanks to Andy Dorfman for allowing us to guest-post his Push Notification setup. Andy did a lot of work to get Push Notifications working in a production environment and he’s sharing his notes. If you are looking to get Push Notifications running, this is a great place to start.

User Story

As a PeopleSoft user, when scheduling a process to run on a process scheduler, I would like to receive a Push Notification about the status of the process, as well as the link to the process output.

System Architecture:

  • 2 application servers

    • ps-apps-01
    • ps-apps-02
  • 2 process schedulers

    • ps-prcs-01
    • ps-prcs-02

Implementation:

Prerequisites:

  1. Until fixed in PeopleTools, on each server in PS_HOME\appserv\local_prcsgw.gbx, at ~ line 50, enclose ACCESSPOINTID value by "", i.e. change

    "PRCS_{$Inter-Domain Events\Process Scheduler Credentials[1]}"    ACCESSPOINTID={$Inter-Domain Events\Process Scheduler Credentials[1]}
    

    to

    "PRCS_{$Inter-Domain Events\Process Scheduler Credentials[1]}"    ACCESSPOINTID="{$Inter-Domain Events\Process Scheduler Credentials[1]}"
    
  2. Firewall needs to be configured to allow communication from ps-apps-01 and ps-apps-02 to ps-prcs-01:8988 and ps-prcs-02:8988, i.e. each application server needs to be able to reach both process schedulers on port 8988. It could potentially be possible to restrict source port range for greater security as well.

  3. Firewall needs to be configured to allow communication from ps-prcs-01 and ps-prcs-02 to ps-apps-01:7988 and ps-apps-02:7988, i.e. each proces scheduler needs to be able to reach both application servers on port 7988. It could potentially be possible to restrict source port range for greater security as well.

Configuration:

  1. In application server configuration, define distinct “Domain ID”s (aka [Domain Settings]\Domain ID), e.g.

    • AS1 on ps-apps-01
    • AS2 on ps-apps-01

    values can be any valid sting for [Domain Settings]\Domain ID, as long as they are distinct

  2. In process scheduler server configuration, define “PrcsServerName”s (aka [Process Scheduler]\PrcsServerName), e.g.

    • PS1 on ps-prcs-01
    • PS2 on ps-prcs-02

    values can be any valid sting. Developer statated that Application servers currently don’t look at ACCESSPOINTID for process scheduler domains and only care about the hostname:port, but if you want multiple Process Scheduler domains, the names have to be distinct regardless.

  3. On each application server domain and process scheduler domain, enable Inter-Domain Communication and Push Notifications

  4. Setup Application Server

    1. On each application server, examine PS_CFG_HOME\appserv\<DOMAIN>\interdom.gbb. Pay special attention to uncommented lines that start with “AS_<Domain ID>_<IPCKEY>”, e.g.

      "AS_AS1_53252"    GWGRP=GWTGROUP  ACCESSPOINTID="AS1_53252" CONNECTION_POLICY=ON_STARTUP
      "AS_AS1_53252"    NWADDR="//PS-APPS-01:7988"
      

      only NWADDR is important here, ACCESSPOINTID will be you Application Server Domain ID from (1)

    2. Assemble the following string using the known information

      "AS1|PS-APPS-01:7988,AS2|PS-APPS-02:7988"
      

      notice AS1 comes from (1), while ps-apps-01:7988 comes from NWADDR in (4.1). The multiple application server domain connection strings are separated by a “,” with no space.

    3. This string above would go into each process scheduler domain configuration under [Inter-Domain Events]\Application Server Credentials, either via psadmin custom configuration or manually

      [Inter-Domain Events]
      ;=========================================================================
      ; InterDomain Event settings
      ;=========================================================================
      Process Scheduler Port=8988
      Application Server Credentials=AS1|PS-APPS-01:7988,AS2|PS-APPS-02:7988
      
  5. Setup Process Scheduler

    1. Similarly, note the setting PS_CFG_HOME\appserv\prcs\<DOMAIN>\interdom.gbb on each process scheduler domain:

      "PRCS"    GWGRP=GWTGROUP1  ACCESSPOINTID="PRCS_PS-PRCS-01_PS1"  CONNECTION_POLICY=ON_STARTUP
      "PRCS"    NWADDR="//PS-PRCS-01:8988"
      

      Both ACCESSPOINTID and NWADDR are important in this case

    2. Assemble the following string using the known information

      "PRCS_PS-PRCS-01_PS1|PS-PRCS-01:8988,PRCS_PS-PRCS-02_PS2|PS-PRCS-02:8988"
      

      The format is ACCESSPOINTID|NWADDR,ACCESSPOINTID|NWADDR from (5.1). The multiple process scheduler connection strings are separated by ‘,’ with no space in between

    3. This string above should go into each application server configuration under [Inter-Domain Events]\Process Scheduler Credentials, either manually or through psadmin custom configuration menu, e.g.

      [Inter-Domain Events]
      ;=========================================================================
      ; InterDomain Event settings
      ;=========================================================================
      Process Scheduler Credentials=PRCS_PS-PRCS-01_PS1|PS-PRCS-01:8988,PRCS_PS-PRCS-02_PS2|PS-PRCS-02:8988
      Application Server Port=7988
      
  6. Clear IPC on each application server and process scheduler domain. Reconfigure and boot each application and process scheduler domain. The boot order does not matter, the ping happens every 60 seconds by default.

  7. Verify that the communication is successfully taking place by examining TUXLOG on each domain, e.g.

        094833.PS-APPS-01!GWTDOMAIN.3660.4520.0: LIBGWT_CAT:1128: INFO: Connection accepted from domain (domainid=<PRCS_PS-PRCS-01_PS1>)
    
  8. In PIA, navigate to “PeopleTools > Web Profile > Web Profile Configuration”. In “Custom Properties”, if not already there, set property EnablePNSubscriptions to true, save the profile and restart the Web Server domain.

  9. Optionally, in PIA, navigate to “My Preferences” and in “Pop-up Notification” section, set “Yes” for all States and for “Enable Popup Notification”. This will allow slide-in notifications

  10. Run XRFWIN and verify that slide-in notifications are occuring and alerts are populated under Notification Center.

#77 – Why the Cloud is Important w/ David Bain

This week on the podcast David Bain, Product Manager for PeopleTools, joins us to talk about Fluid, the Cloud and PeopleSoft, and his favorite PeopleTools features. Dan and Kyle also recap some great discussions they had at the Collaborate conference.

Show Notes

  • David Bain Interview
    • Why the cloud is important to PeopleSoft @ 2:00
    • Why Fluid is a better user interface @ 13:00
    • Favorite new PeopleTools feature @ 19:45
    • How PeopleSoft uses PTF internally @ 22:45
    • Favorite PeopleTools feature of all time @ 26:00
  • Recap of David’s Interview @ 28:00
  • Unsexy software features @ 38:00
  • “Hidden” PeopleTools features @ 39:30
  • Interaction Hub @ 45:45
  • Phire and a Testing Module @ 52:30

#76 – Hybrid Cloud w/ Jim Marion

This week on the podcast Jim Marion joins us to talk about Fluid Development, embedding PeopleSoft into cloud applications, Event Mapping, where the cloud makes sense and Jim’s new role at GreyHeller.

Show Notes

  • Jim’s Background @ 2:15
  • New Role with Grey Heller @ 3:45
  • Thoughts on the future of PeopleTools @ 6:00
  • Fluid Development @ 9:00
  • Improving App Designer @ 11:30
  • Event Mapping and Branding Objects @ 14:00
  • Using the Cloud at Grey Heller @ 25:45
  • Embedding PeopleSoft with Cloud Applications @ 32:00
  • Disadvantages of Hybrid Cloud Systems @ 43:30
  • Where the Cloud makes sense @ 47:30

#75 – Selling Yourself

This week, Dan and Kyle talk about testing different web server configurations, using the ACM for Elasticsearch, and how mobile browsers work with websites. Then, they discuss different ways to promote yourself and your position to a boss or organization.

Show Notes

Change Assistant Debug Mode

This is a short post, but hopefully helpful. I recently discovered that you can turn on Change Assistant with a debug mode using an environment variable. There is no documentation on this, but it seems to work well and might help you resolve any issues you have with Change Assistant.

To enable the debug mode, set the PSCADBG environment variable. I used “true” for the value, but any value should work.

$env:PSCADBG="true"

Then launch Change Assistant from the command line:

c:\Program Files\PeopleSoft\Change Assistant\changeassistant.bat

In the command line you should see the debug output, like this:

Signed on to 'PSFTDB'. Using c:\PT8.55.13_Client_ORA\
Attempt to signon using PS/PS@PSFTDB
Controller sending c:\PT8.55.13_Client_ORA client -com.peoplesoft.pt.changeassistant.pshome.request.db.SignOnDatabase
Controller received from c:\PT8.55.13_Client_ORA client -com.peoplesoft.pt.changeassistant.pshome.request.db.SignOnDatabase
Signed on to 'PSFTDB'. Using c:\PT8.55.13_Client_ORA\