PeopleSoft Learning

Sharing my simple script created to monitor the status of the PRCS scheduler services.

1. PRCS-List.txt is a file referred by my logic which contains PRCS Domain names which we have to monitor…

[Sandeep]:/dba/scripts>cat PRCS-List.txt

SANDEEP

SANSNEW

[Sandeep]:/dba/scripts>

Script starts here….

ScriptPath="/dba/scripts”

rm $ScriptPath/PRCS-Report.txt

cat $ScriptPath/PRCS-List.txt while read line

do

psadmin -p status -d $line > $ScriptPath/PRCS-TMP.txt

#The below statement “egrep” checks for the services within that domain, in this case I have checked if that domain has 'BBLPSPRCSRVPSDSTSRV' running… you can change this according to version and based on requirement … When you change this list you have to change the count of process you are monitoring in the if loop “if [ ${status} -ne 3 ]” in the below line accordingly … in my case since I am monitoring only 'BBLPSPRCSRVPSDSTSRV' hence I have mentioned 3 in the if loop “if [ ${status} -ne 3 ]”

status=`egrep 'BBLPSPRCSRVPSDSTSRV' $ScriptPath/PRCS-TMP.txt wc -l`

if [ ${status} -ne 3 ]

then

echo "" >> $ScriptPath/PRCS-Report.txt

echo $line >> $ScriptPath/PRCS-Report.txt

`echo "Process Scheduler is DOWN" >> $ScriptPath/PRCS-Report.txt`

echo "" >> $ScriptPath/PRCS-Report.txt

echo "++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++" >> $ScriptPath/PRCS-Report.txt

else

#echo $status >> $ScriptPath/PRCS-Report.txt

echo "" >> $ScriptPath/PRCS-Report.txt

echo $line >> $ScriptPath/PRCS-Report.txt

`echo "Up & Running" >> $ScriptPath/PRCS-Report.txt`

echo "" >> $ScriptPath/PRCS-Report.txt

echo "++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++" >> $ScriptPath/PRCS-Report.txt

fi

done

Script Output - PRCS-Report.txt will look as below; you can e-mail this to your ID from the UNIX Server….

SANDEEP

Up & Running

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

SANSNEW

Process Scheduler is DOWN

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

TraceOptions

This section enables you to specify the tracing options that you can enable on the application server to track the SQL and PeopleCode of the domains. You can also set all of the trace parameters from the PeopleSoft sign-in page.

TraceSQL

Enter the logging level for SQL tracing for all clients. Traces are written to <PS_HOME>/appserv/<domain>/LOGS/<Domain User ID>_<svrname>.tracesql. Enter 0 to disable tracing; enter 7 to enable a modest tracing level for debugging. For other levels of tracing, set this option to a value that equals the sum of the needed options. For example, to trace only SQL, enter 1; to trace SQL statements and connect statements enter 7 (1+ 2 + 4 = 7). Tracing can consume large amounts of disk space over time, so be sure to reset this option to 0 when you finish troubleshooting.

TraceSQLMask

Enter the logging level ceiling for SQL tracing for individual clients. Traces are written to <PS_HOME>/appserv/<domain>/LOGS/<Client User ID>_<svrname>.tracesql. Clients must specify the necessary SQL tracing level by using the PeopleSoft Configuration Manager on the Trace tab. To prevent clients from turning on the application server trace and consuming resources, the application server uses TraceSQLMask as an administrative control facility.

If a client transmits a request to trace SQL, the application server compares the value that is transmitted to the TraceSQLMask value. If the client value is less than or equal to the TraceSQLMask value, the application server enables the trace. However, if the client value is greater, the application server enables the trace up to the TraceSQLMask value. Trace files are written on the application server; no trace shows up on the client workstation. Trace values are set in the PSAPPSRV.CFG file. Output files are written to $PS_HOME/appserver/winx86/<domain>/logs.

TracePC

Enter a level for PeopleCode tracing for activity that is generated by all clients on a domain. Eligible values are defined in the configuration file. TracePC values are displayed in the PeopleSoft Configuration Manager on the Trace tab. You can find the results in <PS_HOME>/appserv/<domain>/LOGS/<domain>.log.

TracePCMask

Enter which PeopleCode trace options that are requested by client machines will be written to the trace file. You can find the results in <PS_HOME>/appserv/<domain>/LOGS/<ClientMachine>.<domain>.log.

