Category Archives: TRAM

You are not authorized to view the report(s).

Posted by on February 9, 2010 No comments

Problem:

After creating clone (tramdmo), the DDDAUDIT report was run from Process Scheduler. The report completes successfully, but when trying the view the report (PeopleTools > Process Scheduler > Process Monitor, then Details > View Log/Trace), the fsdmo PIA login screen appears with the message:

You are not authorized to view the report(s).

Solution:

Navigate to PeopleTools > Process Scheduler > Report Nodes

Set URL to http://GLWEBAPP:8020/psreports/tramdmo
Set Description to TRAMDMO Reporting Node
Ensure Operating System is NT/Win200
Network Path is \glwebappe$psreports

The correct URL now appears:

Click to access DDDAUDIT_7311.PDF

Page Not Found After SSL Setup

Posted by on December 9, 2009 No comments

Problem:

After setting up SSL on PeopleSoft instance, logon page appears. After logging on, the web browser displays the message:

This page cannot be displayed.

Solution:

Needed to change Web Profile from DEV to PROD in Application Server config file.

PeopleSoft HR 8.9 Installation Steps

Posted by on August 28, 2009 No comments

Hardware/Software Specifications

Server Hostname

Server Description IP Address
GLWEBAPP GL Web & App Server 10.x.x.x
GLDBASE GL Database Server 10.x.x.x

The machines that were used in the installation of the PeopleSoft test environments were Dell PowerEdge 2950.

The operating system for both servers was Microsoft Windows Server 2003 R2 Enterprise Edition Service Pack 2.

The GLDBASE machine shall house only the database server software (Microsoft SQL Server 2005).

The GLWEBAPP machine shall house all the other server software:

  • File Server (PeopleTools)
  • Application Server (Tuxedo)
  • Web Server (IBM WebSphere)
  • Batch Server

These two servers were accessed remotely using Remote Desktop Connection. Local administrator accounts were set up on these two machines. The username for these accounts were ProjAdmin1, ProjAdmin2 and ProjAdmin3.

Installation Sequence

The following steps were performed in this sequence to install the PeopleSoft Demo instance:

 PeopleSoft Demo Installation (FSDMO)

  1. Install SQL Server [ok 10-Nov-08]
  2. Install PeopleTools 8.49 on Database Server [17-Nov-08]
  3. Install PeopleTools 8.49 on Application Server [ok 11-Nov-08]
  4. Install Application (Financials) on Database Server [ok 17-Nov-08]
  5. Install Application (Financials) on Application Server [ok 11-Nov-08]
  6. Install Tuxedo (Application Server) [ok 11-Nov-08]
  7. Install PeopleTools 8.49.15 Product Patch on Database Server [ok 17-Nov-08]
  8. Install PeopleTools 8.49.15 Product Patch on Application Server [ok 12-Nov-08]
  9. Install IBM WebSphere (Web Server) [ok 11-Nov-08]
  10. Create Database Manually [ok 18-Nov-08]
  11. Shutdown, Backup Database After Creating
  12. Install PIA for WebSphere (fsdmo) [ok 18-Nov-08] [reinstall WebLogic 28-Nov-08]
  13. Create Application Domain [ok 18-Nov-08]
  14. Install PeopleTools PeopleBooks [ok 18-Nov-08] [reinstall 1-Dec-08]
  15. Install Application PeopleBooks [ok 18-Nov-08] [reinstall 1-Dec-08]
  16. Create Process Scheduler [ok 18-Nov-08]
  17. Apply Maintenance Pack 5 (Financials)

PeopleSoft Demo Installation (FSDEMO)

