This is Taken from PeopleBooks – PeopleTools 8.49.

TheWebLogic Server console can display a list of established HTTP sessions for that instance of the WebLogic Server. Session Monitoring is automatically enabled for WebLogic. These instructions describe how monitor the single server configuration of PIA. When in production, note that a multi server configuration would be used to perform these steps to the server instance that you intend to monitor, such as PIA1 or PIA2, or both.

1. Start the PIA server.Start the PIA server either using startPIA.cmd(.sh) or, if installed as a Windows service, NET START peoplesoft-PIA.
2. Log on to PeopleSoftLog on to your PeopleSoft application. If possible, log on from a couple different workstations using different PeopleSoft IDs. For the purpose of this test, do not log off.
3. Log on to the WebLogic Server Administrative Console.In a new browser, access the WebLogic Server console at http://weblogichost:port/console and specify the WebLogic administrative ID you specified during the PIA installation. The default ID and password are system/password, respectively.
4. Monitor established HTTP sessions for the PORTAL web application.On the left, use the following navigation to view the list of established HTTP sessions for the PORTAL web application:
   1. Click Deployments, and view the deployment list in the right hand window.
   2. Click PeopleSoft.
   3. Select the Control tab.
   4. Select the PORTAL application module, where the context root of the module is ‘/’.
   5. Select the Monitoring tab.
   6. Select the Sessions tab.

Note. You can customize the list of fields that you want to monitor using the Customize this table link.

http://www.peoplesoftexpert.com/mediawiki/index.php/Bea_Tuxedo

The above link gives a list of BEA Tuxedo Commands and Utilities.

To install PeopleTools client on individual machine, you may create a batch file with the folloiwng lines in it and execute it to create Peopletools Client.

@echo off
[PS_HOME]\bin\client\winx86\pscfg -clean -quiet
echo Setting up PeopleTools Environment
[PS_HOME]\bin\client\winx86\pscfg -import:[PS_HOME]\peoplesoft.cfg -setup -quiet

[PS_HOME] could be like C:\PSFT\FN88PRD\

peoplesoft.cfg is the configuration file.

A typical example of Log file creation in application engine using peoplecode is given below.

local File &Log_file;

&Log_file = GetFile(“c:\temp\logfilename.txt”, “W”, %FilePath_Absolute);

&Log_file.WriteLine(“Begin Process : ” | %Datetime);

&Log_file.close()

But if you have to use the same log file across the sections within an application engine, then
Declare the file as global in one of the initial step as given below.

Global File &Log_file;

&Log_file = GetFile(“c:\temp\logfilename.txt”, “W”, %FilePath_Absolute);
&Log_file.WriteLine(“Begin Process : ” | %Datetime);

Then in any following section’s peoplecode step, declare the global variable and start writing to the file.

Global File &Log_file;

&Log_file.WriteLine(“Write anything here”);

Don’t forget to close the log file at the end of application engine.

Global File &Log_file;

&Log_file.close()

We had a requirement to audit any SQL actions a user executes on any table, by loggin into SQL Query Analyser. We used SQL profiler to create a script as given below. Using the script, we created a new procedure in master database with an automatic start-on-restart option turned on. Once we restart sql server, the audit process start writing to a file which can be opened from SQL profiler. This file starts a new file once it reaches the file size maximum limit defined in the script or whenever SQL Server is rebooted. You may modify this script based on your requirement.

CREATE PROCEDURE dbo.dba_startup_audit  AS
– Create a Queue
declare @rc int
declare @TraceID int
declare @maxfilesize bigint
DECLARE @File NVARCHAR(100)
Declare @Year nvarchar(10)
Declare @Month nvarchar(10)
Declare @Day nvarchar(10)
Declare @Hour nvarchar(10)
Declare @Minute nvarchar(10)
set @Year = DATEPART(year,GETDATE())
set @Month = DATEPART(month,GETDATE())
set @Day = DATEPART(day, GETDATE())
set @Hour = DATEPART(hour, GETDATE())
set @Minute = DATEPART(minute, GETDATE())
SET @File = N’C:\temp\db_audit_trace’+@Year+@Month+@Day+@Hour+@Minute
set @maxfilesize = 10
exec @rc = sp_trace_create @TraceID output, 2, @File, @maxfilesize, NULL
if (@rc != 0) goto error

