How to Deploy Multiple DPKs with Different Puppet Versions on the Same Machine |

How to Deploy Multiple DPKs with Different Puppet Versions on the Same Machine

A PeopleTools DPK may be shipped with the same or different version of Puppet as compared to a different version of PeopleTools DPK. 

For example, PeopleTools 8.58 DPK comes with Puppet version 5.5.14 whereas PeopleTools 8.57 DPK comes with Puppet version 5.3.5.  

It is a common practice to install multiple PeopleSoft application or multiple PeopleTools on a single machine but then with the introduction of DPKs, a challenge had been that it would only allow a single version of Puppet to be installed.

So, as a workaround, you had to do things like unintall the existing Puppet version and then use the DPKs to install another version of Puppet.

Here is your guide to completely uninstall Puppet.

With PeopleTools 8.58, there is an easier option to maintain multiple PeopleSoft Applications at different PeopleTools releases on the same machine when each DPK requires a specific version of Puppet!

Deploying Different Versions of Puppet on the Same Host Machine

PeopleTools 8.58 DPK introduced a new parameter: --use_alternate_puppet_install for both Microsoft and Linux DPKs.

This option can be used for any supported deployment starting with PT 8.58 but you cannot install Puppet in a separate step unless you perform some manual workarounds to get arounds the situation.

When the parameter --use_alternate_puppet_install is used during a DPK deployment, Puppet gets installed under the BASE_DIR that is specified when running the DPK setup script. 

Additional Things to Note:

  • Puppet will be installed in BASE_DIR/psft_puppet_agent.
  • You cannot specify a different installation location.
  • The Puppet installation is deployment-specific i.e. each setup that is run with this command has its own Puppet installation.
  • This installation does not modify environment variables or the Microsoft Windows registry, so you may need to manually manipulate the environment variables whenever need arises.

Examples of --use_alternate_puppet_install parameter: 

psft-dpk-setup.<ext> --env_type midtier --use_alternate_puppet_install

psft-dpk-setup.<ext> --env_type midtier --deploy_only --use_alternate_puppet_install

psft-dpk-setup.<ext> --env_type midtier --domain_type appserver --use_alternate_puppet_install.

To cleanup this Puppet installation, you need to run:
psft-dpk-setup.<ext> --use_alternate_puppet_install --cleanup

Apurva Tripathi