This FSDEMO installation shall be a plain-vanilla installation (without MP5).

  1. Install SQL Server [already installed]
  2. Install PeopleTools 8.49 on Application Server [ok 15-Dec-08] [E:PSOFTFSDEMO]
  3. Install PeopleTools 8.49 on Database Server [ok 15-Dec-08] [D:PSOFTFSDEMO]
  4. Install Application CDs (Financials) on Database Server [ok 15-Dec-08]
  5. Install Application CDs (Financials) on Application Server [ok 15-Dec-08]
  6. Install PeopleTools 8.49.15 Product Patch on Database Server [ok 15-Dec-08]
  7. Install PeopleTools 8.49.15 Product Patch on Application Server [ok 15-Dec-08]
  8. Install Tuxedo CD (Application Server) [already installed in E:bea]
  9. Install IBM WebSphere CD (Web Server) [already installed in E:IBMWebSphere]
  10. Create Database Manually [ok 18-Nov-08]
  11. Shutdown, Backup Database After Creating
  12. Install PIA for WebSphere (fsdmo) [ok 18-Nov-08] [reinstall WebLogic 28-Nov-08]
  13. Create Application Domain [ok 18-Nov-08]
  14. Install PeopleTools PeopleBooks [ok 18-Nov-08] [reinstall 1-Dec-08]
  15. Install Application PeopleBooks [ok 18-Nov-08] [reinstall 1-Dec-08]
  16. Create Process Scheduler [ok 18-Nov-08]
  17. Apply Maintenance Pack 5 (Financials)

PeopleSoft Sys Installation

  1. Install SQL Server [ok 10-Nov-08]
  2. Install PeopleTools 8.49 on Database Server [17-Nov-08]
  3. Install PeopleTools 8.49 on Application Server [ok 11-Nov-08]
  4. Install Application (Financials) on Database Server [ok 17-Nov-08]
  5. Install Application (Financials) on Application Server [ok 11-Nov-08]
  6. Install Tuxedo (Application Server) [ok 11-Nov-08]
  7. Install PeopleTools 8.49.15 Product Patch on Database Server [ok 17-Nov-08]
  8. Install PeopleTools 8.49.15 Product Patch on Application Server [ok 12-Nov-08]
  9. Install IBM WebSphere (Web Server) [ok 11-Nov-08]
  10. Create Database Manually [ok 18-Nov-08]
  11. Install PIA for WebSphere (fsdmo) [ok 18-Nov-08]
  12. Create Application Domain [ok 18-Nov-08]
  13. Install PeopleTools PeopleBooks [ok 18-Nov-08]
  14. Install Application PeopleBooks [ok 18-Nov-08]
  15. Create Process Scheduler
  16. Install Crystal Reports (on Workstation)
  17. Install Change Assistant
  18. Apply Maintenance Pack 5 (Financials)

Precedence

The SQL Server software must be installed before the PeopleTools.

PeopleTools Product Patch must be installed before PIA.

Step 1: SQL Server Installation

The Microsoft SQL Server 2005 DVD was staged (that is, copied) to D:stagingSQLServer2005 on the GLDBASE machine. After staging, setup.exe from D:stagingSQLServer2005Servers was run.

By default, the following required components were installed prior to installing SQL Server:

  • .NET Framework 2.0
  • Microsoft SQL Native Client
  • Microsoft SQL Server 2005 Setup Support Files

These components were installed to C:Program FilesMicrosoft SQL Server by default.

The other SQL Server components were installed to D:Program FilesMicrosoft SQL Server. These components are:

  • Database Services
    • Data Files
    • Replication
    • Full-Text Search
    • Shared Tools
  • Client Components
    • Connectivity Components
    • Management Tools

The Microsoft SQL Native Client (SNaC) must also be installed on the GLWEBAPP machine in which PeopleTools is installed. To do so, share the D:staging directory on GLDBASE (10.18.14.31). From GLWEBAPP, navigate to \10.x.x.xstagingSQLServer2005Servers. Then run setup.exe.

Allow the required components to install (.NET Framework 2.0, Microsoft SQL Native Client and Microsoft SQL Server 2005 Setup Support Files). Continue the installation and install the Connectivity Components on GLWEBAPP.

Step 2: File Server (PeopleTools) Installation

