DDDauditSysaudit Alteraudit

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 3

PeopleSoft - Alter Audit

Labels: PeopleSoft Admin Posted by Sandeep G on Thursday, December 27, 2007 at 11:42 PM DDDAUDIT is an SQR script that compares your production SQL data tables with the PeopleSoft PeopleTools record definitions to identify inconsistencies. SYSAUDIT is an SQR script used to identify orphaned PeopleSoft objects. For example, SYSAUDIT can identify a module of PeopleCode that exists but does not relate to any other objects in the system. SYSAUDIT also identifies other inconsistencies within your database. To verify that the PeopleSoft PeopleTools definitions are synchronized with the underlying SQL data tables in your database, run the PeopleSoft PeopleTools alter record process on all records in your system. This process, called an Alter Audit, compares the data structures of your database tables with the PeopleSoft PeopleTools definitions to identify inconsistencies. The Alter Audit then creates SQL scripts with the data definition language (DDL) changes that are required to synchronize your database with the PeopleSoft PeopleTools definitions. To run Alter Audit: 1. Launch PeopleSoft PeopleTools and sign in to the Target database. 2. From Application Designer, select File, New 3. Select Project, and then click OK. 4. Select Insert, Definitions into Project... 5. Select Records from the Definition Type drop-down list box. 6. Select Table from the Type drop-down list box. 7. Click Insert, and then click Select All. 8. Click Insert, and then click Close. 9. Select File, Save All. 10. Enter a project name of your choice. 11. Click OK. 12. Select Build, Project.. Note. Triggers are always dropped and re-created during the alter process and will always show up in the generated Alter Audit script. You can ignore the generated script for triggers.
Understanding Peoplesoft Sign on: Basic step in Peoplesoft Sign on are: 1. Initial Connection: The application server starts, and uses the Connect ID and User ID specified in its configuration file (PSAPPSRV.CFG) to perform the initial connection to the database.

2. SELECT on security tables: After the Connect ID is verified, the application server performs a SELECT on various PeopleTools security tables, such as PSOPRDEFN, PSACCESSPRFL, and PSSTATUS. From these tables the application server gathers info such as User ID and password, symbolic ID, access ID, and access password. After the application server has the required information, it logs off from this initial connection. 3. Re-Connects with access ID: When the system verifies that the access ID is valid, the application server begins the persistent connection to the database that all PIA and windows three-tier clients use to access the database.
Change Assistant Setup To start with, identify an environment that will act as a PSEMHUB. Configure PSEHMHUB To start with, identify an environment that will act as a PSEMHUB. In case of a single server configuration for PIA, the PSEMHUB is started whenever we start PIA and uses the same http post as the PIA. Lets say if the PIA URL is: http://ws1_ip:9081/site/signon.html, the hubURL will be http://ws1_ip:9081/PSEMHUB/hub (Format of hubURL is: http://[server_name]:[port]/PSEMHub/hub ) To configure PSEMHUB: - Go to below directory (of web server machine) $PS_HOME/webserv/DOMAIN_NAME/applications/peoplesoft/PSEMHUB/envmetadata/config - Edit configuration.properties for hubURL, agentport (must be unique) and windowsdrivestocrawl or unixdrivestocrawl. hubURL=http://ws1_1p:9081/PSEMHUB/hub unixdrivestocrawl=/u02/pt848 or windowsdrivestocrawl=D:\pt848 Configure PSEM Agent To configure PSEM Agent: - Go to $PS_HOME/PSEMAgent/envmetadata/config - Edit configuration.properties for hubURL, agentport (must be unique) and windowsdrivestocrawl or unixdrivestocrawl. Once PSEM Agent is configured, start the PSEM Agents in App Server machine, Process Scheduler Server machine, File Server machine, NT machine where CA is configured: $PS_HOME/PSEMAgent/StartAgent.sh (in Unix) $PS_HOME/PSEMAgent/StartAgent.cmd (in Windows) For the first time, start the PSEMAgent with recrawl command - so that it crawls the drives to identify the environment components (all servers): $ $PS_HOME/PSEMAgent/StartAgent.sh recrawl (in Unix) $PS_HOME/PSEMAgent/StartAgent.cmd recrawl (in Windows) After recrawl is done, start PSEMAgent normally. $ $PS_HOME/PSEMAgent/StartAgent.sh recrawl (in Unix) $PS_HOME/PSEMAgent/StartAgent.cmd recrawl (in Windows)

Before doing so, you may want to modify the StartAgent.sh file in unix using nohup command - so that EM Agent keeps running even if we exit from unix box To modify the StartAgent.sh, open it in vi editor and update the last line as: nohup ../jre/bin/java com.peoplesoft.pt.environmentmanagement.agent.Agent $1 & Save and exit. Execute $./StartAgent.sh Setup Change Assistance Now, that we have done with the configuration of PSEMHUB and PSEM Agent next step would be to setup Change Assistance. Open the Change Assistance, and go to Tools -> Options: - Select Apply Application Update as Change Assistant Mode - Download directory is where we have downloaded the bundle or MP zip files - Staging directory is the one which CA will use as a stage - it will extract zip files from Download directory to Staging Location and will use contents in this directory for processing - Output directory is the one where CA will keep all the output files generated during implementation of a bundle or MP Go to Tools -> Options -> Environment Management Tab: - Server Host: enter the IP address of PSEMHUB machine - Server Port: enter the Port Number at which PSEMHUB is configured - Click Ping to check the connection - Click View to see the Environment Management Hub Summary it shows all the environments name and availability of their server components. Go to Tools -> Scan Configuration: Go to Tools -> validate:

You might also like