PeopleSoft Learning

To make changes in the login page one has to change the signin.html page but all the text used by the .html is inside the text.properties

For miltilanguage instance it would be textXXX.properties

Example: To change the value of the login button from 'sign in' to 'developement' or something else one has to make changes in text.properties, signin.html & other few .html files refers text.properties for these values.

Unable to DrillDown in a nVision Report:

Set EnableDrillDownForFile=1 in the Process Scheduler Configuration File, then bounce & re-configure the process scheduler. This option will allow users to use the drill down option in the nVision report.

SQLNET.EXPIRE_TIME

Purpose

Use parameter SQLNET.EXPIRE_TIME to specify the time interval, in minutes, to send a probe to verify that client/server connections are active. Setting a value greater than 0 ensures that connections are not left open indefinitely, due to an abnormal client termination. If the probe finds a terminated connection, or a connection that is no longer in use, it returns an error, causing the server process to exit. This parameter is primarily intended for the database server, which typically handles multiple connections at any one time.


DEAD CONNECTION DETECTION

DCD is initiated on the server when a connection is established. At this time SQL*Net reads the SQL*Net parameter files and sets a timer to generate an alarm. The timer interval is set by providing a non-zero value in minutes for the SQLNET.EXPIRE_TIME parameter in the sqlnet.ora file. When the timer expires, SQL*Net on the server sends a "probe" packet to the client. (In the case of a database link, the destination of the link constitutes the server side of the connection.) The probe is essentially an empty SQL*Net packet and does not represent any form of SQL*Net level data,but it creates data traffic on the underlying proto .

If the client end of the connection is still active, the probe is discarded, and the timer mechanism is reset. If the client has terminated abnormally, the server will receive an error from the send call issued for the probe, and SQL*Net on the server will signal the operating system to release the connection's resources.

Values for config section - RemoteCall

RCCBL Redirect=0

Enter 0 to disable redirection and enter 1 to enable redirection. Redirection causes the server process to retain intermediate work files used to pass parameter values between the server process and a RemoteCall/COBOL program for debugging purposes.

Note: Redirect should always be 0 except for debugging. Work files are written to the /LOGS directory with ".in" and '.out" extensions.

Source: PeopleBooks

How to disable Workflow Tiggers in Peoplesoft ?

Main Menu > PeopleTools > Workflow > Defaults & Messages > Set Workflow defaults
Uncheck Worklist Active and Email Active

PeopleSoft certification Exam - Dumps

Downloads

PeopleSoft Certificaiton Question Bank

Peoplesoft Certification Exam

Peoplesoft Certification Questions & Answers

Peoplesoft Certification Additional Questions

People Soft 8 Tools Implementation Champion Proficiency Level Assessment

People Tools Certification Questions

Certification Detalis

Exam - I - PeopleTools Developer Certified Expert - 1z0-241
Exam - II - PeopleTools Advanced Developer Certified Expert 1z0-242

Multi-Language - How to Determine if the application has Multi-Language

Log onto the database and run the following select statement in SQL*Plus

select Language_CD, Installed from PSLANGUAGES;

If the 'Installed' field returns a '1' in for the Language_CD, then that language is installed in the application.

PeopleSoft Application and PeopleTools maintenance releases are intended to address defects,
performance enhancements, regulatory changes (such as tax updates), or security issues. In general, feature enhancements are part of new releases which require a product upgrade.


Application fixes and changes are delivered in a variety of means; these include individual postings (Patches), Bundles, Maintenance Packs and Service Packs.

Fixes

Fixes for specific issues with an application may be posted as a standalone fix intended to address that specific issue; these are generally referred to as Patches.

Patches

Patches almost always have pre-requisites that are included in the documentation for that Patch. Patches are created by development using the most recently released bundle, this means they may list that bundle as a prerequisite. There may be other pre-requisites that are also required, all pre-requisites are clearly documented in the notes for the Patch.

Bundles

Bundles are periodic accumulations of fixes resolved in that time period and applied to the application as a group. For most applications, the interval has been about every 6 weeks or 12 weeks for posting these Bundles. When Bundles are applied using Change Assistant, information about the Bundle is recorded in the Maintenance Log table for future reference. Bundles will typically require pre-requisites and occassionally post-requisites. These are documented in the notes for the Bundle. Information about the individual Report ID s associated with a Bundle is available in the supplemental information posted on Customer Connection related to that Bundle.

Maintenance Packs

Maintenance packs are less frequent updates that aggregate Bundles to minimize the number of Bundles that need to be applied. For most applications, maintenance packs are delivered once a quarter for the two most current releases.

Service Packs

Service Packs serve as a vehicle for an even larger aggregation of fixes than Maintenance Packs.
In all cases, the PeopleSoft tool Change Assistant is a valuable tool in identifying dependencies of Patches, Bundles, and Maintenance Packs.

When you want to search for files in all folder expect few selected folders you can use the below command as reference, this will find the files with name *bkp* , *bak* & *old* in all the folders under /psoft/pt848, but will ignore the directories like psreports & log_output

find /psoft/pt848 -path '*psreports*' -prune -o -path '*log_output*' -prune -o -type f \( -iname "*bkp*" -o -iname "*bak*" -o -iname "*old*" \) -exec ls -lh {} \;

Happy Sharing
Sandeep G

PID -- Process Id
The tasks unique process ID, which periodically wraps, though never restarting at zero.

USER -- User Name
The effective user name of the tasks owner.

PR -- Priority
The priority of the task.

NI -- Nice value
The nice value of the task. A negative nice value means higher priority, whereas a positive nice value means lower priority. Zero in this field simply means priority will not be adjusted in determining a tasks dispatch-ability.

VIRT -- Virtual Image (kb)
The total amount of virtual memory used by the task. It includes all code, data and shared libraries plus pages that have been swapped out.

RES -- Resident size (kb)
The non-swapped physical memory a task has used.

SHR -- Shared Mem size (kb)
The amount of shared memory used by a task. It simply reflects memory that could be potentially shared with other processes.

S -- Process Status
The status of the task which can be one of:
D = uninterruptible sleep
R = running
S = sleeping
T = traced or stopped
Z = zombie

%CPU -- CPU usage
The tasks share of the elapsed CPU time since the last screen update, expressed as a percentage of total CPU time. In a true SMP environment, if Irix mode is Off, top will operate in ´Solaris mode where a tasks cpu usage will be divided by the total number of CPUs. You toggle Irix/Solaris modes with the I interactive command.

%MEM -- Memory usage (RES)
A tasks currently used share of available physical memory.

TIME+ -- CPU Time, hundredths
The same as TIME, but reflecting more granularity through hundredths of a second.

Command -- Command line or Program name
Display the command line used to start a task or the name of the associated program.

Note: Of course you can get more info on this from 'man top'

Peolesoft Interview Questions

Download links

Error: SQR runs successfully but the Process Status is showing Error in the PIA Process Monitor Page…

Issue: The two procedures required to be included in that particular SQR was missed by the developer.

Solution: Called two procedures (stdapi-init, stdapi-term) in the SQR and included the Stdapi.sqc in the bottom of the program…

Note:

Step we have to fallow to run the SQR program from the Peoplesoft environment (Process Scheduler) - Making the SQR program API aware by calling two procedures (stdapi-init, stdapi-term) from the Begin-program section and including the Stdapi.sqc in the bottom of the program.

stdapi.sqc: It contains the application program interface procedures. These procedures allow the SQR program to communicate with the Process Monitor and Report Manager inside the PeopleSoft environment.

Thanks

Sandeep G