The "standard" rollback plan has plenty of issues. Simply restoring the file backup will not revert the system to pre-migration state.

These are the steps to do a proper backup/rollback, it's not detailed but it should give you the general idea on what's involved and how to do it correctly.

Backup Steps:

1. Copy Project Definition Only to Target DB (e.g. Prod)
2. Open Project Definition in Target DB, and set Action for Project = COPY
3. Copy the Project Definition to a Project Backup file.
4. Run Data Mover or Oracle export to backup all the data in all the tables including any Message Catalog Entries and User Roles in the project.
5. At this point there should be 2 files -- the Project Backup and the Data Backup

Rollback Steps:

1. Open the project definition from the Source DB (e.g. QA)
2. Set Action for Project = DELETE (This will ensure all objects that moved are deleted)
3. Move the Project from the Source DB to the Target DB to perform the delete
4. Copy the Project Backup from file to the Target DB to restore the objects.
5. Alter Tables/Rebuild Views.
6. Run Data Mover or Oracle import to restore all Data and any Message Catalog Entries and User Roles from the Data Backup

IPC resources are operating system resources, such as message queues, shared memory, and semaphores. When an application server shuts down properly all IPC resources used are removed from the system. In some cases, however, an application server may fail to shut down properly and stray IPC resources may remain on the system. When this happens, it may not be possible to reboot the application server.

The command to remove IPC resources, tmipcrm, resides in TUXDIR/bin. This command reads the binary configuration file (TUXCONFIG), and attaches to the bulletin board using the information in this file.

To list all IPC resources

"tmipcrm -n [TUXCONFIG]" (Ex. tmipcrm -n D:\PS\appserv\PSDEMO\PSTUXCFG)

To Clean/remove all IPC resources used by the BEA Tuxedo system

Application Server Command
tmipcrm -y /apps/psoft/pt844/appserv/PSDEMO/PSTUXCFG

Process Scheduler Command
tmipcrm -y /apps/psoft/pt844/appserv/prcs/PSDEMO/PSTUXCFG

This will remove the IPC resources associated that particular domain…

The ERP Connectors are used with the Integration Broker product. If you do not plan to utilize the Integration Broker portion of PeopleTools, reply NO to the prompt. If you do plan to use Integration Broker, reply YES to the prompt. If you reply NO to the prompt but then later decide to use Integration Broker you will have to go back and reinstall PeopleTools. The YES will cause files to be unloaded to your PsHome for use with the Integration Broker product.

Issue: While running the database Setup step during installation we received the error shown in the screen shot…

Solution:

Add this parameter in the Oracle DB parameter file & restart the DB.

NLS_LENGTH_SEMANTICS=CHAR

How to grant access for a User to perform object migration

To create user who can perform object migration from one environment to another environment, without having write access to the Application Designer objects like record, field, Application Engine, PepleCode etc.

Solution:

Login to PIA:

Go to Home > People Tools > Maintain Security > Use > Permission Lists open the permission list the user has.  Then go to People Tools tab, tick Application Designer Access.  You may set different objects permissions to read only if you click the links for Definition Permissions, Tools Permissions, and Miscellaneous Permissions.
You should have "full access" to project.

You can set Build script only or more in Build / Data Admin of Tools permission. Once the user has this permission list, the user should be able to migrate the project and build the project only.

With Peoplesoft Internet Architecture don't have local cache files on work station. All the cache files are on your Web Server and Application Server.

Web Server CACHE:

If you are using Web Logic as web server: The cache files are under Web Logic/My Server/Public_html/"PIA Instance name"/Cache.
If you are using Apache as web server: The cache files are under Apache Group/Apache/psftdocs/"PIA Instance name"/Cache.

App Server CACHE:

You also need to cache on App server domain which can even corrupt some times.
App server cache is located under your App server Box's PS_HOME/Appserv/"Domain Name"/Cache.

Workstation:

The only cache files on workstation when you use Peoplesoft Internet Architecture are Browser cache and cookies. You can delete browser cache from Internet Options->delete Temporary internet files.
Cookie, it downloads for the first time you signin for each PIA instance and every user you signed in from that work station's Browser. You can check these from Browser->tools->internet options->General Tab->settings Button->View files. You will see different files by name with cookie. The only way to delete them is manually each cookie or all the contents from this directory. Once you delete cookie, you get a new cookie created on browser when you sign back-in

To Change the Access ID password, possible methods are listed below:

There are ONLY 3 ways to do this. These options MUST be done in 2 tier and your application servers, Process Schedulers, and Web Servers MUST BE DOWN and ALL users need to be logged off if possible.

METHOD # 1 - (Preferred Method) Log into Data Mover as the Access ID (Bootstrap mode).

Then run this command:

CHANGE_ACCESS_PASSWORD sa1 (This is your symbolic ID) cloud123 (This is the new password for the Access ID);

And hit the Green traffic light.

NOTE - This method does NOT work in PT 8.14 or 8.15, but is now fixed in PT 8.16 (T-JPELAY-AU4QW) so use method 2 or method 3. You MUST also make sure that the password for the Access ID has successfully been changed at the Database level because prior to PT 8.17 this method would not change the database level password. To do this go through your SQL tool (SQL Plus, Query Analyzer) and make the change in the database users table.

METHOD # 2 - (Second best method) You need to change the Access ID Password at database level then log into Data Mover in bootstrap mode and run:

update PSACCESSPRFL set ACCESSID = 'what your Access ID is' , ACCESSPSWD = 'your New Access Password' , ENCRYPTED = 0, where SYMBOLICID = 'whatever the SYMBOLICID is';

Then run

ENCRYPT_PASSWORD *;

Note: If you have more than 45,000 rows in the PSOPRDEFN table then you may not be able to run the ENCRYPT_PASSWORD *; command in Data Mover. In that case just logon as a valid user in 2 tier and that will encrypt the Access ID in the PSACCESSPRFL table.

This will synch up the PSACCESSPRFL table with the same password stored at the database level for your Access ID.

METHOD # 3 - (Last and most discouraged method) Go into Application Designer / Tools / Miscellaneous Objects / Access Profiles.

Highlight the Symbolic ID and push the Edit button, enter the old password, new password, and confirm new password.

If you change it in Application Designer it does not change at the database level. This is because we do not GRANT to the database in PT 8. You MUST also make sure that the password for the Access ID has successfully been changed at the DB level. To do this go through your SQL tool (SQL Plus, Query Analyzer) and make the change in the database users table.

Creating HTML output from SQR

To use the HTML procedures listed below, your program must reference the HTML procedures.

Issue the following two commands at the start of your program:

#include html.inc

do html_on

The file html.inc is located in the SAMPLE (or SAMPLEW) directory.  Use the command-line flag -I to indicate this location.

There are 6 types of HTML procedure that can be used to easily create HTML o/p files.

General Purpose Procedures

Heading Procedures

Highlighting Procedures

Hypertext Link Procedures

List Procedures

Table Procedures

Eg:-        

1) Html_br

Produces the specified number of line breaks in a paragraph using the HTML<BR> tag.

This causes the paragraph to be continued onto the next line.

Syntax: html_br(number count, string attributes)

count    = the number of HTML <BR> tags that are inserted.

            Attributes          =          the HTML attributes that are incorporated inside the HTML <BR> tag.

Example: Producing a line break:

            Print 'Here is some text' ()

            Do html_br (3,'')

            Print 'Here is some three lines down' ()

2) Inserts an image using the HTML <IMG> tag. This can also be done using the command PRINT-IMAGE;

However, the procedure html_img provides the ability to specify the full set of available HTML attributes.

Syntax:             html_img (string attributes)

Attributes          =          the HTML attributes that are incorporated inside the HTML <IMG> tag.

Some common attributes:

Src       =          URL of the image to be inserted (Ex:  src=/images/abc.gif)

Height =            height of the image in pixels (Ex:  height=200)

Width   =           width of the image in pixels (Ex:  width=400)

Example:          Producing an image:

Do html_img('src="/images/stop.gif"')

-Posted by

Ganesh A.M

http://www.roughsea.com/vids/SQL_Best_Practices.html

-Ganesh A.M

Field default event Peoplecode in Peoplesoft

The People code in this event is used to initialize the default values for the fields in the component.

What happens when the field has default value defined in the record field properties and has People code assign the different value in the Field default people?

The Field default event People code will only fired when there is not default value defined for that field in the record field properties, so the value assigned in the record field properties will be initialized to that field.

-Ganesh A.M

Common Query Access Issues

a) User cannot see a table they wish to query from in query manage

   User does not have access to the table via one of their Access Group. Double-Click that they have the Proper Access group on one of their Permission lists an ad the table to an Access group if necessary.

