#121 – Under Review

That’s right, its another Change Assistant episode. Dan shares some updates to Change Assistant in 8.56, some 8.57 speculation, and applying PeopleTools Upgrades headlessly. Kyle shares an ACM discovery, and the PeopleTools Idea Space updates.

Show Notes

#119 – Installing Change Assistant

This week on the podcast, Dan and Kyle talk about cloud provisioning tools and how they could work for PeopleSoft Admins, Mike Ripley’s POC for securing WebLogic, and changes to the Change Assistant installation process.

Show Notes

Change Assistant 8.56 Installation Changes

Starting in Change Assistant 8.56, a new file is used to track the installations of Change Assistant, C:\Windows\PeoplesoftCA.txt. While Change Assistant 8.55 let us install multiple versions at the same time, 8.56 now tracks which your Change Assistant installations.


1 8.56.05  c:\psft\ca\hr025-8.56.05
2 8.56.05  c:\psft\ca\hrtst-8.56.05

The Change Assistant installer scripts set the path for the file. On Windows, is uses the WINDIR environment variable and on Linux it generates a temporary folder.

if isWin() :
  winpath = os.environ['WINDIR']
else :
  winpath = tempfile.gettempdir()

The C:\Windows location doens’t seem like the best place to store this file though. C:\Windows is for Windows files, not for vendor configuration. I’d like to see this stored in a better location, like C:\ProgramData\Peoplesoft.

If you run into errors when installing Change Assistant, especially in early releases of 8.56, try deleting the PeoplesoftCA.txt file. Earlier versions of Change Assistant used this format of the file (this is from Change Assistant 8.56.03):


There are multiple ways to install Change Assistant with 8.56.

  1. tools_client\setupPTClient.bat on the PeopleSoft Image
  2. Use the setup.bat file under PS_HOME\setup\PsCA
  3. Silent Install option:

    .\silentInstall.bat c:\psft\ca\hr025-8.56.05 NEW NOBACKUP
    .\silentInstall.bat c:\psft\ca\hcmpum UPGRADE NOBACKUP

A few changes to the installation process:

  1. Installing an older version of Change Assistant will error if the PeoplesoftCA.txt has a newer version in it.
  2. The PeopleTools Installation Guide for 8.56 references the installer as setup\PsCA\installCA.exe, but in the latest 8.56.05 client tools that file does not exist.
  3. Instead, there is a setup.bat script to perform the installation.
  4. At OpenWorld, we heard that 8.56 included Change Assistant for Linux but you had to look for it. Now we have a setup.sh script for Change Assistant on Linux.
  5. The installation process is powered by Python, not an installation wizard. This follows suit with the DPK changes and supports multiple platforms.

#117 – Invalid Views

This week on the podcast, Dan and Kyle discuss a WebLogic exploit used for currency mining, Dan revisits the Health Center in the latest PeopleSoft Images, and Kyle explains why you need to review the Invalid View project.

Show Notes

#115 – “Old School” Patching

This week on the podcast, Kyle goes back to applying bundles and appreciates all the improvements to Change Assistant. Dan shares his research of “Slow PO Output” and what was really going on.

Show Notes

#93 – Forced Adoption

This week on the podcast, Kyle recaps the Phire User Group meeting, his PTF talk, and shares a nice tip on integrating Usage Monitor with PTF scripts. Then, Dan and Kyle discuss the latest changes with HR Image 23 and PeopleTools 8.56 and forcing users to adopt new technologies.

Show Notes

#87 – PeopleTools 8.56

PeopleTools 8.56 has been released. This week on the podcast we talk about new features in 8.56 that we are excited about and dive into some of the changes to Deployment Packages.

Show Notes

  • 8.56 is out! @ 2:00
  • Platform Changes @ 4:45
  • Fluid Changes @ 7:00
  • Event Mapping API? @ 11:00
  • Searching Improvements @ 11:45
  • PUM @ 14:00
  • Portal Changes @ 18:30
  • Unified Navigation @ 21:00
  • PTSYS Database @ 26:30
  • Classic Plus @ 30:15
  • PSCBO @ 34:30
  • Role/PL Aliases @ 35:15
  • Event Mapping @ 37:45
  • VCD Still Around @ 40:00
  • Change Assistant @ 41:45
  • Deployment Packages @ 48:00
  • RECONNECT @ 68:00

Change Assistant Debug Mode

This is a short post, but hopefully helpful. I recently discovered that you can turn on Change Assistant with a debug mode using an environment variable. There is no documentation on this, but it seems to work well and might help you resolve any issues you have with Change Assistant.

To enable the debug mode, set the PSCADBG environment variable. I used “true” for the value, but any value should work.


Then launch Change Assistant from the command line:

c:\Program Files\PeopleSoft\Change Assistant\changeassistant.bat

In the command line you should see the debug output, like this:

Signed on to 'PSFTDB'. Using c:\PT8.55.13_Client_ORA\
Attempt to signon using PS/PS@PSFTDB
Controller sending c:\PT8.55.13_Client_ORA client -com.peoplesoft.pt.changeassistant.pshome.request.db.SignOnDatabase
Controller received from c:\PT8.55.13_Client_ORA client -com.peoplesoft.pt.changeassistant.pshome.request.db.SignOnDatabase
Signed on to 'PSFTDB'. Using c:\PT8.55.13_Client_ORA\

#74 – Killing COBOL

This week on the podcast, Kyle and Dan talk about planning PeopleTools and Catch-up projects, BI Publisher security, and how to turn off excessive BI Publisher logging. We also talk about slowly killing COBOL with PeopleSoft (it’s not dead yet) and using multiple Change Assistant installations.

Show Notes

Running Change Assistant without “as Administrator”

One annoyance with Change Assistant (among a few) is that you have to start it “as Administrator”. If you don’t, you’ll get the message “Another instance of Change Assistant is already running” (even though it’s not). While running a program “as Administrator” is not hard, there is no reason why Change Assistant needs Administrative rights. (At least that I know of).

Folder Security

The fix to run Change Assistant without Administrator is to set the folder security permissions correctly. If you install Change Assistant to the default directory, C:\Program Files\PeopleSoft\Change Assistant, the Change Assistant folder security needs to be updated. Grant the user (or group) who will be running Change Assistant Full Control over the directory. In my case, I granted the group “Authenticated Users” full access to the folder.

Screen Shot 2017-03-08 at 5.17.53 PM

Now you can start Change Assistant as a normal application.

PeopleTools Idea

There is an Idea on the Oracle PeopleSoft Space for the PeopleTools team to fix this. If you want to vote for the Idea, you can do that here.

I don’t remember where I originally saw this solution, so I can’t give appropriate credit, but I want to thank whoever posted about this in the past.