PeopleSoft Deployment Package command lines

It is possible to install these domains separately on different machines using a DPKs. The DPK will have to be executed on each server with the proper install command.

the bootstrap has options to specify the domain_type (the default is all). You can execute the following command in PowerShell or Linux Batch process:

1. For App Server domain

--env_type midtier --domain_type appserver

2. For App Batch Domain (for App Server & Process Scheduler on on one machine)

--env_type midtier --domain_type appbatch

3. For PIA Domain

--env_type midtier --domain_type pia

4. For a Process Scheduler Domain

--env_type midtier --domain_type prcs

5. This command setups a fulltier (database and midtier) PeopleSoft environment using the DPK zips from the directory /opt/psft/dpks.

--dpk_src_dir /opt/psft/dpks

7. This command deploys just the PS_HOME. It does not setup any PeopleSoft environment. Just installs PS_HOME and none of the other 3rd party components.

--env_type midtier --deploy_only --deploy_type tools_home

[NOTE] For --deploy only commands, above, the “--deploy_type --deploy_only” option is broken in 8.55.01 which is bundled with PUM –HCM Image 16.

There is no workaround. If a customer is taking PUM image, this deploy-only option is not even valid as they need fulltier components.

The issue has been addressed in the 8.55.03 patch of PeopleTools. The Bug# is 22535736 - SERVER DPK - DEPLOY_ONLY WITH APPS DPKS CREATES PI_HOME.