– Set the events
declare @on bit
set @on = 1
exec sp_trace_setevent @TraceID, 10, 1, @on
exec sp_trace_setevent @TraceID, 10, 2, @on
exec sp_trace_setevent @TraceID, 10, 6, @on
exec sp_trace_setevent @TraceID, 10, 8, @on
exec sp_trace_setevent @TraceID, 10, 10, @on
exec sp_trace_setevent @TraceID, 10, 11, @on
exec sp_trace_setevent @TraceID, 10, 12, @on
exec sp_trace_setevent @TraceID, 10, 14, @on
exec sp_trace_setevent @TraceID, 10, 22, @on
exec sp_trace_setevent @TraceID, 10, 35, @on

exec sp_trace_setevent @TraceID, 12, 1, @on
exec sp_trace_setevent @TraceID, 12, 2, @on
exec sp_trace_setevent @TraceID, 12, 6, @on
exec sp_trace_setevent @TraceID, 12, 8, @on
exec sp_trace_setevent @TraceID, 12, 9, @on
exec sp_trace_setevent @TraceID, 12, 10, @on
exec sp_trace_setevent @TraceID, 12, 11, @on
exec sp_trace_setevent @TraceID, 12, 12, @on
exec sp_trace_setevent @TraceID, 12, 14, @on
exec sp_trace_setevent @TraceID, 12, 22, @on
exec sp_trace_setevent @TraceID, 12, 35, @on
exec sp_trace_setevent @TraceID, 12, 41, @on
exec sp_trace_setevent @TraceID, 13, 1, @on
exec sp_trace_setevent @TraceID, 13, 2, @on
exec sp_trace_setevent @TraceID, 13, 6, @on
exec sp_trace_setevent @TraceID, 13, 8, @on
exec sp_trace_setevent @TraceID, 13, 9, @on
exec sp_trace_setevent @TraceID, 13, 10, @on
exec sp_trace_setevent @TraceID, 13, 11, @on
exec sp_trace_setevent @TraceID, 13, 12, @on
exec sp_trace_setevent @TraceID, 13, 14, @on
exec sp_trace_setevent @TraceID, 13, 22, @on
exec sp_trace_setevent @TraceID, 13, 35, @on
exec sp_trace_setevent @TraceID, 13, 41, @on

exec sp_trace_setevent @TraceID, 14, 1, @on
exec sp_trace_setevent @TraceID, 14, 2, @on
exec sp_trace_setevent @TraceID, 14, 6, @on
exec sp_trace_setevent @TraceID, 14, 8, @on
exec sp_trace_setevent @TraceID, 14, 9, @on
exec sp_trace_setevent @TraceID, 14, 10, @on
exec sp_trace_setevent @TraceID, 14, 11, @on
exec sp_trace_setevent @TraceID, 14, 12, @on
exec sp_trace_setevent @TraceID, 14, 14, @on
exec sp_trace_setevent @TraceID, 14, 22, @on
exec sp_trace_setevent @TraceID, 14, 35, @on
exec sp_trace_setevent @TraceID, 14, 41, @on

exec sp_trace_setevent @TraceID, 15, 1, @on
exec sp_trace_setevent @TraceID, 15, 2, @on
exec sp_trace_setevent @TraceID, 15, 6, @on
exec sp_trace_setevent @TraceID, 15, 8, @on
exec sp_trace_setevent @TraceID, 15, 9, @on
exec sp_trace_setevent @TraceID, 15, 10, @on
exec sp_trace_setevent @TraceID, 15, 11, @on
exec sp_trace_setevent @TraceID, 15, 12, @on
exec sp_trace_setevent @TraceID, 15, 14, @on
exec sp_trace_setevent @TraceID, 15, 22, @on
exec sp_trace_setevent @TraceID, 15, 35, @on
exec sp_trace_setevent @TraceID, 15, 41, @on

exec sp_trace_setevent @TraceID, 17, 1, @on
exec sp_trace_setevent @TraceID, 17, 6, @on
exec sp_trace_setevent @TraceID, 17, 8, @on
exec sp_trace_setevent @TraceID, 17, 9, @on
exec sp_trace_setevent @TraceID, 17, 10, @on
exec sp_trace_setevent @TraceID, 17, 11, @on
exec sp_trace_setevent @TraceID, 17, 12, @on
exec sp_trace_setevent @TraceID, 17, 14, @on
exec sp_trace_setevent @TraceID, 17, 22, @on
exec sp_trace_setevent @TraceID, 17, 35, @on
exec sp_trace_setevent @TraceID, 17, 41, @on

exec sp_trace_setevent @TraceID, 40, 1, @on
exec sp_trace_setevent @TraceID, 40, 2, @on
exec sp_trace_setevent @TraceID, 40, 6, @on
exec sp_trace_setevent @TraceID, 40, 8, @on
exec sp_trace_setevent @TraceID, 40, 10, @on
exec sp_trace_setevent @TraceID, 40, 11, @on
exec sp_trace_setevent @TraceID, 40, 12, @on
exec sp_trace_setevent @TraceID, 40, 14, @on
exec sp_trace_setevent @TraceID, 40, 22, @on
exec sp_trace_setevent @TraceID, 40, 35, @on