It was necessary to install up the SQL Server Connectivity Components on the GLWEBAPP because the SQL Server Connectivity Program Directory must be specified as part of the installation.

The seven PeopleTools CDs were staged to the E:stagingCDImages

Note that you MUST install PeopleTools on both nodes.

The following values/options were set as part of the PeopleTools installation on the peoplesoft4hr node:

Variable Value
PeopleSoft (PeopleTools) License code z66smq-22c7mc-3w444e1-2is234-81p1f7
Type of Database Non-Unicode Database
Peoplesoft Application Server Checked
Peoplesoft Batch Server Checked
Peoplesoft Database Server Checked
Peoplesoft File Server Checked
Peoplesoft Web Server Checked
PS_HOME Drectory Name E:PSOFTHR900
ERP Connectors? No
Connectivity Program Directory C:Program FilesMicrosoft SQL Server80Toolsbinn
Install PeopleTools Icons? Yes
PeopleTools Program Group Folder PeopleTools 8.4
Environment Hub machine name Peoplesoft4hr
Environment Hub Port Number 8000
PeopleTools (Product Installation) Checked
PeopleTools System Database Checked
PeopleTools Language Pack Not checked
PeopleTools Language Development Kit Not checked

Step 3: Application Installation

To install the PeopleSoft Enterprise Human Resources Management System and Campus Solutions 9.0 (HR) application, the disk was obtained from the CD. It was unzipped (“exploded”) and staged to the F:stagingcd849-HR directory, in the disk1 directory.

To install the Financials application, navigate to F:stagingcd849-HRdisk1 directory and run setup.exe

The following values/options were entered

Variable Value
PeopleSoft (HRMS) License code
Type of Database Non-Unicode Database
PeopleSoft Application Server Checked
PeopleSoft Batch Server Checked
PeopleSoft Database Server Checked
PeopleSoft File Server Checked
PeopleSoft Web Server Checked
PS_HOME Directory Name E:PSOFTFS900

Step 4: Application Server (Tuxedo) Installation

The Tuxedo 9.1 CD (Windows version) was staged to E:stagingCDImagescd849-Tuxdisk1 on the GLWEBAPP server. To install Tuxedo, run pstuxinstall.exe. This brings up a console interface (as opposed to a GUI wizard).

The following prompts appeared when psstuxinstall.exe is run:

1 file(s) copied.

1 file(s) copied.

BEA Home being defaulted to C:\bea  (y/n)? [y]: n

Please provide a BEA Home: E:\bea

Tuxedo 9.1 will be installed to E:\beaTuxedo9.1  (y/n)? [y]: <Enter>

TListen port being defaulted to 3050  (y/n)? [y]: <Enter>

Accept default TListen password ‘password’  (y/n)? [y]: <Enter>

Are you happy with your selections (y/n)? [y]: <Enter>

Tuxedo 9.1 is being installed on your system….

Tuxedo 9.1 base install completed.

Stopping Tuxedo 9.1 Services…

The TListen 9.1 (Port: 3050) service is stopping..

The TListen 9.1 (Port: 3050) service was stopped successfully.

The BEA ProcMGR V9.1 service is stopping.

The BEA ProcMGR V9.1 service was stopped successfully.

Patch installation completed.

Please note that you must reboot your system before using any Tuxedo 9.1 or PeopleSoft applications.

Press any key to continue…

After installing Tuxedo, the GLWEBAPP server was rebooted remotely.

Step 5: Web Server (WebSphere) Installation

The two IBM WebSphere CDs (Windows version) were staged to the E:stagingCDImagescd849-WebSphere directories, in the disk1 and disk2 directories.

To install IBM WebSphere, navigate to disk1 and run installWAS.bat.

Install to E:IBMWebSphereAppServer

For Environments, choose None, then click Yes to accept the choice.

In the Summary screen, click Next.

Uncheck the Create a new WebSphere Application Server profile, and then click Finish.

