It seems that PeopleSoft is really becoming object oriented – now it has it’s own automated unit testing tool, like JUnit – this one is called PSUnit. I hope this one is as good as it sounds. Check out the Wiki article below
Introducing PSUnit – Oracle Wiki
You can download the actual project file here:
http://blogs.oracle.com/peopletools/2009/03/psunit_unit_test_framework_for.html
Take a look at this great post by Peter Slager about upcoming PeopleTools release
And here you can find the latest about PeopleTools 8.50 from Oracle – just an overview of things to come:
Release Value Propositions available
By matthew.haavisto on May 14, 2009 1:58 PM
Two new release value propositions are now available: one covers PeopleTools 8.50, another covers Enterprise Portal 9.1. Both documents provide an overview of the value proposition for the enhancements that are planned for PeopleTools 8.50 and Enterprise Portal 9,1. Both are intended to help you assess the business benefits of these products and to plan your information technology (IT) projects and investments.
And if you like pictures – then the older, but still valid presentation from last year’s OpenWorld would still do a goo job:
By jeff.robbins on September 24, 2008 5:26 AM
During Part 2 of the PeopleTools Roadmap presentation at OpenWorld, I promised to post the presentations and demo viewlets we used. The presentations are in PDF file and I’ll upload the viewlets later today.
Here is Part 1: Download file
Here is Part 2: Download file
Enjoy!
PeopleTools Roadmap Presentation at OpenWorld on Tuesday, Sep 23 (PeopleSoft Technology Blog)
Tags: PeopleTools, PeopleSoft
As many PeopleSoft developers and managers I have suffered through my share of nVision Tuning efforts and until very recent we could not get our reports to run under 4 hours, until the recent change…
In any case here are a few points from my experience:
We experienced an almost almost 5 fold increase in performance when we did a PS_LEDGER reorg with PSCLEDGER index option as follows:
1:
2: db2 "reorg table PSFSSYS.PS_LEDGER index PSFSSYS.PSCLEDGER allow read access indexscan"
3: db2 "RUNSTATS ON TABLE PSFSSYS.PS_LEDGER FOR INDEX PSFSSYS.PSCLEDGER"
4: db2 "reorgchk current statistics on table PSFSSYS.PS_LEDGER"
Also it is great to cleanup treeselectors, to make sure that static selectors did not get out of sync with trees, this can be done on a regular basis, see a sample script below. Please note that the number in the end of the treeselector name xx – corresponds to the chartfield length:
1:
2: -- Delete TreeSelectors
3: Delete from PSFSSYS.PSTREESELECT05;
4: Delete from PSFSSYS.PSTREESELECT06;
5: Delete from PSFSSYS.PSTREESELECT10;
6:
7: -- Delete Tree Control table for the respective selectors above
8: delete from PSFSSYS.pstreeselctl
9: where length in (5,6,10);
For details about PeopleSoft nVision architecture and structure please make sure to read the Red Paper by clicking below
Tags: PeopleSoft nVisoin
After searching the Web, I have found that there is not enough documentation about IMAGE-SIZE of the PRINT-IMAGE command, or I have not done the search right ;-). Either way here it goes in plain English:
Excerpt from the Book:
1: PRINT-IMAGE
2: Syntax
3: PRINT-IMAGE[image_name]position
4: [TYPE={image_type_lit|_var|_col}]
5: [IMAGE-SIZE=(width_num_lit|_var|_col,height_num_lit
6: [SOURCE={file_name_txt_lit|_var|_col}]
IMAGE-SIZE – Specifies the width and height of the image. The width (width_num_lit) is specified in the font point-size that you have specified in the print command or ALTER-PRINTER. So putting:
alter-printer point-size=14 font=4
would affect your image size. Height (height_num_lit) – is specified in the line height. So changing
1: DECLARE-LAYOUT
2: [CHAR-WIDTH=char_width_num_lit[uom]]
3: [LINE-HEIGHT=line_height_num_lit[uom]]
4: END-DECLARE
5: Would have an effect on the image width and height.
Enjoy!
Tags: PeopleSoft SQR
I would like to briefly describe some of the PeopleSoft debugging techniques that I have used and found invaluable during development batch and online programs.
SQR Debugging
| Flag | Description |
| -S | Choose Append Option on Parameter List of Process Definition. All of your SQL statements – simple and clear + execution counts |
| –debug(flag) | Choose Append Option on Parameter List of Process Definition. Put the following statements in your code
#debug(flag) show this will allow you to display definitions in your log. What is most useful this allows you to specify different levels of tracing using the flag – which can be letters A-Z. Specifying –debug(A-Z) on process definition it allows you to selectively display your debug statements. |
COBOL Debugging
| Flag | Description |
|
Choose Override Option on Parameter List of Process Definition. Copy and paste Flags and run your process normally. You will see the trace file in the Process Monitor |
App Engine Debugging
| Flag | Description |
| -TRACE 131 | Choose Append Option on Parameter List of Process Definition.
Required to start the app engine trace. Does not display much more than message log |
| -TRACE 131
-TOOLSTRACEPC 2048 |
Choose Append Option on Parameter List of Process Definition.
Adding TOOLSTRACEPC with a number causes detailed PeopleCode code trace – be careful those can get very large and significantly impact performance. |
| -TRACE 131
-TOOLSTRACESQL 31 |
Choose Append Option on Parameter List of Process Definition.
Adding TOOLSTRACESQL with a number causes detailed SQL trace. This option should always be used when tracing – app engine are all about SQL. |
App engine can also be debugged on the client. In order to do this you need to configure trace setting in the configuration manager:
Open App Engine program in the Application Designer, press the Run Program icon and enter the Run Control ID and Process Instance Number (You should have an existing process instance and run control id defined online). Click ‘OK’ to run the App Engine process in two-tier mode.
If you would like to read about debugging in more details here is an excellent overview presentation by Kai Markowitz from CSU:
http://www.scribd.com/doc/15756180/Tracing-Debugging-in-People-Tools-84x-CMS411
Oracle PeopleTools Blog
Oracle PeopleTools Blog
Recent Comments