exec sp_trace_setevent @TraceID, 41, 1, @on
exec sp_trace_setevent @TraceID, 41, 2, @on
exec sp_trace_setevent @TraceID, 41, 6, @on
exec sp_trace_setevent @TraceID, 41, 8, @on
exec sp_trace_setevent @TraceID, 41, 10, @on
exec sp_trace_setevent @TraceID, 41, 11, @on
exec sp_trace_setevent @TraceID, 41, 12, @on
exec sp_trace_setevent @TraceID, 41, 14, @on
exec sp_trace_setevent @TraceID, 41, 22, @on
exec sp_trace_setevent @TraceID, 41, 35, @on

exec sp_trace_setevent @TraceID, 46, 1, @on
exec sp_trace_setevent @TraceID, 46, 2, @on
exec sp_trace_setevent @TraceID, 46, 6, @on
exec sp_trace_setevent @TraceID, 46, 8, @on
exec sp_trace_setevent @TraceID, 46, 10, @on
exec sp_trace_setevent @TraceID, 46, 11, @on
exec sp_trace_setevent @TraceID, 46, 12, @on
exec sp_trace_setevent @TraceID, 46, 14, @on
exec sp_trace_setevent @TraceID, 46, 22, @on
exec sp_trace_setevent @TraceID, 46, 34, @on

exec sp_trace_setevent @TraceID, 47, 1, @on
exec sp_trace_setevent @TraceID, 47, 2, @on
exec sp_trace_setevent @TraceID, 47, 6, @on
exec sp_trace_setevent @TraceID, 47, 8, @on
exec sp_trace_setevent @TraceID, 47, 10, @on
exec sp_trace_setevent @TraceID, 47, 11, @on
exec sp_trace_setevent @TraceID, 47, 12, @on
exec sp_trace_setevent @TraceID, 47, 14, @on
exec sp_trace_setevent @TraceID, 47, 22, @on
exec sp_trace_setevent @TraceID, 47, 35, @on

exec sp_trace_setevent @TraceID, 82, 1, @on
exec sp_trace_setevent @TraceID, 82, 6, @on
exec sp_trace_setevent @TraceID, 82, 8, @on
exec sp_trace_setevent @TraceID, 82, 9, @on
exec sp_trace_setevent @TraceID, 82, 10, @on
exec sp_trace_setevent @TraceID, 82, 11, @on
exec sp_trace_setevent @TraceID, 82, 12, @on
exec sp_trace_setevent @TraceID, 82, 14, @on
exec sp_trace_setevent @TraceID, 82, 22, @on
exec sp_trace_setevent @TraceID, 82, 35, @on
exec sp_trace_setevent @TraceID, 82, 41, @on

exec sp_trace_setevent @TraceID, 104, 1, @on
exec sp_trace_setevent @TraceID, 104, 2, @on
exec sp_trace_setevent @TraceID, 104, 6, @on
exec sp_trace_setevent @TraceID, 104, 8, @on
exec sp_trace_setevent @TraceID, 104, 10, @on
exec sp_trace_setevent @TraceID, 104, 11, @on
exec sp_trace_setevent @TraceID, 104, 12, @on
exec sp_trace_setevent @TraceID, 104, 14, @on
exec sp_trace_setevent @TraceID, 104, 22, @on
exec sp_trace_setevent @TraceID, 104, 35, @on

– Set the Filters
declare @intfilter int
declare @bigintfilter bigint

exec sp_trace_setfilter @TraceID, 10, 0, 7, N’People%’
exec sp_trace_setfilter @TraceID, 10, 0, 7, N’sqlmon.pl’
exec sp_trace_setfilter @TraceID, 10, 0, 7, N’SQL Profiler’
exec sp_trace_setfilter @TraceID, 10, 0, 7, N’SQLAgent%’
exec sp_trace_setfilter @TraceID, 10, 0, 7, N’MS SQLEM%’
exec sp_trace_setfilter @TraceID, 10, 0, 7, N’sqlsvr_collector.pl%’
exec sp_trace_setfilter @TraceID, 10, 0, 7, N’sqlsvr_backup_collector.pl%’
exec sp_trace_setfilter @TraceID, 10, 0, 7, N’ps_app_version_pop.pl%’
exec sp_trace_setfilter @TraceID, 10, 0, 7, N’SQLDMO%’
exec sp_trace_setfilter @TraceID, 10, 1, 6, N’SQL Query Analyzer%’
exec sp_trace_setfilter @TraceID, 1, 1, 6, N’Select%’
exec sp_trace_setfilter @TraceID, 1, 1, 6, N’Insert%’
exec sp_trace_setfilter @TraceID, 1, 1, 6, N’Update%’
exec sp_trace_setfilter @TraceID, 1, 1, 6, N’Create%’
exec sp_trace_setfilter @TraceID, 1, 1, 6, N’Drop%’
exec sp_trace_setfilter @TraceID, 1, 1, 6, N’Delete%’
–set @intfilter = 100
–exec sp_trace_setfilter @TraceID, 22, 0, 4, @intfilter
–exec sp_trace_setfilter @TraceID, 35, 1, 6, N’HR83FS’