Step 6: PeopleTools 8.49.15 Product Patch Installation

Check Customer Connection (now Metalink3 at http://metalink3.oracle.com) for the latest PeopleTools 8.49 Product Patch. As at this time, the latest PeopleTools Product Patch for version 8.49 is 8.49.15.

Download this patch 84915.exe from:

ftp://ftp.peoplesoft.com/outgoing/ptools/84915/84915.exe

(The password for 84915.exe is ‘MisterEd’)

Run 84915.exe and unzip the file to E:stagingCDImages. It automatically creates the cd84915 directory and unzips the file.

From E:stagingCDImagescd84915disk1, run setup.exe. It updates PS_HOME (E:PSOFTFS900) with the updated files.

Step 7: Pure Internet Architecture (PIA) Installation

To create the PIA, change directory to E:PSOFTFS900PsMpPIAInstall and run setup.exe

Install PIA to the IBM WebSphere web server, located in E:IBMWEBSPHEREAppServer.

Application name and web site name should be set to the name of the environment e.g. fsdmo. Create a Multi Server installation, not a Single Server installation.

Note that the port numbers for http and https must not be consecutive.

Web Profile Name, User ID and Password should remain the default.

The Report Repository should be set to E:psreports.

The installation process takes about ten minutes to complete.

PeopleSoft HR 8.9 Installation Checklist

Posted by on August 28, 2009 No comments

1. Install SQL Server

2. Install SQL Server Native Client

3. Stage PeopleTools 8.49 CDs on F:stagingpt-849

4. Install PeopleTools 8.49 on peoplesoft4hr (E:PSOFTHR900)

5. Install Application (Human Resources) on peoplesoft4hr

6. Install Database Manually

7. Task B-1: Running Server Configuration Scripts

8. Task B-2: Creating a Database

9. Task B-3: Configuring ODBC Data Source

10. Task B-4: Running ADDOBJ.SQL

11. Task B-5: Setting Up Connect ID

12. Task B-6: Creating Data Mover Import Scripts

13. Task B-7: Running Data Mover Import Scripts

14. Task B-8: Updating Database to Latest PeopleTools Release

15. Task B-8-2: Updating PeopleTools System Tables

16. Task B-8-3: Updating PeopleTools Database Objects

17. Task B-8-5: Deleting Obsolete PeopleTools Database Objects

18. Task B-8-6: Altering PeopleTools Tables

19. Task B-8-7: Updating PeopleTools System Data

20. Task B-8-8: Running PeopleTools Conversions

21. Task B-9: Running Additional Data Mover Scripts

22. Task B-11: Running VERSION Application Engine Program

23. Task B-12: Changing the Base Language

24. Task B-13: Running SQR Reports

25. Task B-14: Checking the Database

26. Task B-15: Cleaning and Backing Up the Database

27. Shutdown, Backup Database After Creating

28. Install Tuxedo (Application Server)

29. Install BEA WebLogic 9.2 Web Server

30. Install PIA

31. Create Application Domain

32. Install PeopleTools PeopleBooks

33. Install Application PeopleBooks

34. Create Process Scheduler

35. Install COBOL compiler (and license)

36. Execute PTPATCH.DMS using Data Mover (8.49.15)

37. Apply project PATCH849 using Application Designer

38. Run DDDAUDIT, SYSAUDIT to verify system ok, troubleshoot if necessary

39. Shutdown all servers and backup PS_HOME

Running DDDAUDIT

Posted by on February 12, 2009 No comments

To run DDDAUDIT manually:

1. Click Start > Run

2. Click Browse, navigate to binsqlMSSbinw, and select sqrw.exe. Append the necessary flags:

On glwebapp:

E:PSOFTFS900binsqrMSSBINWsqrw.exe -IE:PSOFTFS900sqr -ZIFE:PSOFTFS900sqrpssqr.ini -fC:Temp -KEEP

Note that the above is one line without breaks.

If PS_HOME is mapped to a drive, use the drive letter instead:

P:binsqrMSSBINWsqrw.exe -IP:sqr -ZIFP:sqrpssqr.ini -fC:Temp -KEEP

Parameters for DDDAUDIT reportSQ

3. The SQR for PeopleSoft V8.49.15 form appears. Enter the following parameters:

Report name: E:PSOFTFS900sqrdddaudit.sqr
Data Source: FSDMO
Username: sa
Password: train

The FSDMO ODBC connection must be created for it to appear in the Data Source drop down list.

Parameters for SYSAUDIT report

4. The SQR for PeopleSoft V8.49.15 form appears. Enter the following parameters:

Report name: E:PSOFTFS900sqrsysaudit.sqr
Data Source: FSDMO
Username: sa
Password: train

The FSDMO ODBC connection must be created for it to appear in the Data Source drop down list.

5. To view the report, enter the following at the Command Prompt:

E:PSOFTFS900binsqrMSSBINWsqrwv.exe

PDF reports not appearing in browser

Posted by on February 8, 2009 Comments Off on PDF reports not appearing in browser

Problem:

After running a report in PeopleSoft with PDF output, when the output file is clicked in Process Monitor, a dialog box appears prompting you to save the PDF file to the hard drive. The expected behaviour is that the PDF report will appear in the browser window.

Solution:

1. In Internet Explorer, click the Tools menu and then click Internet Options. Click the Advanced tab. Then click Restore Defaults.

Alternatively, uncheck ‘Do not save encrypted pages to disk.

2. The digital certificates are incorrectly configured. Regenerate and setup the correct certificates.

(TRIGGER-1) Trigger defined in the Application Designer and not found in the Database

Posted by on February 7, 2009 No comments

Problem:

After cloning fsdev to fstst, DDDAUDIT was run. It showed the following error:

(TRIGGER-1) Trigger defined in the Application Designer and not found in the Database:
 Record Name Trigger Name
 --------------- ---------------
 CHARTFIELD1_TBL PSICHARTFIELD1_TBL
 CHARTFIELD1_TBL PSUCHARTFIELD1_TBL
 2 Total Rows

Solution:

In GLWEBAPP, launch Application Designer. Log on to FSTST (ensure FSTST ODBC Connection created).

(QUERY-22) Following Queries Were Created Without PUBLIC Access Query Name

Posted by on February 6, 2009 No comments

Problem:

After cloning fsdev to fstst, SYSAUDIT was run. It showed the following error:

(QUERY-22) Following Queries Were Created Without PUBLIC Access Query Name
 -------------------------------
 Oper ID
 -------------------------------
 FJBG_CALENDARS VP1
 FJBG_NAVIGATION VP1
 FJBG_SET_CONTROL_GROUP VP1
 FJBG_TIMESPANS VP1
 4 Total Rows

Solution:

Spoke to consultant (FB). He said that he created these queries and they were set to be private. Therefore, the error could be ignored.

(TREE-21) Tree Selector Control contains Tree name that is not defined in Tree Definition table

Posted by on February 6, 2009 No comments

Problem:

After cloning fsdev to fstst, SYSAUDIT was run. It showed the following error:

(TREE-21) Tree Selector Control contains Tree name that is not defined in Tree Definition table:
 Tree Name
 --------------------
 Set Id
 ------------
 Effect DT
 ------------
 Selector Number
 ----------
 ACCT_BY_LOB_DETAIL SHARE 01/01/1900 101
 1 Total Rows

Solution:

This tree was created by the consultant FB and he advised that it could be ignored.

Enterprise FSCM9.0 PeopleBooks Not Appearing

Posted by on February 5, 2009 No comments

Problem:

After installing Enterprise FSCM 9.0 PeopleBooks and bouncing PeopleBooks web server, they do not appear in the list of PeopleBooks.

Solution:

Enterprise FSCM 9.0 PeopleBooks installed to wrong directory. It should be installed to the htmldoc directory:
E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warhtmldoc