While running DBTSFIX.sqr, we faced this error -
SQR 1500: (SQR 1500) Array element out of range (32767) for array ‘a_dbts_list’ on line 125.

We tweaked the sqr as below -
Locate the create-array name=a_DBTS_list statement in sqr.
Update the size of the array to 131070 (double the delivered size of 65535).

This help us run the sqr successfully. Oracle validated the fix later.
I hope this will help folks who are upgrading to Tools 8.51.

To setup verity in such environment -

• We have to create a shared location which is accessible by all servers.This will be the location where indexes will be created and application server will search for them.
• We have to make following changes in application server configuration file -

                     Modify the section “[Search Indexes]” with values -

                     RSFSRA =//shared_location

                     RSFSRB = //shared_location

• We can do the same for specific indexes ( like Resumes in Candidate gateway).
• Make the above changes in all other application server( different machine) configuration files.
• Make the above change in Process Scheduler configuration file too.
• Clear cache and Restart app/web and process scheduler.

This will help you setup verity in load-balancing environment.

Application server was on a windows 2003 server.

To get an email , first of all we need to setup SMTP  in psappsrv.cfg. Then we will require any kind of third party tool like bmail or sendmail. I have used sendmail.

I have written a bat file which runs infinitely , and gather application server status after every 1 minute and take this output in a text file . Whenever application server is up , it will have BBL.exe process running . Search for ‘BBL.exe’ in text file and if found do nothing , delete the text file and continue the infinite loop.

If not found , go to send mail procedure , which will send emails to an individual or a group , and will keep mailing at fixed interval until application server is up.

Recently I was implementing forgotten password functionality in PeopleSoft. Earlier it was taken care by Portal. But now customer is decomissioning Portal system they want to implement this functionality on Finance homepage.

The  first step for this was to create a new site and make it bypass signon enabled.

Even for a single server domain , multiple sites can be create. The http port will be same. Once the site is created , make following changes to configuration.properties file and bounce the webserver.

byPassSignOn = True

defaultUserId = <UserId>

defautltPWD = <UserPwd>

Also make public access enabled in Web Profile for the user id given in configuration.properties file.

After that change the PIA link from http://<myserver>/psp/<sitename>/?cmd=login  to  http://<myserver>/psp/<sitename>/?cmd=start.

This change makes webserver to check for bypass signon , and thus didn’t ask for authentication.

Once this is set you can create an userid with appropriate permissions ( which will only access forgotten password component ) and give that as a direct link on the signin.html page.

Now I am your partner.

The easiest thing I can write at this time is the project I am working now. We are implementing benefit system for one of our customer in Singapore. Now if you have worked in past with North American customers then need to remember that systems here is far more simplified. But for developer it becomes more difficult as we are actually developing a bolt-on. We found PeopleSoft’s Base Benefits and Ben Admin systems far complicated then the need of the customer.

Like employers around the world companies here in Singapore provide similar benefits related to medical & dental insurance, reimbursement of health screening, hospitalization & surgical expenses. There are also other benefits like leave and vacation which are managed in PeopleSoft’s Absence system. Traditionally and in NA we used to calculated leave and vacation entitlement in Benefit system as rules were highly simple. Here rules are not very complicated but types of leaves are too many to manager in Benefit system. Hence Absence Management is used. It provided great rules processing and delivered integration with Global Payroll system.

Back to benefits. Much of what I am going write here is about my client, because this is my first and only project related Benefits in this region. We have primarily Medical, Dental, Health Screening, Hospitalization and Surgical, and Travel Insurance benefits. Apart from there are many allowances and fringe benefits but they are outside the scope as they are managed in Payroll system.

Medical benefits include cashless service at panel clinics, doctors, polyclinics (govt hospitals) and private hospitals. It can be reimbursement if patient visit doctor or clinic not on panel of the employer or insurance company. This benefit is applicable to General Practitioner or Specialist. Specialist claims are subject to letter from GP. All the reimbursements are subject to 10% co-payment by employees. The monetary value of the provided benefit is not very exciting and it has too many rules on policy document. Fortunately customer did not expect us to implement all of them. But that is Asia. Lack of trust.

Dental claims are subject to reimbursement of S$ 150 to S$ 250. Very simple. Not much of the rules.

Health Screening reimbursements are provided to employees over the age of 40. Till 45 you get 1 health check paid by company in two years. After 45 you get same benefit every year. This is primarily for management and staff above that grade/band.

Travel Insurance is for all staff members who travel for company business. They are eligible to standard travel insurance that is fully outsourced.

Hospitalization and Surgical claims can be made by all employees based up on their eligibility. Eligibility varies in the form for total amount, type of hospitals, beds and services selected.

Unlike NA, here employee do not contribute any amount towards premium for medical and dental insurance.

This was in nutshell. There are different kind of eligibility rules and automatic processing which we have developed. Consider this as initial draft and starting point. Buzz if you have any questions. That will make this post more interesting and complete.

Thank you Neil for making me a partner. And this post good or bad is dedicated to you. Consider this as new year gift.