– Set the trace status to start
exec sp_trace_setstatus @TraceID, 1
– display trace id for future references
select TraceID=@TraceID
goto finish
error:
select ErrorCode=@rc
finish:
GO
exec sp_procoption N’dba_startup_audit’, N’startup’, N’true’
GO

There was a need to put two different foot note in SQR Reports based on the page orientation (Landscape or Portrait). For this situation, we can creat one SQC using #if and PAGE_ORIENTATION variable defined in our standard setup01a.sqc, setup02a.sqc etc. The SQC lines are given below.

 #if {PAGE_ORIENTATION} = ‘PORTRAIT’
begin-footing 2
  print ‘Important Note: 1′ (1,1)
  !Add more lines as needed
end-footing
#else
    #if {PAGE_ORIENTATION} = ‘LANDSCAPE’
begin-footing 2
  print ‘Important Note: 2 ‘ (1,1) 
  !Add more lines as needed
end-footing
    #end-if
#end-if

This assumes that the main sqr report has included one of standard setup layout sqc like setup01.sqc or setup02.sqc which should have PAGE_ORIENTATION defined using #define.

PSQRYSTATS table tells you about when was a particular query last executed and more details. This PSQRYSTATS table has following fileds.

OPRID
QRYNAME
EXECCOUNT  – Count of Query Execution
AVGEXECTIME  – Average Query Execution Time
AVGFETCHTIME – Average Fetch Time
LASTEXECDTTM – DateTime of Last Execution
AVGNUMROWS – Average Number of Rows Fetched
NUMKILLS – Number of Times Killed

**********************

PSQRYDEFN has a field QRYTYPE. It is a number field and It’s values are listed below.
7  – ARCHIVE
5  - PROCESS
4  – ROLEQRY
1  – QUERY

On the Portal > Structure and Content, I opened a Content Ref Administration Page, on the General page, I observed Node Name as LOCAL_NODE. I clicked on the prompt for the field, it did show a LOCAL_NODE as valid value and in addition it showed this node as local and default node along with PT_LOCAL as default and local node. I was surprised as there cannot be two local and default nodes in a PIA. So I opened the component PORTAL_CREF_ADM and in that I opened the page PORTAL_CREF_ADM. Node Name field MSGNODENAME was from a derived work record PORTAL_CREF_ADM, I checked the prompt view for MSGNODENAME field, it was dynamic view PORTAL_NODE_VW, the SQL for this view is given below.

SELECT FILL.MSGNODENAME
 , FILL.DESCR
 , FILL.LOCALNODE
 , FILL.LOCALDEFAULTFLG
 , FILL.NODE_TYPE
  FROM PSMSGNODEDEFN FILL
  UNION
 SELECT ‘LOCAL_NODE’
 , ‘ ‘
 , 1
 , ‘Y’
 , ‘PIA’
  FROM PSMSGNODEDEFN FILL

The LOCAL_NODE I saw on structure and content page was a dummy node.

People Tools version 8.49

The REN Server is a Real Time Event Notification system that allows reports to be printed to a separate browser window. 

If you are getting “Communication with REN Server failed (HTTP 403 Forbidden) ” error message, when trying to open a report to a separate browser window or trying to ping the REN server,  then follow the following steps suggested by PeopleSoft for checking REN server.

Case # 1:
Make sure that you have the proper REN server permissions configured.

Navigate to PeopleTools > Security > Permissions and Roles > Permission Lists.  Select the primary permission list that is tied to the user profile that you are testing with.  You will also have to grant permissions to the USER ID that is configured for your Process Scheduler database signon settings, if that user is different than the one that you are currently logged in as.  Once the permission list is up, go to the PeopleTools tab.  Click on the “Realtime Event Notification Permissions” link in the middle of the page.  On the next page, make sure that the access code for Reporting Window is set to full access. 

