In Part 1, Fix NativeOS DPK Issues on Windows, we covered the service changes and TNS Listener change to resolve issues with the NativeOS DPK. But, I realized today that I approached the TNS Listener issue the “old way”. We are working with DPK’s now and there is a different method to manage configuration changes: Puppet and Hiera.
In the new 8.55/DPK setup, configuration changes are handled in the
psft_customizations.yaml Hiera file.
psft_customizations.yaml overrides the default configuration provided by the DPKs. So, if we want to change the Oracle Listener port, let’s add it the YAML file.
Don’t forget the
---at the top of the file. The
---is a file delimiter; you can include more than one YAML “file” inside a physical
Copy the file to
Fresh Install v. Existing Install
The theory behind Puppet (and the DPK’s) is that you describe your configuration and Puppet does the implementation. In our case above we have changed the configuration of
db_port. If this was an existing installation of the DPK (e.g, you’ve already build HR 9.2 Image 16 using the DPK), we should be able to change that value. Unfortunately, the Puppet providers for PeopleSoft aren’t that robust. (I hope that is a feature that will be released). If you have already installed your PeopleSoft Image, you can make the change above, but when you run
puppet apply site.pp the listener port is not updated.
But, if you are installing a NativeOS-based PeopleSoft you can include this change. When you run the bootstrap script, you are presented with the question “Do you want to continue the default initialization process?”. Answer
No. (This [poorly worded] question means: Do you want to change any configuration?)
At this point, the bootstrap script will stop and you can copy your
psft_customizations.yaml file into the
data folder. Once your change is in place, we just start the Puppet process using
puppet apply site.pp
You need to run the
puppet apply site.ppcommand from