Monthly Archives: February 2009

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

PIA Installation on IBM WebSphere Hangs on 20%

Posted by on February 4, 2009 Comments Off on PIA Installation on IBM WebSphere Hangs on 20%

PIA Installation on IBM WebSphere Hangs on 20%

Problem:

When installing new PIA on IBM WebSphere, the installation hangs for several minutes at 20%

Solution:

Installation takes a long time to complete. If the timeout is not long enough, the installation may fail. (Applying MP5 appears to have resolved this). Else, manually increase the timeout.

Cloning PeopleSoft Instance

Posted by on February 3, 2009 Comments Off on Cloning PeopleSoft Instance

Here are the steps to clone the PeopleSoft instance:

1. Backup the database (FSDEV) and restore it to another name (FSTST)
2. Clear the GUID field in the PSOPTIONS table in FSTST
3. Set up ODBC connection for FSTST
4. Map PS_HOME network drive and run Configuration Manager to set up shortcuts, PS/nVision path names
5. Create new application server domain for FSTST
6. Create new batch server for FSTST
7. Stop web server and setup new PIA for FSTST
8. Start application server, batch server, web server and log on to FSTST.

[amazon asin=0071664939&template=iframe image&chan=default]     [amazon asin=1430237074&template=iframe image&chan=default]     [amazon asin=0071787925&template=iframe image&chan=default]

Installing BEA WebLogic Windows Service

Posted by on February 3, 2009 Comments Off on Installing BEA WebLogic Windows Service

Problem:

How can PeopleSoft profiles (fsdmo) that use BEA WebLogic as the web server be installed as a Windows Service?

Solution:

Navigate to the WebLogic domain directory (E:PSOFTFS900webservfsdmobin) and run installNTservice.cmd .

To uninstall, use UninstallNTservice.cmd :

Cd /d E:PSOFTFS900webservfsdmobin
 UninstallNTservice.cmd PIA
 UninstallNTservice.cmd WebLogicAdmin
E:PSOFTFS900webservfsdmobin>UninstallNTservice.cmd PIA
fsdmo-PIA removed.
 Press any key to continue . . .
E:PSOFTFS900webservfsdmobin>
E:PSOFTFS900webservfsdmobin>UninstallNTservice.cmd WebLogicAdmin
fsdmo-WebLogicAdmin removed.
 Press any key to continue . . .
 E:PSOFTFS900webservfsdmobin>

Setting Up IBM WebSphere as a Service

Posted by on February 2, 2009 Comments Off on Setting Up IBM WebSphere as a Service

Problem:

If the user that starts the IBM WebSphere web server logs off the system, the web server is shut down. A Windows service must be created to ensure that the web service(s) remain running.

Solution:

At Command Prompt, issue the following commands:

E:
 cd E:IBMWebSphereAppServerbin
 WASService.exe -add fsdev -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservfsdev -logFile E:IBMWebSphereAppServerlogsstartNodefsdev.log -restart true -startType automatic
WASService.exe -add fsdmo -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservPIA_fsdmo -logFile E:IBMWebSphereAppServerlogsstartNodefsdmo.log -restart true -startType automatic
E:IBMWebSphereAppServerbin>cd E:IBMWebSphereAppServerbin
E:IBMWebSphereAppServerbin>WASService.exe -add fsdev -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservfsdev -logFile E:IBMWebSphereAppServerlogsstartNodefsdev.log -restart true –startType automatic
 Adding Service: fsdev
 Config Root: E:PSOFTFS900webservfsdevconfig
 Server Name: server1
 Profile Path: E:PSOFTFS900webservfsdev
 Was Home: E:IBMWebSphereAppServer
 Start Args:
 Restart: 1
 IBM WebSphere Application Server V6.1 - fsdev service successfully added.
 E:IBMWebSphereAppServerbin>
The “IBM WebSphere Application Server V6.1 – fsdev” service is created.
Note that the log file is E:IBMWebSphereAppServerlogsstartNodefsdev.log
E:>E:
 E:>cd E:IBMWebSphereAppServerbin
E:IBMWebSphereAppServerbin>WASService.exe -add tramdmo -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservPIA_tramdmo -logFile E:IBMWebSphereAppServerlogsstartNodetramdmo.log -restart true -startType automatic
 Adding Service: tramdmo
 Config Root: E:PSOFTFS900webservPIA_tramdmoconfig
 Server Name: server1
 Profile Path: E:PSOFTFS900webservPIA_tramdmo
 Was Home: E:IBMWebSphereAppServer
 Start Args:
 Restart: 1
 IBM WebSphere Application Server V6.1 - tramdmo service successfully added.
To remove the service:
 cd E:IBMWebSphereAppServerbin
 WASService.exe -remove tramdmo
E:>E:
 E:>cd E:IBMWebSphereAppServerbin
E:IBMWebSphereAppServerbin>WASService.exe -add peoplebooks -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservPSOL_fsdmo -logFile E:IBMWebSphereAppServerlogsstartNodepeoplebooks.log -restart true -startType automatic
Adding Service: peoplebooks
 Config Root: E:PSOFTFS900webservPSOL_fsdmoconfig
 Server Name: server1
 Profile Path: E:PSOFTFS900webservPSOL_fsdmo
 Was Home: E:IBMWebSphereAppServer
 Start Args:
 Restart: 1
 IBM WebSphere Application Server V6.1 - peoplebooks service successfully added.
 E:IBMWebSphereAppServerbin>
To remove the service:
 cd E:IBMWebSphereAppServerbin
 WASService.exe -remove peoplebooks

Reference:
http://handly.blogspot.com/2008/05/setting-up-websphere-61-cluster-to.html

Setting up the WebSphere Node Manager as a Windows service

First, you need to set up the Node Manager on each physical server to run as a service and restart after a reboot:

Open a Command Window and go to the ..IBMWebSphereAppServerbin directory
Type in the following command (adjusted for your install paths):

WASService -add “IBM WebSphere Node Agent” -servername nodeagent -profilePath D:IBMWebSphereAppServerprofilesAppSrv01 -wasHome D:IBMWebsphereAppserver -logFile D:IBMWebSphereAppServerprofilesAppSrv01logsnodeagentstartNode.log -logRoot D:IBMWebSphereAppServerprofilesAppSrv01logsnodeagent -restart true -startType automatic