Next, go to the Web Libraries tab.  Make sure that there is an entry for WEBLIB_RPT.  If it is not there, then please add the library in.  Once that is added, click on the edit link and make sure that the access permissions are set to full access.

Make sure to save the changes before exiting.

Next, navigate to PeopleTools > Portal > Node Definitions and click search to bring up all of your nodes.  Sort so that your default local node is listed at the top.  Click on the name link for the default local node and make sure that the Authentication Option is set to password and that a password has been entered. 

Finally, navigate to PeopleTools > Security > Security Objects > Single Signon.  Make sure that your default local node is listed there.

Case #2
If using an authentication domain, make sure that the REN server configuration is specifying the domain:
  -Navigate to PeopleTools -> REN Server Configuration -> REN Server Cluster
  -Select your REN Server Cluster
    -Verify ‘Authentication Domain’ has been specified
    -Verify that the domain is specified in the ‘REN Server Browser URL’

Case # 3
This case applies to PeopleTools 8.44 only.  If the initial PIA deployment did not specify an Authentication Domain, but the environment now has one, it is necessary to add the Authentication Domain to the active Web Profile.  Navigate to PeopleTools > Web Profile.  Search for and select the active Web Profile.  (If you do not know what Web Profile is currently active, check your configuration.properties file.  It will tell you what Web Profile is currently active).  Once you have the Web Profile up, the first tab should be labeled “General”.  Make sure the field for Authentication Domain field on the General tab has your company’s Authentication Domain (ex. mycompany.com).  Make sure to save your changes and bounce the web server for the change to take effect, then go back and try running your Ping Test.

Case # 4:
One customer reported that in their REN Server Configuration > REN Server Definition page, the Application Server Domain name was case sensitive.  After they changed the Application Server Domain name to match how it was defined through PSADMIN (in this case, to include lowercase characters), they were able to access the REN server.

Case # 5:
If you are still having issues after trying the suggestions above, then try clearing cache in case some Ren configuration changes were made, but cache was not cleared afterwards.  To clear cache,  bring down the PIA web server and the application server and clear the cache.  Also, clear the cache and cookies from your browser and close all browser sessions.  Restart the PIA web server and application server.   Then run ping test again.

The only local node definition used by PeopleSoft Integration Broker is the one designated Default Local, which represents the database onto which you are signed. Only portals use nodes designated simply as Local.

If we try to ping a local node which is not a default local node, we will get the following message. Destination node does not match the local node (158,506).

Default Local Node indicates whether the current node represents the database to which you are assigned. PeopleSoft Integration Broker is delivered with one node predefined as the default local node. You can’t change which node is the default local node, but you can use the Rename Node button to rename the default local node to more appropriately reflect your application or system.

To change the password for VP1/PS, following steps are to be executed.

1. Change VP1/PS Password online. Login to the appropriate PeopleSoft instance online, PeopleTools > Security > User profile open VP1/PS profile and change the password.
2. Shutdown appserver and process scheduler server
3. Change the password for VP1/PS in Application Server configuration using psadmin.
4. Change the password for VP1/PS in Process Scheduler Server configuration using psadmin.
5. Start appserver and process scheduler server
6. Web profile Configuration – Go to PeopleTools > Web Profile – open up the related profile and update the password in the security tab.
7. Change the VP1/PS password in Integration broker configuration file. Go to PeopleTools > Integration Broker > Gateway open the local Gateway – Click on properties link, enter user id and password and in the gateway configuration file change VP1/PS password.

When we schedule a processes/Report to run by loggin in as say, VP1, then to see the output/report you have to login with the same User Id VP1. If the requirement is that another user need to see the same output/report, without using VP1 user id, then we need to do report distribution and give the user access to report manager so the user can view other’s reports. One way of achieving this as given below.

• Add the following roles to user
  • ReportDistAdmin or ReportSuperUser(See the Note below).
  • Any role containing permission List – CPPT1040 (gives access to Report manager) or similar one.
• To all the processes/reports that user needs to have access, add the userid to distribution list of that processe/report.
  • Go to the process/report run control page
  • Slect run control Id
  • Click run
  • Click ‘distribution’ link for the process/report.
  • Select either a user and enter his User Id.
  • You have to submit the process/report, once for the distribution data you have entered to save.
• Submit the process/report for testing.
• Now if the user logs in and go to  Administration tab in Report Manager, he could see the process/reports and link to see the output/report. User can see the output/report using process monitor also.

 Note: The difference between the administrator (ReportDistAdmin) and super user (ReportSuperUser) roles is that the administrator role can access and update any report in the Report Manager. The super user role can  update only reports that they are authorized to view.

