Whether you’re installing an application for the first time, applying a PeopleTools patch, or making another technology change to an environment, you’ll need to test everything out to make sure it’s working. Here are some things I like to test before I turn an environment over to the end-users.
Process Scheduler- Make sure any environment-specific SQC’s exist in the correct SQR directory and have the correct settings for the environment.
- Verify the process scheduler starts with no errors.
- Make sure the process scheduler shows a “Running” status with a current date/time stamp on the Process Servers tab of process monitor.
- Make sure you can run SQR, App Engines, COBOL’s, PSJOBS, Crystals as appropriate for your process scheduler environments. One easy place to run sample processes is PeopleTools > Process Scheduler > Sample Processes. Verify these all run to completion and post to the report repository. Also verify that you can run the jobs to files (preferably to a network location for PSNT process schedulers) and make sure you can run to an e-mail. If you are using the REN server, run a report to WEB and verify a pop-up window opens, shows the run status, and the report loads automatically when it’s complete.
- In the same way, make sure you can run nVision reports (for Financials especially). You can run an nVision report at PeopleTools > Define Report Request. You might want to check with your local nVision expert for which reports and report books would be good to test with and what parameters to enter for them.
PeopleSoft Single Sign OnPeopleSoft Single Sign On allows different environments to trust the sign on of each other, allowing the user to bypass the sign in page when going between applications or when you request a report from the report repository. The easiest way to verify that Single Sign On is working within a single environment is to try to view a report out of the report repository. You can do this by going to Process Montior, click Details on one of the reports, click View Log/Trace, and click on a report. Note: You’ll need the ReportDistAdmin role in order to view other people’s reports. Debug TestsMake sure all of the tests under PeopleTools > Utilities > Debug are working. These include Remote Call tests and Business Interlinks tests. Keep in mind these tests are executed from the application server box, and they won’t necessarily tell you if these tests will be successful on your process schedulers unless your process schedulers run on the same server. Integration BrokerVerify that the local gateway URL returns an expected result.
1. Navigate to PeopleTools > Integration Broker > Configuration > Gateways. Enter LOCAL in the search dialog and click Search. The integration broker gateway should appear. 2. Click the Ping Gateway button, and Verify a good message appears, such as the following:
PeopleSoft Integration Gateway
PeopleSoft Listening Connector
Tools Version : 8.49.09
Status: ACTIVE 3. Click the Load button. Verify the connector information loads with no errors. 4. Navigate to the Integration Broker monitor message tab. The navigation changes from release to release, but in Tools 8.47 and earlier it was PeopleTools > Integration Broker > Monitor > Monitor Message. In PeopleTools 8.48 and later it’s under PeopleTools > Integration Broker > Service Operations Monitor > Monitoring > Asynchronous Services. 5. Click the Node Status tab. 6. Enter the default local node (PSFT_EP for Financials, PSFT_HR for HRMS) in the message node name and click the Ping Node button. 7. Verify Message Text says “Success” in the node information. 8. Repeat for any other nodes you know your environment needs to communicate with. For instance, if you’re logged into HRMS and know it needs to communicate with Financials and Enterprise Learning, also ping the PSFT_EP and PSFT_LM nodes and verify there are no errors. 9. If you are using Tools 8.47 and before, Click the Domain Status tab. If you are using Tools 8.48 and later, go to Service Operations Monitor > Administration > Domain Status. Verify the domain information is correct: Machine name should be the app server machine name, the application server path should be correct for the environment, and Domain Status should be Active. Attachment ServersThe attachment server allows users to upload a file to the PeopleSoft server into either the PeopleSoft database or a directory on your application server. For Financials, here’s how to make sure that functionality works: 1. Navigate to General Ledger > Journals > Import Journals > Spreadsheet Journals
2. Choose a run control ID and click OK
3. Click the Add button to add a file
4. Browse for a spreadsheet file on your local disk and click Upload
5. Click Save
6. Click the View button and verify that you can view the file.
7. Click the Delete button.
8. Click Save. Check E-mail Send Functionality (online)1. Navigate to PeopleTools > Workflow > Defaults & Messages > Workflow/Email Message.
2. Enter your own user ID in the user ID field. Make sure this user ID has your e-mail address defined in operator security.
3. In Subject, enter Test.
4. In Message, enter “Test Message”.
5. Click Save
6. Wait a few minutes, and verify the e-mail message was sent to your workstation. Check E-mail Send Functionality (Batch)1. Navigate to PeopleTools > Process Scheduler> System Process Requests
2. Select a run control ID
3. Click the Run button
4. Verify the server name is the process scheduler server you want to test email functionality on.
5. Check the DDDAUDIT report, Choose Email as the distribution type, and click the Distribute To icon ( )
6. In the Distribute To, select ID Type = User; Distribution ID = your user ID. Make sure this user ID has your e-mail address defined in operator security.
7. Click OK
8. Click OK to run the report.
9. Verify that the process completes successfully and the report output is e-mailed to you. XML Link (PS Financials)Update the following URL for the environment being tested, and paste it into a browser:
http://<servername>:<port>/xmllink/<environment>/Excel_Journal_Import?userid=<USERID>&pwd=<USERPSWD> Verify the output resembles the following:
PeopleSoft General Ledger: Import Journals from Excel Queries- Verify you can run queries on-line using both Query Manager and Query Viewer.
- Test large queries. Sometimes the application server will limit the number of query rows returned, so just make sure the rows either return or the user gets an error like you would expect.
- Be sure you can run queries to an Excel file on-line. Verify numeric, alpha-numeric and dates are formatted like you would expect.
External Uploads
- Verify you can upload a journal using the Journal Upload spreadsheet.
- Verify any ExcelToCI spreadsheet uploads that users run still work.
- Verify the Voucher Upload process still works
- Test any Component Interface applications to make sure they can still connect and retrieve or update data.
Application DesignerThere are things you can check out with application designer. - Verify you can connect using 2-tier (specify your database platform and database name) and 3-tier (Specify Application Server and your app server name) on the sign in page.
- Verify you can open a page definition and print it to a printer.
Comments () |
 |
|
|
|
 |
dev instances and needed a documented test plan. Your is priceless and has no doubt saved me several hours of documentation already. Thanks! 