This content has been marked as final. Show 6 replies
For your first point :
Did you reconfigure the AppServ and Prcs based on the new config file ?
For your second point :
Open the DataMover toolin bootstrap mode, and run the following command :
CHANGE_ACCESS_PASSWORD SYSADM1 new_password;SYSADM1 is your symbolic id (check it into PSACCESSPRFL)
new_password is the new password for the Oracle user (SYSADM)
This command will change the SYSADM Oracle password, and that will update the PSACCESSPRFL table as well and will encrypt the entry (ACCESSID and ACCESSPSWD).
I don't get you on that point.
i also want to block access of people tools
restricting peopletools means that nobody could login to datamover in either regular/bootstrap mode and also to application designer.
Do you really want to disallow all the DMS connection against your application ?
Well, you can limit by the application ROLE, by removing the PeopleTools role from the authorized list of users.
But remove the bootstrap mode access... why ? How do you think to manage the fixes scripts ?
I posted a blog entry on this topic a while back. It's at http://www.erpassociates.com/peoplesoft-corner-weblog/peopletools/changing-peoplesoft-admin-passwords.html.
The best way to change SYSADM is to use data mover and the change_access_password command. All PeopleSoft user passwords are encrypted with SYSADM's password as part of the key, so if you change this at the database only, nobody will be able to log on.
There is a dms in the scripts folder of ur fileserver, resetpswd.dms.
make the neccessary modification to that script and run it in bootstrap mode.once you are done with that do edit psappsrv.cfg for the new passwords. i hope that should do the job. This is not very different from what others have suggested but its a lot more easier as peoplesoft itself have provided a script for the same.