Archive

Archive for the ‘PS Admin’ Category

Using WebLogic Server Console to Monitor PeopleSoft Sessions

October 10, 2008 2 comments

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.

Categories: PS Admin Tags:

BEA Tuxedo Commands & Utilities

September 22, 2008 Leave a comment

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

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

PeopleTools client installation Batch file

September 19, 2008 3 comments

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.

SQL server database audit

September 14, 2008 Leave a comment

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

Steps to check REN Server failure

August 4, 2008 Leave a comment

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.

Categories: PS Admin Tags:

Report Distribution – Report Manager

March 7, 2008 19 comments

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:

Email distribution error

January 17, 2008 Leave a comment

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.tmp
SMTP 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 2
ERROR: sender or recipient are missing.Command line arguments are incorrect

Failure… email not sent

This error is because User defined environment variables TEMP and TMP is set to a long string like “C:\DOCUME~1\hrdev\Local Settings\Temp”. The space in that string, makes one parameter split into two parameters. Obviously the paramter2 and parameter3 put separately makes the file location unreadable and hence email fails. 

To resolve this problem the User defined Environment variables TEMP and TMP should be set to a simple string like C:\temp, with no space in it. Since the User defined environment variables are user ID specific, Make sure that the user who boots the application server and process scheudler server should login and reset the TEMP and TMP user variable. After Changing the variable, the same user need to restart the process scheduler server.

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

Email Distribution Parameters:

The Email subject, Message Text, and Email Address List data entered on the email distribution page is stored in the PSPRCSRQSTTEXT table. The key for this table is process instance.

SELECT * FROM PSPRCSRQSTTEXT WHERE PRCSINSTANCE = ‘123456’

Categories: PS Admin