This content has been marked as final. Show 4 replies
hzg wrote:That's wrong, Peopletools includes binaries (PS_HOME), the client (AppDesigner, DataMover) and eventually the database.
...I understand that all the changes for peopletools are stored in database, so we can just move it to the database of the production environment by using AD. Should I move or install the new peopletools to the production environment?
Going from 8.49 to 8.52 may also imply a change of hardware (check the certification matix).
How to find and resolve the error of the old customized after upgraded?Test ?
Thanks Nicolas,you’re right. It changed including binaries (PS_HOME), the client and so on.
I know that when I apply the maintenance pack for the HRCS, there are some steps that the change assistant will transfer some files to my test environment or file server. After that, I can instead the old PS_HOME of production by that PS_HOME in my test environment or file serve, and compare and migrate the new from the database to the production database. But for upgrade the peopletools only, I don’t see any step like those. Should I install the new release peopletools to the old PS_HOME instead?
In PeopleTools upgrade, the CA doesn't deploy files as it does in applying an MP. All the scripts, projects etc are coming from the new release PeopleTools.
So, yes, you need to install the new release Tools. You need to install it to a new location not on top of the old PS_HOME
Check the Tools upgrade documentation for details