Skip to content

PS FSCM two path Upgrade 8.4 –>9.0 –>9.1

Advertisements

Expense

USA Inc Income statement

How to restart Application Server process(PSREN,PSAPPSERV etc.,) with out restarting the Application server

The below steps will help to restart the specific process of application server if we made change to process and user logged in to the production system.The below option will reboot only the specific PeopleSoft application server process eg., PSRENSERV,PSAPPSERV etc while the application server is up and running….

PeopleSoft Domain Administration
Domain Name: PSXX89

1) Boot this domain
2) Domain shutdown menu
3) Domain status menu
4) Configure this domain
5) TUXEDO command line (tmadmin)
6) Edit configuration/log files menu
7) Messaging Server Administration menu
8) Purge Cache
9) Preload File Cache
10) Clean IPC resources of this domain
q) Quit

Command to execute (1-10, q) : 3
PeopleSoft Domain Status Menu
Domain Name: PSXX89

1) Server status
2) Client status
3) Queue status
q) Quit

Command to execute (1-3, q) [q]: 1
Loading command line administration utility …
tmadmin – Copyright (c) 1996-1999 BEA Systems, Inc.
Portions * Copyright 1986-1997 RSA Data Security, Inc.
All Rights Reserved.
Distributed under license by BEA Systems, Inc.
Tuxedo is a registered trademark.

Prog Name Queue Name Grp Name ID RqDone Load Done Current Service

———
PSSUBDSP SUBDQ_dflt PUBSUB 300 0 0 ( IDLE )
BBL 63085 chqpvuu+ 0 7649 382450 ( IDLE )
PSAPPSRV APPQ APPSRV 1 84 4200 ( IDLE )
PSANALYTICSRV 00080.00001 ANALYTI+ 1 0 0 ( IDLE )
PSSUBHND SUBHQ_dflt PUBSUB 301 0 0 ( IDLE )
PSMONITORSRV MONITOR MONITOR 1 0 0 ( IDLE )
PSWATCHSRV WATCH WATCH 1 0 0 ( IDLE )
PSAPPSRV APPQ APPSRV 2 81 4050 ( IDLE )
PSANALYTICSRV 00080.00002 ANALYTI+ 2 0 0 ( IDLE )
PSANALYTICSRV 00080.00003 ANALYTI+ 3 0 0 ( IDLE )
JREPSVR 00094.00250 JREPGRP 250 11 550 ( IDLE )
PSQRYSRV QRYQ APPSRV 70 0 0 ( IDLE )
PSQRYSRV QRYQ APPSRV 71 0 0 ( IDLE )
JSL 00095.00200 JSLGRP 200 0 0 ( IDLE )
PSPUBDSP PUBDQ_dflt PUBSUB 200 0 0 ( IDLE )
PSPUBHND PUBHQ_dflt PUBSUB 201 0 0 ( IDLE )
PSBRKDSP BRKDQ_dflt PUBSUB 100 0 0 ( IDLE )
PSSAMSRV SAMQ APPSRV 100 0 0 ( IDLE )
PSRENSRV RENQ1 RENGRP 101 0 0 ( IDLE )
PSBRKHND BRKHQ_dflt PUBSUB 101 0 0 ( IDLE )

Go into server status and you will see the PSRENSRV line. he third column and the value of the Group process.For example if we need to bounce PSREN server only then the group is “RENGRP”. Take that value and do the following:

PeopleSoft Domain Administration
Domain Name: PSXX89

1) Boot this domain
2) Domain shutdown menu
3) Domain status menu
4) Configure this domain
5) TUXEDO command line (tmadmin)
6) Edit configuration/log files menu
7) Messaging Server Administration menu
8) Purge Cache
9) Preload File Cache
10) Clean IPC resources of this domain
q) Quit

Command to execute (1-10, q) : 5
Loading command line administration utility …
tmadmin – Copyright (c) 1996-1999 BEA Systems, Inc.
Portions * Copyright 1986-1997 RSA Data Security, Inc.
All Rights Reserved.
Distributed under license by BEA Systems, Inc.
Tuxedo is a registered trademark.

shutdown -g RENGRP

Shutting down server processes …

Server Id = 101 Group Id = RENGRP Machine = xxxxxx: shutdown succeeded
1 process stopped.

boot -g RENGRP
INFO: BEA Tuxedo, Version 9.1, 64-bit, Patch Level 036
INFO: Serial #: 650522264137-2065448083901, Expiration NONE, Maxusers 1000000
INFO: Licensed to: Oracle-Peoplesoft-ISV

Booting server processes …

exec PSRENSRV -A — -C psappsrv.cfg -D PSXX89 -S PSRENSRV :
process id=778302 … Started.
1 process started.

PSUNX process scheduler redirect to look for cobols in a non-default location and RCCBL remote call

You can have cobols being looked at different directory on Unix by modifying the following parameters in the following files, then clear caches and restart the process scheduler and the application server.

A) For the process scheduler
————————————