Report Manager related other blog entries are given below:

• greysparling – Report Manager Performance
• Using Report manager
• Report manager

• Query is a PeopleTool that helps you build SQL queries to retrieve information from your application tables.
• Query takes advantage of user’s security settings, row-level security, and primary permission list.
• For each Query user, you can specify the records they are allowed to access when building and running queries. We can achieve this by creating Query Access Groups in the Query Access Group Manager, and then you assign users to those groups with Query permissions.  

Query Access Group Trees:

• Trees are a graphical way of presenting hierarchical information.
• PeopleSoft Query uses query access group trees to control the access of the tables in your PeopleSoft database.
• Define a hierarchy of PeopleSoft record definitions, based on logical or functional groupings, and then give users access to one or more nodes of the tree.
• Users can retrieve information only from those tables whose record definitions to which they have access.
•  Nodes: Query access group trees contain two types of Nodes: groups and records.
  • Groups are a logical representation of a set of child groups or records. It is similar to folder in Windows.
  • Records represent a PeopleSoft record definition.
• Structure:
  • Always use the ACCESS_GROUP Tree Structure.
  • Do not use SetID or UKV/BU.
  • Do not have Details.
  • Do not use Levels.
  • No Branches.

• Requirements:

  • The Root Node is always a group.
  • Groups must be unique in a given Tree while records definitions can be repeated.
  • Groups and records could have Child Groups and Child Records.
  • Each record needs a unique fully qualified path in the tree. You can’t add the same record under the same parent node (group or record).
• To open an existing Query Access Group Tree, Select PeopleTools, Security, Query Access Manager.
• Create custom Query Access Group suitable to your organization. Create functional group names and add records under the group.
• To Add the Query Access Groups to user:
  • Open the primary Permission List for the user
  • Go to ‘Query’ Tab
  • Click on Access Group Permissions.
  • Add the tree name, select the proper Access Group, Select ‘Accessible’ button. Repeat to add more Access groups.
  • Save the permission List.

Row Level Security:

• By default, when you give Query users access to a record definition, they have access to all the rows of data in the table built using the associated record definition.
• With row-level security, users can have access to a table without having access to all rows on that table.
• This type of security is typically applied to tables that hold sensitive data.
• For example, you might want users to be able to review personal data for employees in their own department, but not for people in other departments. You would give everyone access to the PERSONAL_DATA table, but would enforce row-level security so that they could only see rows where the DEPTID matches their own.
• PeopleSoft applications implement row-level security by using a SQL view that joins the data table with an authorization table.
• When a user searches for data in the data table, the system performs a related record join between the view and the base table rather than searching the table directly.

Query Security Record Definitions:

• You implement row-level security by having Query search for data using a query security record definition. The query security record definition adds a security check to the search.
• Query security record definitions serve the same purpose as search record definitions do for panels. Just as a panel’s search record definition determines what data the user can display in the panel, the query security record definition determines what data the user can display with Query.
• To get Query to retrieve data by joining a security record definition to the base table, you specify the appropriate Query Security Record when you create the base table’s record definition.

To apply row level security:

1. Select PeopleTools, Application Designer to open the Application Designer, and open the record on which you want to apply row-level security.
2. With the record definition open in the Application Designer, click the Properties button, and select the Use tab from the Record Properties dialog box.
3. Select the security record definition (usually a view) in the Query Security Record list box.
4. Once you’ve set the query security record definition, click OK to close the Record Properties dialog box, then save the record definition. If you’ve already used SQL Create to build a table from this record definition, you don’t need to rebuild it.

Note. PeopleSoft row-level security views restrict users from seeing certain rows of data. To secure data through the search record, simply put one of the three Row Level Security fields on your record as a Key, not a List Box Item. The three Row Level Security fields are OPRID (User ID), OPRCLASS (Primary Permission List), and ROWSECCLASS (Row Security Permission List). If one of these fields is on the search record as a Key, not a List Box Item, PeopleTools does the following. PeopleTools adds a WHERE clause when it performing a SELECT through the record forcing the value to be equal to the current user’s value.

I tried to distribute a report by email, set distribution type as ‘Email’ and format as ‘PDF’ and enter either a user with proper email or enter a desired email in Distributio detail. The report ended with an error, saying unable to send email. I opened up the message log file and the error text was as shown below.

3 parameters
Parameter 0 = psmail
Parameter 1 = -INPUTC:\DOCUME~1\hrdev\Local
Parameter 2 = Settings\Temp\PRCD3.tmpSMTP Settings:

SMTPServer = outbound.smtp.net
SMTPPort = 25
SMTPServer1 =
SMTPPort1 = 0
SMTPSender = psadmin@peoplesoft.com
SMTPSourceMachine = Error opening file, error code 2
Error opening file, error code 2
Error opening file, error code 2
Error opening file, error code 2
Error opening file, error code 2
Error opening file, error code 2ERROR: sender or recipient are missing.Command line arguments are incorrect

Here are the steps for configuring Integration Gateway in PeopleSoft: 

Open a browser and enter the URL string in the address bar http://ipaddress/PSIGW/PeopleSoftListeningConnector Click enter, you will see the screen showing the following message.

PeopleSoft Integration Gateway
 
PeopleSoft Listening connector
Tools version:8.45.10
Status: ACTIVE

Loading Gateway Connectors:
Go to PeopleTools> Integration Broker> Gateways

On this page check the Local Gateway check box.
Enter http://ipaddress/PSIGW/PeopleSoftListeningConnector  in the URL field

First Save the Page. Then Click on Load Gateway Connectors button, this will populate all the Connectors and shows the following message.

Loading Process was successful. Number of connectors Loaded:10, Number of Properties Loaded 164.(158,42)

Hit the Save Button to save all the connectors.

Modification of Gateway Properties file:

Click on Properties link after the URL field.

Enter USERID and Password. (Default USERID = administrator and Password = password)

Gateway Properties file will open up.

Modify the following lines in the gateway properties file

ig.isc.PT_LOCAL.serverURL=//ipaddress:JOLT Listener Port
ig.isc.PT_LOCAL.userid=VP1
#Use the supplied “PAssword Encryption Utility” to generate an encrypted password for the next entry.
ig.isc.PT_LOCAL.password=GD9klUFw8760HVaqeT4pkg==
ig.isc.PT_LOCAL.toolsRel=8.45.10

After modification of Gateway Properties file, Click on Apply button, and then Click on OK button. Save the Gateway page again.

From 8.49 tools onwards, you no longer need to edit the gateway properties file, instead there will be fields you need to fill the fields. Check the Node by pinging the node. You should get success result when you ping the node. Then Save the page.

Reboot the web server after the configuration file is modified.

Making Domain Status Active:
Go to PeopleTools> Integration Broker> Monitor > Monitor Message, click on Domain Status tab.

Select the Domain Status as active,  click on Update button.
Click on Refresh button to see the Dispatcher status as ACT (Active)

With this the Integration Broker configuration is complete.

-DBconnection string option in Begin-Select, allows you to combine data from multiple databases in one program. An example for this is, Your SQR report which will be running from Finance database, needs name of employee from HRMS database. Create a procedure with -dbconnectionstring as show below.

Begin-Procedure Get_Empl_Name
#debugy show ‘In Procedure : Get_Empl_Name’

let $dbname = ‘DBNAME’
let $dbconnstr = ‘DSN=’ || $DbName || ‘;UID=USERID;PWD=PASSWORD’

Begin-Select -DB$dbconnstr
EMPLID
NAME
     show &emplid ‘ – ‘ &name
FROM PS_PERSONAL_DATA
WHERE EMPLID = $emplid
End-Select
End-Procedure !Get_Empl_Name

For this to work, we need to establish DB Link between the two databases. In the above example, the Finance database should have a DB Link established with HRMS database. The User-id and password, given in the connection string is the user id and password established while creating DB Link. We can assign appropriate access for this userid in DB Link.

While testing, you might want to know how much time a particular procedure or a step in sqr is taking. You may use the following to know the time spent by a procedure or a step.

Begin-Program
let $start_time = edit(datenow(), ‘DD/MM/YYYY-HH:MI:SS:NNNN’)
   do any-procedure-or-step
let $end_time = edit(datenow(), ‘DD/MM/YYYY-HH:MI:SS:NNNN’)
let #total_time = datediff(strtodate($end_time,’DD/MM/YYYY-HH:MI:SS:NNNN’), strtodate($start_time,’DD/MM/YYYY-HH:MI:SS:NNNN’),’minute’)
#debugy show ‘total time taken by the Program = ‘ #total_time  ‘ minutes’
End-Program

We can use the following as an sqc, for performing file operations in SQR. 

!*********************************************************************
!Program Name : FileOprs.sqc
!Description        : File operations using DOS commands.
!*********************************************************************

!*********************************************************************
!Procedure Name : Make_Dir
!Description        : Creates a new path based on the input. Path must be
!                        a complete directory tree listing.
!Usage              : Do Make_Dir($Directory_NewPath)
!*********************************************************************
begin-procedure  Make_Dir($NewPath)
#debugy show ‘In Procedure : Make_Dir’

