Documente Academic
Documente Profesional
Documente Cultură
TECHNICAL BRIEF
Contents
Abstract .......................................................................................................................................................................... 2
Introduction ................................................................................................................................................................... 3
Formatting Notes ......................................................................................................................................................... 3
About the PeopleSoft Application Engine .................................................................................................................. 4
What is a PeopleSoft Enterprise Application Engine? ................................................................................................. 4
Application Engine Structure ....................................................................................................................................... 4
Example Application Engine Program ......................................................................................................................... 5
Creating a Post-Migration Step .................................................................................................................................... 6
Using Command-Line Parameters .............................................................................................................................. 6
Storing Parameters in Stat ....................................................................................................................................... 6
Creating the Post-Migration Step ................................................................................................................................ 7
Editing the Post-Migration Step ................................................................................................................................... 8
Its All in the Interpretation ........................................................................................................................................... 9
Lets Take It for a Spin ................................................................................................................................................ 10
About the Author ......................................................................................................................................................... 12
TECHNICAL BRIEF
Abstract
This technical brief is written for Stat administrators of PeopleSoft ERP systems. It explains how to create and launch
a Stat post-migration step that will run a PeopleSoft application engine process when that process is migrated from
one environment to another.
TECHNICAL BRIEF
Introduction
This technical brief is written for Stat administrators of PeopleSoft ERP systems. It explains how to create and launch
a Stat post-migration step that will run a PeopleSoft application engine process when that process is migrated from
one environment to another.
For some, these procedures can be a bit convoluted. However, we are seasoned PeopleSoft DBAs and PeopleSoft
administrators. Remember: We are the courageous! We are the valiant! We are the Stat Administrators!
Formatting Notes
In this document, local Stat or other application screen menus are displayed in the following format:
Menu Name > Menu Name > Menu Name > Target Menu Item
System output, keyboard input, and screen-related text are displayed in the Courier New font style.
TECHNICAL BRIEF
TECHNICAL BRIEF
TECHNICAL BRIEF
TECHNICAL BRIEF
TECHNICAL BRIEF
Outlined in purple is the PS_SERVER_CFG. If you do not have the system variable PS_SERVER_CFG value set on
your environment, you will want to set that variable at runtime.
We set up a PSAE Stat parameter (in yellow) to hold the run location of the PS app engine program (psae.exe).
When we select it from the list above and double-click it, Stat places the parameter into our post-migration step
command as %%PSAE%%. The double percent signs tell Stat that these are variables that need to be interpreted at runtime.
The last command-line variable passed (outlined in blue) is the app engine debug parameter. I set it to yes in my
stored parameter, so it will be equal to: AEDBUG = -DEBUG Y
TECHNICAL BRIEF
The purple text is hardcoded and will appear every time this call is run; it is the Set PS_SERVER_CFG call.
The yellow PSAE value is interpreted to the full path of P:\PT8.52\bin\client\win86\PSAE.exe.
The orange AEDBTYPE value is interpreted to the database type value of -CT ORACLE.
The blue AEDBUG value is interpreted to the app engine debug Y/N value of -DEBUG Y
On the last line in Figure 6 above, you will notice that the -CD parameter is set to <Null>. If you look back at the
command entry, that value is set as text -CD and then %%TARGET_DB_NAME%%. If this was being called at runtime,
and we were migrating this to our HRPROD environment, then Stat would interpret is as -CD HRPRD.
TECHNICAL BRIEF
10
TECHNICAL BRIEF
For our valid run, we will replace the parameters as required and let the app engine execute. All values will be passed
out to the psae executable and the app engine will be executed within its own command shell window.
The following image shows the successful execution of our app engine program:
11
TECHNICAL BRIEF
12
TECHNICAL BRIEF
Trademarks
Quest, Quest Software, the Quest Software logo, AccessManager, ActiveRoles, Aelita, Akonix, AppAssure, Benchmark Factory, Big Brother,
BridgeAccess, BridgeAutoEscalate, BridgeSearch, BridgeTrak, BusinessInsight, ChangeAuditor, ChangeManager, Defender,
DeployDirector, Desktop Authority, DirectoryAnalyzer, DirectoryTroubleshooter, DS Analyzer, DS Expert, Foglight, GPOADmin, Help Desk
Authority, Imceda, IntelliProfile, InTrust, Invirtus, iToken, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, LogADmin,
MessageStats, Monosphere, MultSess, NBSpool, NetBase, NetControl, Npulse, NetPro, PassGo, PerformaSure, Point,Click,Done!,
PowerGUI, Quest Central, Quest vToolkit, Quest vWorkSpace, ReportADmin, RestoreADmin, ScriptLogic, Security Lifecycle Map,
SelfServiceADmin, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL Navigator, SQL Watch, SQLab, Stat, StealthCollect, Storage Horizon,
Tag and Follow, Toad, T.O.A.D., Toad World, vAutomator, vControl, vConverter, vFoglight, vOptimizer, vRanger, Vintela, Virtual DBA,
VizionCore, Vizioncore vAutomation Suite, Vizioncore vBackup, Vizioncore vEssentials, Vizioncore vMigrator, Vizioncore vReplicator,
WebDefender, Webthority, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of
America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.
UpdatedMAY, 2012
13
TECHNICAL BRIEF
If you are located outside North America, you can find your local office information on our Web site.
EMAIL
sales@quest.com
14