Working with PS_APP_HOME
This topic contains an overview and discusses how to manage environments where PS_APP_HOME has been implemented.
PS_APP_HOME refers to the installation location for the PeopleSoft application software. In previous PeopleSoft releases, you installed PeopleTools into a high-level directory referred to as PS_HOME, and then you installed your PeopleSoft application into the existing PS_HOME location such that PeopleTools and your PeopleSoft application coexisted within the same directory structure. In the current release, this configuration is not supported. PS_APP_HOME must not be the same as PS_HOME.
The installation performed by the PeopleSoft Deployment Packages (DPKs) supports only separate PS_APP_HOME and PS_HOME. For information on the default installation locations for PS_HOME and PS_APP_HOME set by the DPKs, see the PeopleSoft PeopleTools Deployment Packages installation guide on the PeopleSoft PeopleTools Patches Home Page, My Oracle Support, Doc ID 2062712.2.
The separate PS_APP_HOME configuration includes the following benefits:
PeopleTools patches and updates can be applied knowing that no application content has been disturbed. Likewise, PS_APP_HOME application updates can be applied independently.
Increased flexibility and modularity in that a single PS_HOME can be associated with multiple PS_APP_HOME locations.
Disk space savings, due to shared PS_HOME amongst multiple PS_APP_HOME locations. Using the traditional method, each application installation requires its own PeopleTools installation.
When troubleshooting it will be easier to isolate application and PeopleTools issues.
As you configure your system, you need to be mindful of the PS_APP_HOME location. When you run PSADMIN, the PS_APP_HOME location is listed.
In many of the configuration settings where PS_APP_HOME might be involved, PeopleTools includes both PS_APP_HOME and PS_HOME references. For example,
RCCBL PRDBIN=%PS_APP_HOME%/cblbin:%PS_HOME%/cblbinIn environments where PS_APP_HOME has been implemented, system elements such as server domains have access to content supplied by both PS_HOME and PS_APP_HOME, but files added by the PeopleSoft application installation (those residing in PS_APP_HOME) that have the same name as those in the PeopleTools PS_HOME take preference.
The following table outlines key areas in the PeopleSoft system, where you need to consider the PS_APP_HOME location for your PeopleSoft applications. When you are installing, configuring, and maintaining your system, make sure to keep these items in mind and review the documentation associated with these areas.
|
PeopleSoft Infrastructure Element |
PS_APP_HOME Consideration |
|---|---|
|
Application Server |
Remote Call COBOL can look for COBOL programs in both PS_APP_HOME or PS_HOME, so be sure to review those settings. See RCCBL PRDBIN. |
|
Process Scheduler |
The Process Scheduler domains reference PS_APP_HOME and PS_HOME locations for the following processes:
See Understanding the PeopleSoft Process Scheduler Configuration File. |
|
COBOL |
During your installation, you will need to perform different tasks when compiling COBOL. See the product documentation for PeopleSoft 9.2 Application Installation, "Installing and Compiling COBOL on UNIX" or "Installing and Compiling COBOL on Windows." |
|
SQR |
When specifying locations where the system should look for SQR reports, for example, in Process Scheduler or in Configuration Manager, make sure to consider reports that may exist in PS_APP_HOME. |
|
Lifecycle Management |
For applying updates and performing upgrades, PS_APP_HOME also needs to be considered for various tasks, including:
|
|
Windows Development Environment |
When setting up Windows Development workstation profiles using Configuration Manager, you set the PS_APP_HOME variable on the Process Scheduler tab, and you'll also consider your PS_APP_HOME location when specifying:
|