Let $Commmand_line = ‘cmd /c mkdir ‘ || $NewPath
Do Exec_Cmd($Commmand_line)

end-procedure ! Make_Dir

!*********************************************************************
!Procedure Name : Exec_Cmd
!Description        : Executes $Commmand_line on the system and reports
!                         errors for debugging.
!Usage               : Do Exec_Cmd($Commmand_line)
!*********************************************************************
begin-procedure  Exec_Cmd($Commmand_line)
#debugy show ‘In Procedure : Exec_Cmd’

call system using $Commmand_line #status nowait
If #status <> 0
    #debugy show ‘Command ‘ $Commmand_line ‘ failed to execute.’
End-If

end-procedure ! Exec_Cmd

!*********************************************************************
!Procedure Name : Copy_Files
!Description : Copy files from old to new path. Old information should be of
!       form \pathname\filename, while new information can just be a path.
!Usage               : Do Copy_Files($old_file_name, $new_file_name)
!*********************************************************************
begin-procedure  Copy_Files($old, $new)
#debugy show ‘In Procedure : Copy_Files’

Let $Commmand_line = ‘cmd /c copy ‘ || $old || ‘ ‘ || $new
Do Exec_Cmd($Commmand_line)

end-procedure ! Copy_Files

!*********************************************************************
!Procedure Name : Move_Files
!Description    : Move files from old to new path. Old information should be of
!           form \pathname\filename, while new information can just be a path.
!Usage               : Do Move_Files($old_file_name, $new_file_name)
!*********************************************************************
begin-procedure  Move_Files($old, $new)
#debugy show ‘In Procedure : Move_Files’

Let $Commmand_line = ‘cmd /c move ‘ || $old || ‘ ‘ || $new
Do Exec_Cmd($Commmand_line)

end-procedure ! Move_Files

!*********************************************************************
!Procedure Name : Delete_Files
!Description        : Deletes the files passed in variable $files
!Usage               :  Do Delete_Files($files)
!*********************************************************************
begin-procedure  Delete_Files($files)
#debugy show ‘In Procedure : Delete_Files’

Let $Commmand_line = ‘cmd /c del ‘ || $files
Do Exec_Cmd($Commmand_line)

end-procedure ! Delete_Files

Here is a typical peoplecode example for reaching the level three reord using rowset peoplecode. 

/* Need to insert a row when a flag = ‘Y’ after graying all other fields in the row in correction mode */
PeopleCode Event : COMPONENT_NAME(Component).GBL.PostBuild(Component PeopleCode)

Local Rowset &TQ_Lvl0, &TQ_Lvl1, &TQ_Lvl2, &TQ_Lvl3;
Local number &insert_row, &lvl_1_row, &lvl_2_row, &lvl_3_row;

&TQ_Lvl0 = GetLevel0();
&TQ_Lvl1 = &TQ_Lvl0(1).GetRowset(Scroll.LEVEL1_SCROLL_NAME);
&insert_flag = “N”;

For &lvl_1_row = 1 To &TQ_Lvl1.ActiveRowCount
   &TQ_Lvl2 = &TQ_Lvl1(&lvl_1_row).GetRowset(Scroll.LEVEL2_SCROLL_NAME);
   For &lvl_2_row = 1 To &TQ_Lvl2.ActiveRowCount
      &TQ_Lvl3 = &TQ_Lvl2(&lvl_2_row).GetRowset(Scroll.LEVEL3_SCROLL_NAME);
      For &lvl_3_row = 1 To &TQ_Lvl3.ActiveRowCount
         &tq_adj_applied = &TQ_Lvl3(&lvl_3_row).LEVEL3_RECORD_NAME.FIELD_NAME.Value;
         If &tq_adj_applied = “Y” Then
            &TQ_Lvl3(&lvl_3_row).MPF_TINQ_LOG.EARNS_END_DT.Enabled = False;
            &TQ_Lvl3(&lvl_3_row).MPF_TINQ_LOG.MPF_ADD_SUBTRACT.Enabled = False;
            &TQ_Lvl3(&lvl_3_row).MPF_TINQ_LOG.MPF_HOURS_TYPE.Enabled = False;
            &TQ_Lvl3(&lvl_3_row).MPF_TINQ_LOG.MPF_HOURS_ADJ.Enabled = False;
            If %Mode = %Action_Correction Then
               &TQ_Lvl3.InsertRow(&TQ_Lvl3.ActiveRowCount);
            End-If;
         End-If;
      End-For
   End-For;
End-For;