Update: You may find a more current version of this article in the PS Corner Wiki.
If there's a way to automate an unpleasant task, I'm always the first to do it. So when I ended up in a position where I had to do PeopleSoft migrations, it didn't take long before I had a migration batch script up and running. I thought I'd share my script, and maybe you can find a way to improve on it.
As you probably know, Application Designer has a command-line interface that allows you to migrate and build projects via the command line. You can also compare databases and import and export projects as files via the command line, but that's beyond what we're trying to accomplish here.
Here's the script:
And here's the contents of the registry entry file (RDMBuildSettings.reg) that it imports:
And here's how it all works:
I'll leave the scripting of batch objects like SQR's and Crystal to your imagination. I'm sure you can find plenty of internet resources on how to copy files from one directory to another, and how to write a script to FTP files to your UNIX server.
Comment from Chris Heller
written by Chris Heller, April 24, 2006
If there's a way to automate an unpleasant task, I'm always the first to do it. So when I ended up in a position where I had to do PeopleSoft migrations, it didn't take long before I had a migration batch script up and running. I thought I'd share my script, and maybe you can find a way to improve on it.
As you probably know, Application Designer has a command-line interface that allows you to migrate and build projects via the command line. You can also compare databases and import and export projects as files via the command line, but that's beyond what we're trying to accomplish here.
Here's the script:
rem Filename: MigrateProject.cmd
setlocal
set DBTYPE=ORACLE
set SOURCEUSERID=BRENT
set SOURCEPWD=mysecretpassword
set SOURCEDB=HDEV
set TARGETUSERID=BRENT
set TARGETPWD=mysecretpassword
set TARGETDB=HTST
set PROJECTNAME=%1
rem Copy Project
N:\HR8_9\bin\client\winx86\PSIDE.EXE -HIDE -PJC %PROJECTNAME% -CT %DBTYPE% -CD %SOURCEDB% -CO %SOURCEUSERID% -CP %SOURCEPWD% -TD %TARGETDB% -TO %TARGETUSERID% -TP %TARGETPWD% -QUIET -LF C:\TEMP\COPY.LOG -CL 150 -AF 1 -DDL 1
rem Build Project
regedit -s "C:\Documents and Settings\bmartin1\My Documents\Scripts\RDMBuildSettings.reg"
N:\HR8_9\bin\client\winx86\PSIDE.EXE -CT %DBTYPE% -CD %TARGETDB% -CO %TARGETUSERID% -CP %TARGETPWD% -PJB %PROJECTNAME% -HIDE -QUIET
:END
endlocal
And here's the contents of the registry entry file (RDMBuildSettings.reg) that it imports:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\PeopleSoft\PeopleTools\Release8.40]
[HKEY_CURRENT_USER\Software\PeopleSoft\PeopleTools\Release8.40\RDM Build Settings]
"CreateTables"=dword:00000001
"CreateIndexes"=dword:00000001
"CreateViews"=dword:00000001
"CreateTrigger"=dword:00000001
"AlterTables"=dword:00000001
"ExecuteOption"=dword:00000002
"LogErrors"=dword:00000002
"LogToScript"=dword:00000001
"LogToWindow"=dword:00000000
"LogSettings"=dword:00000000
"AlterDropOption"=dword:00000001
"AlterTruncateOption"=dword:00000001
"TableOption"=dword:00000002
"ViewOption"=dword:00000001
"IndexOption"=dword:00000003
"AlterAdds"=dword:00000001
"AlterChanges"=dword:00000001
"AlterRenames"=dword:00000001
"AlterDeletes"=dword:00000001
"OutputToSingleFile"=dword:00000000
"AlwaysOverwrite"=dword:00000001
"LogComments"=dword:00000000
"UnicodeScript"=dword:00000000
"AlterByTableRename"=dword:00000001
"ForceAlterOption"=dword:00000000
"LogFilename"="c:\\temp\\psbuild.log"
"OutputToSingleFilename"="c:\\temp\\PSBUILD.SQL"
"CreateTableFilename"="c:\\temp\\CreateTables.sql"
"CreateIndexFilename"="c:\\temp\\CreateIndexes.sql"
"CreateViewFilename"="c:\\temp\\CreateViews.sql"
"AlterTableFilename"="c:\\temp\\AlterTables.sql"
"CreateTriggerFilename"="c:\\temp\\CreateTriggers.sql"
And here's how it all works:
rem Filename: MigrateProject.cmd
setlocal
set DBTYPE=ORACLE
set SOURCEUSERID=BRENT
set SOURCEPWD=mysecretpassword
set SOURCEDB=HDEV
set TARGETUSERID=BRENT
set TARGETPWD=mysecretpassword
set TARGETDB=HTST
set PROJECTNAME=%1
This code essentially sets your database type, source database connection info, and your target database connection info. Notice the setlocal command on the first line. This will keep environment variable changes local to the script, so you don't leave them hanging around after the script completes.
rem Copy Project
N:\HR8_9\bin\client\winx86\PSIDE.EXE -HIDE -PJC %PROJECTNAME% -CT %DBTYPE% -CD %SOURCEDB% -CO %SOURCEUSERID% -CP %SOURCEPWD% -TD %TARGETDB% -TO %TARGETUSERID% -TP %TARGETPWD% -QUIET -LF C:\TEMP\COPY.LOG -CL 150 -AF 1 -DDL 1
This copies the project from the source database to the target database. The -HIDE and -QUIET flags are required for running app designer on the command line, otherwise app designer starts normally. CL sets the commit level to 150 objects. AF 1 directs app designer to retain the target audit flags, and DDL 1 directs app designer to retain the target DDL settings.
rem Build Project
regedit -s "RDMBuildSettings.reg"
N:\HR8_9\bin\client\winx86\PSIDE.EXE -CT %DBTYPE% -CD HQA -CO %TARGETUSERID% -CP %TARGETPWD% -PJB %PROJECTNAME% -HIDE -QUIET
:END
endlocal
This code segment creates the DDL necessary to build the objects. Since you can't really specify build settings on the command line, I use regedit to import the registry settings for the build options I want. In this case, it only creates SQL files (it doesn't execute them); it creates separate files for create table, alter table, create trigger, create index, and create view SQL; and puts it all in the C:\temp directory. I'm not crazy about this step because the correct registry entries can change between tools releases and it creates the potential to corrupt your registry. Unfortunately I don't know a better way to do it, so import registry entries at your own risk!
Next the script calls App Designer again with the directives to build the project. When it's complete, you should find your SQL scripts in the C:\temp directory. After reviewing, I'll either run them or send them to the DBA to run depending on the migration process.
I'll leave the scripting of batch objects like SQR's and Crystal to your imagination. I'm sure you can find plenty of internet resources on how to copy files from one directory to another, and how to write a script to FTP files to your UNIX server.
Trackback(0)
TrackBack URI for this entry
Comments (2)
Subscribe to this comment's feed
written by Chris Heller, April 24, 2006
Good writeup Brent.
I was just doing a little automation and was scratching my head about why the project wasn't building, but I wasn't getting the project built. Your post reminded me about the registry settings, which was the culprit.
The problem was coming from the fact that I was scripting the whole build process from refreshing the VMWare environment, checking the source code out, importing the project, building it, etc.
The problem was that refreshing the VMWare environment was taking me back to an environment where no builds had been done at all and so there wasn't even an RDM Build Settings key in the registry at all.
Which explains why it wasn't actually building anything :-)
I was just doing a little automation and was scratching my head about why the project wasn't building, but I wasn't getting the project built. Your post reminded me about the registry settings, which was the culprit.
The problem was coming from the fact that I was scripting the whole build process from refreshing the VMWare environment, checking the source code out, importing the project, building it, etc.
The problem was that refreshing the VMWare environment was taking me back to an environment where no builds had been done at all and so there wasn't even an RDM Build Settings key in the registry at all.
Which explains why it wasn't actually building anything :-)
-
- +0
-
-
Write comment
| < Prev | Next > |
|---|
Last Updated on Wednesday, 10 May 2006 19:36.
Speaking about a better way of importing registry entries, I think there is no better way than what you have stated. The obvious reason is that the internal code of App Designer, Change Assistant and Upgrade Assistant are the real drivers for these registry settings. We cannot obtain any version difference document for these internal codes - or registry settings.
For different Tools releases, we can set our desired Build settings though our Application Designer then export it and reuse it.
But there is another possible solution which is only theoritical - we could change the selected branch of the registry from a higher tools to a lower Tools, I think that PeopleSoft would have maintained backward compatibity. May be you could give it a shot!
Thanks