1) Add SEGMENT SPACE MANAGEMENT AUTO clause
2) Change the EXTENT MANAGEMENT from LOCAL AUTOALLOCATE to LOCAL UNIFORM nnnK or nnnM

e.g.

OLD:

CREATE TABLESPACE PSINDEX DATAFILE ‘/u04/oradata/<SID>/psindex.dbf’ SIZE 160M
EXTENT MANAGEMENT LOCAL AUTOALLOCATE
/

NEW:

CREATE TABLESPACE PSINDEX DATAFILE ‘/u04/oradata/<SID>/psindex.dbf’ SIZE 2500M
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M
SEGMENT SPACE MANAGEMENT AUTO
/

The addition of the following clause to the tablespace script was the performance enhancement  proposed.

SEGMENT SPACE MANAGEMENT AUTO

The change that impacts the footprint size was the storage allocation change from:

EXTENT MANAGEMENT LOCAL AUTOALLOCATE     (This was the old way, it rendered a smaller DB footprint)

to

EXTENT MANAGEMENT LOCAL UNIFORM nnnk

While this is more efficient,  this clause has the negative impact of causing the DB’s to have a bigger storage fooprint.

By using the combination below the Oacle DB’s result in a smaller storage footprint.

EXTENT MANAGEMENT LOCAL AUTOALLOCATE
SEGMENT SPACE MANAGEMENT AUTO

Starting with 8.48 Tools, the LOCAL UNIFORM option is being delivered as the default option for the Create TableSpace syntax. This brings better space management on future inserts, but also will dramatically increases the initial database footprint.  It is possible to revert to the AUTO ALLOCATE option,  which will minimize the initial footprint.

One possible workaround in one situation for a demo FSCM 9 database, was to reduce extent size for the PSINDEX tablespace. Instead of using the default extent size of 1MB, a reduced size of 512 KB is used.

Oracle has come up with updates which will bring these modifications , or if you download newer version of tools you will get the modifies scripts.

In Metalink 3 click on the Product Certifications tab.

In the Certifications menu (immediately below the tabs but above the Search area) click on Product Roadmap.

For Calendar Year, choose All Years

For Calendar Quarter, choose All Quarters

For Product Line, choose PeopleSoft Enterprise

Click on Search.

In the Results, you can click on the Product Family column title to sort by   Product Family.

Click on the link for your Product Release

Click on the triangle beside Technology to open up the Technology Release which is the minimum supported People Tools version.

This version is for installs only, not for upgrades. The minimum version does not include the Required for Installation People Tools patch.

For upgraded environments please refer to your Upgrade Homepage for your upgrade path.

For the maximum version of People Tools:

While PeopleSoft has a minimum People Tools version required for each application and version, there is no upper limit for applications that are 8.40 or greater.

So you can safely upgrade your People Tools without needing to upgrade your application.

But Enterprise Portal application is very closely tied to People Tools. Certain versions of Enterprise Portal require specific bundle levels for specific People Tools versions.

You should view Product Certification pages on Metalink 3 to see if your database, operating system and third party applications are supported on the newer version of People Tools

Open Configuration Manager -> Profile ->Edit.

Select Connection Type as Application Server.

Machine Name or IP Address should be your machine IP address on which application server domain resides.

Port Number should be WSL port number.

 Turn on Debugger Service. Bring the following changes in your PSAPPSRV.CFG file

 Psappsrv.cfg:

..[People Code Debugger]

;————————————————————————-

PSDBGSRV Listener Port=15000

.

..

[PSAPPSRV]

;=========================================================================

; Settings for PSAPPSRV

;=========================================================================

;————————————————————————-

; UBBGEN settings

Min Instances=2 Give >= 2

Max Instances=2

Service Timeout=0  Give >= 2

 ————————————————————

Go to PSADMIN -> Quick Configuration. Check whether the PC Debugger feature is enabled or not. Make it yes, and start the application server domain.

Open Configuration Manager -> Trace

In People Code Debugger Section, Local PSDBGSRV Listener Port number should be the same as provided in PSAPPSRV.CFG.

• Create a text file including all the projects that need to be backed up.
• Create the batch file as below-

set pside=e:\PT849\bin\client\winx86\pside.exe
set folder=%date:~10,4%_%date:~4,2%_%date:~7,2%
set export_path=E:\projectexports\%folder%\
set dbtype=MICROSFT
set user=VP1
set pwd=VP1
set srcdb=FNDMO

FOR /F %%a IN (project_list.txt) DO %pside% -HIDE -PJTF %%a -FP %export_path% -CT %dbtype% -CO %user% -CP %pwd% -CD %srcdb% -QUIET -AF 0 -DDL 1 -PPL 0 -CFD 0 -CFF 0 -LF %export_path%%%a.log

This batch file will create a subfolder inside E:\projectexports folder like (2009-04-06) and do a file copy of all the projects listed in project_list.txt.

You need to update this text file daily and schedule the batch file to  run on daily basis.