Kyle and Dan continue the discussion of DPK-based PeopleSoft Images. Dan shares a few frustrations with the new PI’s, we both learn a new way to generate trace files, and brainstorm how to manage the DPK’s YAML files.
We want to make this podcast part of the community discussion on PeopleSoft administration. If you have comments, feedback, or topics you’d like us to talk about, we want to hear from you! You can email us at email@example.com, tweet us at @psa_io, or use the Twitter hashtag #psadminpodcast.
You can listen to the podcast here on psadmin.io or subscribe with your favorite podcast player using the URL below, or subscribe in iTunes.
- CORS Support in 8.54: 2099484.1
- First 8.56 Reference in MOS: 2086326.1
- Tracing IB Handlers: 2079310.1
- SetTracePC() and SetTraceSQL() Functions
- LeanITDesigns DPK Review and Hostname bug
One thought on “#17 – PI’s and DPK’s (Part 2)”
Hey great podcast. So many things I’ve dealt with, CORS Web Profile setting in 8.54, Cobol, etc.. Had to deal with CORS for a Shibboleth front end. As for your own custom web profile properties. These can be used in your “look and feel” signin.html, siginout.html, pages. We used it for a maintenance window notice to users on login page. You can use it like other “bind” variables. It allowed the maintenance time to be configured in web profile:
We also built our own custom cobol compiler script (Linux) that spoofs a “HOME” environment variable that achieved the same result as you noted having all compiled results in cust home. Since we started the script, we added INAS stuff and run the store.dms automatically, and let our migrators run it through STAT. Saves a lot of my admin time.
My 2 cents, DPK is good for PUM (though so were the past scripts), but for real world, it was useless for us. We started to use ansible to automate Peoplesoft, then discovered the Puppet DPK, and found it disappointing, complex, and limited flexibility to our architecture. Considering the standalone use of Puppet, and the user audience, I’m a bit surprised they didn’t use ansible. I found it more useful for application deployment and more flexible to add custom architecture configs (which we have a lot of).