1 ) psprcs.cfg
CBLBIN=%PS_HOME%/CBLBIN%PS_COBOLTYPE%
if the CBLBIN does not exist in the psprcs.cfg , simply you can add this parameter

2) psprcsrv.ubx
{UNIX}
COBPATH={$PS_HOME}/cblbin

3) Clear cache and restart the process scheduler

B) For the Application server to run the remote cobol

——————————————————————-
1) psappsrv.cfg
; UNIX:
RCCBL PRDBIN=%PS_HOME%/cblbin

2) psappsrv.ubx
{UNIX}
COBPATH={$PS_HOME}/cblbin

3) Restart application server.

PeopleSoft Installaton script order for new environment creation

CHANGE AND ON SCRIPTS createdb10.sql, rollback.sql,epddl.sql,ptddlupg.sql,ptddl.sql,utlspace.sql ,ts841.sql TO THE APPROPRIATE VALUES FOR  DATABASE STANDARD

All the scripts will be available on PS_HOME\scripts\NT after the Peoplesoft application installation
1)createdb10.sql– creates database (Change the database name and file locatoin)
2)rollback.sql — created rollback segnemt .
3)epddl.sql — Creates PeopleSoft metadata tools tablespace and PS application data tablespace (Change the datafiles location in the script for server standard)
4)ptddlupg.sql — Creates additional metadata tools tablespace.Ignore error tablespace already exists (Change the datafiles location in the script)
5)ptddl.sql — Creates additional metadata tools tablespace.Ignore error tablespace already exists (Change the datafiles location in the script)
6)utlspace.sql — Creates temp tables and Runs catalog,cataproc,catablock for loading oracle metadata ( Change datafiles location and script path)
7)ts841.sql — Creates additional metadata tools tablespace.Ignore error tablespace already exists (Change the datafiles location in the script)
8)dbowner.sql — creates user PS and PSDBOWNER table/synonym (change oracle system password in script to connect)
9)connect.sql — creates user people

10)psrole.sql — creates two roles PSUSER and PSADMIN

11)psadmin.sql — Enter user name as “sysadm” and password “sysadm” when prompts. This script also runs catdbsyn/pupbld (change oracle system password in script to connect)

12)upstats.sql — runs the DB statistics after data load from data mover

Then load the data from datamover

COBOL custom path compilation different from PS HOME

Create a custom directory called “TEST”.Copy all the cobol source code to to this directory and also copy the setup folder to this TEST directory.Follow the below steps to generate the .gnt executables in the custom target path from custom souce path

C:\Documents and Settings\svc_psoft>set PS_HOME=d:\psoft\TEST

C:\Documents and Settings\svc_psoft>set path=D:\psoft\TEST\src\cbl\win32;%path%

C:\Documents and Settings\svc_psoft>set COBROOT=”D:\Program Files\Micro Focus\Net Express 5.0\Base”

C:\Documents and Settings\svc_psoft>d:

D:\>cd %PS_HOME%\setup

D:\pt849gbl\FINGRPT\setup>cblbld c: \temp

Commands to test COBOL server express

$PS_HOME/bin> ./ptpdbtst
$PS_HOME/bin> cobrun
$PS_HOME/bin> cob -v
$PS_HOME/bin> cob -V
$PS_HOME/bin> ls -l PSRUN*

Oracle cold backup database refresh

1.  Prepare controlfile creation script.  This can be done by
alter database backup controlfile to trace as '/export/home/oracle/ctlfile.sql';
2.  View the edit ctlfile.sql, so that it should contain the following
CREATE CONTROLFILE SET DATABASE "UATDB" RESETLOGS NOARCHIVELOG
  MAXLOGFILES 16
  MAXLOGMEMBERS 3
  MAXDATAFILES 100
  MAXINSTANCES 1
  MAXLOGHISTORY 453
LOGFILE
  GROUP 1 '/u01/oradata/UATDB/redo01.log' SIZE 200M,
  GROUP 2 '/u02/oradata/UATDB/redo02.log' SIZE 200M,
  GROUP 3 '/u03/oradata/UATDB/redo03.log' SIZE 200M
-- STANDBY LOGFILE
DATAFILE
  '/u01/oradata/UATDB/system01.dbf',
  '/u01/oradata/UATDB/undotbs01.dbf',
  '/u01/oradata/UATDB/users01.dbf',
  '/u01/oradata/UATDB/data01.dbf',
  '/u01/oradata/UATDB/tools01.dbf',
  '/u01/oradata/UATDB/perfstat01.dbf',
  '/u01/oradata/UATDB/sysaux01.dbf'
CHARACTER SET WE8ISO8859P1
;
3. Gernerate script to create TEMP tablespace
set long 2000
select DBMS_METADATA.GET_DDL('TABLESPACE','TEMP') from dual;
4. Shutdown UATDB cleanly
shutdown immediate
5. Copy the cold backup files from production to UAT box.
6. Start the database in nomount state

startup nomount

7. Run the create control file script
@/export/home/oracle/ctlfile.sql
8. Open the database with resetlogs
alter database open resetlogs;
9. Create temp tablespace from the script generated from step 3:
CREATE TEMPORARY TABLESPACE "TEMP1" TEMPFILE
'/u01/oradata/UATDB/TEMP01.dbf' SIZE 5242880000
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576