b) A user cannot see a public query from search screen in either query manager or query viewer.

     Once you have determined that the query does in fact exist, and I s indeed a public query, then the user probably does not have access to all the tables being used in the query. If a user does not have access to all the tables involved in a query, the search screen itself will filter out the query, so that it does not even appear in the list. Double-Check that they have the proper Access group on one of their permission lists and add the table to an Access group if necessary.

Posted by

-Ganesh A.M

Row Level Security in Peoplesoft HRMS

The Default department security is name DEPT_SECURITY and the SetID is the share, although you may choose to create one to operate with a different Setid, depending on your environment.

Root level on this tree represents your company or organization. Below that you are adding departments in a hierarchical manner until you have built on organizational char of your company’s department structure.

When you click the link on one of department levels to either insert a child or a sibling node, you will be allowed to either choose an existing department that has been created or to create a new department on the fly by clicking Add.

Tie date Permission lists to Your Trees

Define Business Rules - > Administer HR systems -> Use -> Maintain Row level Security

1)       Select a Permission list – It needs to created in the maintain security menu.

2)       Peoplesoft standard is to generally preface them with DP

3)       In the Data security profile page, you need to add the Departments that this permission list will have access to.

4)       You need to provide SetID for the Department Security Tree you are using and then enter the DeptID for the node you are choosing.

5)       Department Security Tree is hierarchical, that by adding an access to a department, you are automatically granting access to all the departments below that node as well.

If you need to exclude the data from a particular ‘Sub-Department’ you will have need to add that department separately to this list, and choose ‘No Access’ as the Acess code instead of the default of ‘Read/Write’.

Change the security Basis for the System

The final step to implement Row level security in HR is to change all the search views controlling which data is accessed on various pages. Luckily you don’t have to change it manually change each one, as Peoplesoft has delivered a process that takes care of it all for you. Please note that you only run this Process when turning on Department security System-Wide, Or when removing it from the system.

Define Business Rules -> Define General options - > Process - > Change Row Security Basis.

You need to choose option for Department security, to turn Department security on, or the Option of ‘None’, to turn Department security off.

-Posted by

Ganesh A.M

To enable change control in the Application Designer, navigate to the link [shown in the picture] in the application designer and check the check box appropriately.

• Use change control locking

• Use change control history

Exception Handling in Peoplesoft

Exception handling is the processing you initiate when an exception occurs. You can handle errors in PeopleCode using the Catch statement. The places in your code where you want exceptions handled must be enclosed by the Try and End-Try statements.

The Exception class encapsulates exceptional runtime conditions. It can be used with most PeopleCode programs.

The process of error handling can be broken down as follows:

• An error occurs (either a hardware or software error).

• The error is detected and an exception is thrown (either by the system or by your program).

• Your exception handler provides the response.

You can create exceptions in 2 ways

1) Creating an Exception base class that encapsulates the built-in function call and handles its function parameters consistently. This is the preferred way.

2) Calling the built-in function CreateException.

Application code often continues some form of processing even in the event of an exception; you should not assume that the script all processing if an exception occurs.

The error message that PeopleTools displays might not be appropriate for end-users because of its technical information.

The Exception class does not work with any of the PeopleSoft APIs, that is, the classes whose objects are declared as type ApiObject. This includes the Tree classes, the Query classes, Search classes, and so on.

try

Protected StatementList

catch QualifiedID &Id

StatementList

End-try;

Example 1:-

Import ExceptionPackage:*; 

try               /* Code to manipulate &MyArray here */

 &MyArray = GetArrayData(&Param1, &Param2, &Param3); 

catch ExceptionNull &Ex1

 If &Ex1.MessageSetNumber = 2 and &Ex1.MessageNumber = 236 Then 

   /* this is the message set and message number for &MyArray being Null */ 

   /* do data error handling */

   End-if;

End-try;

Example 2:-

Local Exception &ex;  

Function t1(&i As integer) Returns number 

   Local number &res = &i / 0;     

End-Function; 

Function t2 

   throw CreateException (2, 160, "'%1' doesn't support property or method '%2'", "SomeClass", "SomeMethod"); 

End-Function; 

/* this will cause a divide by 0 leading to an exception. This code will never be caught since t1(2) will resume execution in the catch block below. It is here to show how an exception can be thrown directly bythe Peoplecode itself. */

try 

  t2 ();   

Local number &res = t1 (2); 

Catch Exception &caught 

   MessageBox (0, "", 0, 0, "Caught exception: " | &caught.ToString()); 

end-try;

Posted by

Ganesh