|
|
|
Re:Most important admin commands, processes, configuration files in PeopleSoft environment 8 Months, 2 Weeks ago
|
|
The first step to become a PeopleSoft admin is to understand the architecture of PIA and have some idea on how it works.
I will add documents in the " Document" Menu and also update this topic whenever more documents are added. I will also provide links to the documents which are good for admins available on the internet. And also I will publish the ones that I have during the course of time.
To get the update of this discussion through email, you can register yourself and subscrible to this topic.
To start with I suggest the Architecture document by University of Bridgeport is a detailed document which explains about the architecture.
Also you can see the " Documents" page to get commands help. I will keep updating the page with more commands, especially for PSADMINs.
|
|
|
|
Logged
|
|
|
Last Edit: 2008/04/22 10:30 By PSADMIN.
|
|
|
|
|
|
|
Re:Most important admin commands, processes, configuration files in PeopleSoft environment 8 Months, 2 Weeks ago
|
|
You are welcome and the cheatsheet is a good document which will be handy for day to day work.
If you happen to have administer HRMS, this document would be some what useful during the tax updates
|
|
|
|
Logged
|
|
|
|
|
|
|
Re:Most important admin commands, processes, configuration files in PeopleSoft environment 8 Months, 2 Weeks ago
|
|
Most of the time, knowing OS command is very useful. Mostly the PS Administrators are also responsible for Databases and to manage both, one should know the basic OS commands. Especially the OS that you are using.
If your OS is Unix, you can try this site. I used to get useful tips when I looked for some commands or sometime foget it.
Also the command list with all flavors is good. Check it out.
|
|
|
|
Logged
|
|
|
Last Edit: 2008/04/22 21:13 By PSADMIN.
|
|
|
|
|
|
|
Re:Most important admin commands, processes, configuration files in PeopleSoft environment 8 Months, 2 Weeks ago
|
|
|
Yes, the database needs to be refreshed. What level and about the Tools data/Security depends on the client request, size of the database and also of the convenience of the administrators and developers.
For example, a company which has more developers working on various projects, they would like to have the security replaced with the current one rather than the copy of production.
For smaller shops one or two developers, they would rather go for refreshing the entire database and change the SID and update the report nodes and keep the security, tools table as copy of production. At the most they might lock all the users other than the ones that are going to use the refreshed environment.
Some clients might just want to refresh certain tables or I have worked with a client who had about 30 developers spread across the globe and they wanted to export the security on the environment which is getting refreshed and refresh the environment with the copy of the production and put back the old security so the developers and QA will have same security as before and also they need not change the password. Most of the production environments may not have a operid for developers.
Besides the security setup, the scheduled processes/jobs and job sets, nodes, etc many not be the same for all the environments, which needs to be updated after the refresh.
|
|
|
|
Logged
|
|
|
Last Edit: 2008/04/25 15:21 By PSADMIN.
|
|
|
|
|