PeopleSoft database refresh steps

Below are steps can we followed for pre and post refresh of PeopleSoft application environment.Please also  copy the SQR,COBOL,Crystal for file object refresh.

  1. Export any security that you need to preserve from the target database to a flat file. Data Mover is a nice tool to use for this since you can qualify each table with a list of operator ID’s to export. The tables you should consider exporting for specific users are PSOPRDEFN, PSOPRALIAS, PSROLEUSER, PSUSERATTR, PSUSEREMAIL, PSUSERPRSNLOPTN, PS_ROLEXLATOPR and PS_RTE_CNTL_RUSER.
  2. Stop the target application environment, including application servers and process schedulers. Stopping the web server is optional since it doesn’t connect directly to the database. Be sure to clear cache.
  3. Overlay the target database with a recent backup of the Production database. The exact process will differ for your database platform, but your DBA should be able to do this with minimal direction.
  4. After the database comes back on-line, set DBNAME in PSDBOWNER back to the target database name.
  5. Set GUID to ‘ ‘ in the PSOPTIONS table. This will cause PeopleSoft to generate a new GUID so that change assistant can track it separately from the source database.
  6. Delete the data from the reporting tables, process scheduler tables and application messaging tables since this data isn’t relevant in the target database. Run prcsclr.dms, rptclr.dms and appmsgpurgeall.dms. In addition, I also delete from the report manager tables PSRF_RATTR_TBL; PSRF_RSCRTY_TBL; PSRF_RINFO_TBL; and delete from PSRF_FINFO_TBL where PSRF_PRNT_FLDR_ID <> 0;
  7. If you have a script to reset everyone’s e-mail address to a pre-defined value so that workflow messages from the Test environment don’t get sent to real users, run it now. It should update the PSUSEREMAIL and PS_ROLEXLATOPR tables.
  8. Log on to the target database with data mover and run the following command to set the SYSADM password and any other back to it’s pre-refreshed value:
    — Author: Brent Martin, ERP Associates Inc.
    — Date: February 10, 2006
    — Purpose: Reset application passwords and purge PeopleTools tables after a database refresh so that
    — the application can be started with minimal reconfiguration.
    — Compatibility: This works with PeopleTools 8.4x releases
    — Notice: This script modifies data in your PeopleSoft database. It changes account passwords, and
    — it deletes data from process scheduler, report repository and integration broker tables.
    — It as provided for reference purposes only. Use it at your own risk.

    set log c:\temp\dbrefresh.log;

    — Change Access Password (SYSADM)
    CHANGE_ACCESS_PASSWORD SYSADM1 CHANGEME1;

    — Change Application Password (PSAPPS)
    update psoprdefn set OPERPSWD = ‘changeme1’, encrypted = 0 where oprid = ‘PSAPPS’;
    encrypt_password PSAPPS;

    — Set GUID to blank so PSEMAgent and Change Assistant doesn’t get confused
    update psoptions set guid = ‘ ‘;

    — Purge Process Scheduler
    RUN h:\fdmo881\scripts\PRCSCLR.DMS;

    — Purge Report Repository Tables
    RUN h:\fdmo881\scripts\RPTCLR.DMS;

    — Purge Application Messaging RUN h:\fdmo881\scripts\APPMSGPURGEALL.DMS;

  9. Import the security that you exported in step 1.
  10. While you’re in data mover, change the user passwords that are configured in your application server, process scheduler, and integration broker configurations back to the pre-refresh values:
    update psoprdefn set OPERPSWD = ‘devpswd’, encrypted = 0 where oprid = (‘PSAPPS’);
    encrypt_password PSAPPS;
    update psoprdefn set OPERPSWD = ‘devpswd’, encrypted = 0 where oprid = (‘PTWEBSERVER’);
    encrypt_password PTWEBSERVER;
  11. Clear application server, web server and process scheduler cache if you haven’t already done it. Start the target application environment.
  12. Log on through the web front end.
  13. Update the Report Node configuration and verify your Process Scheduler Servers are using the correct configuration. Make any Web Profile changes if needed.
  14. Navigate to PeopleTools > Utilities > Options and update the database name and description.
  15. Change password rules as appropriate for a development environment.
  16. Change your default local node if it should be named differently than the default local node from the source database. If it’s not named differently, you may be at risk for a single sign-on vulnerability.
  17. Reconfigure attachment servers (if used)
  18. Reconfigure REN servers and clusters if the application server didn’t configure it correctly at startup.
  19. Make sure you copy all of the batch objects (SQR’s, Crystal Reports, COBOL programs, etc.) from your source to your target environment to keep the environment in synch. Don’t forget to do this on both UNIX and Windows servers.
  20. Perform some sanity checks to make sure the environment is behaving itself before you let users back into it. At a minimum you should verify you can log on and run a report. Verify the report runs to completion, posts, and allows you to view the report without having to sign in a second time.