1 / 76

SX / TWL 4.1 for Windows Databases

SX / TWL 4.1 for Windows Databases. Installation and Upgrade Training. January 2005 presenter: Joe Baumgarten. Agenda. New Installs and prerequisites Directories Script changes Major Upgrades (4.0 to 4.1), possibly 4.3 if Progress 9.1E/OpenEdge 10 qualified TWL 4.1 for windows databases

murray
Download Presentation

SX / TWL 4.1 for Windows Databases

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SX / TWL 4.1 for Windows Databases Installation and Upgrade Training January 2005 presenter: Joe Baumgarten

  2. Agenda • New Installs and prerequisites • Directories • Script changes • Major Upgrades (4.0 to 4.1), possibly 4.3 if Progress 9.1E/OpenEdge 10 qualified • TWL 4.1 for windows databases • Code Pushes with TWL/SX CHUI separated • eSales Center • Code Patches • Schema Patch Minor Upgrades (4.2)

  3. New Installs of SX for Windows Databases NEW INSTALLS

  4. Windows DB New Installs Software Prerequisites: • Windows 2000 (SP3) / Windows Server 2003 • Progress 9.1D • Winzip • Adobe Acrobat • Anti-Virus software • Windows 2000 Resource Kit • Windows 2000 Support Tools • IIS may be required if eSales will be installed. Exchange Server may be required for Verisign and SSL (secure sockets layer) functionality in SX.enterprise.

  5. Windows DB New Installs Hardware Prerequisites: • 2Ghz Processors • 1 processor up to 35 users • 4 up to 140 users • 2.5 to 8 gig memory (35 to 140 users) • Raid Level 1 OS ( minimum 6 gig) • Raid Level 1 Temp (500 meg minimum) • Separate Drive: Paging (non raid partition min 500 meg) • Separate Drive (Raid 5 recommend): Data (min 8 gig) • Separate Drive (or Raid): After Imaging and Recovery

  6. Windows DB New Installs Operating System Prerequisites (from separate doc): • Install OS • partition raid arrays, • update windows to latest patch • Create the nxtadmin/dlcmgr user account • Increase event logs • Configure Windows Explorer • Configure Internet Explorer • Optimize Performance for Background Services • Configure Virtual Memory • Configure Startup and Recovery • Optimize for maximum throughput for network applications • Configure Indexing Services

  7. Questions on Requirements __________________________ __________________________ __________________________ __________________________ __________________________ __________________________ __________________________

  8. SX Windows DB New Install SX.Enterprise Information to gather: • Download the latest patch to %TEMP% • Environment Name • Database drive location • Backup drive location • Tape Device name • After Image Drive location • SMTP server, admin email from address • RXServer Poll Directory, User, password, mailto New to 4.1 • Scheduled Tasks Admin Username, password

  9. Add New Environment

  10. Windows DB Install • Run the install and enter information • If TWL installed at same time, you can disable compile until TWL install • Enter Path to Patch setup if installing 4.1.020 or downloaded patch (note may have issue, cd needs to be recut for tb#d600) • Finish the install

  11. Special Note on Multiple versions of Progress • If you have both Progress 9.1D and 9.1E, installed you may see selection screen • Install to different program Groups (e.g. Progress 9.1D and Progress 9.1E) see Solution ID P10888 • If any combination of 9.1D, 9.1E, OpenEdge 10.0A • Adminserver default udp Port 20931 may conflict (and adminport) • Nameserver default udp Port 5162 may conflict • Recommend changing adminserver to 7180 (adminport 7181) • NS1 to 7182 • This can be done during new SX install for alternate version of Progress

  12. Special Note on Multiple versions of Progress • Uses method to change registry in adminservice. See: ID: P10465 Title: "How To Configure Multiple Versions of AdminServer To Be Run Concurrently on Windows“ • ID: 18919Title: "How to Change the Port Number When the 9.x Admin Server is Running On?" • See: P45120 Title: "Instances in Progress Explorer get lost when using multi Progress versions"

  13. Special Note on Multiple versions of Progress • Progress 9.1D0980 patch may overwrite registry hack and properties files. • Special 91D0980 patch can be obtained from infor that will save adminserver configuration and apply the sub-patch 80 automatically.

  14. Post Install Steps • Apply the SX latest patch (if not done during initial install) • Insure compile of SX code and push out • License the Database in SASA for customer • Test nxtall.start and nxtall .shut scripts to be sure report managers start • Verify everything works and do full backup at soonest time.. • Check Scheduled tasks for backups, aisave • Install Terminal Server Client (full push) • Install GUI network clients, if necessary

  15. Creating RPTMGR queues • Rptmgr –add –queue myqueue –num 1 • Create the queue in SX

  16. Questions on the Initial Install __________________________ __________________________ __________________________ __________________________ __________________________ __________________________ __________________________

  17. Directories • Appsrv - library • Character – pf nxtprint, runtime • Rd • Bin - scripts • Install - programs • Lib – chui library – nxt.pl • Log • Opsys – pf’s • Shp - clippership • Tmp • Rptmgr – pf nxtprint, runtime • Staging • Character • I • P • Rptmgr-r • test/ • Rptmgr – pushes nxt.lib ( used to be standard in 4.0)

  18. Windows Database Directories • C:\nxt\rd\bin - Scripts (not to be modified) • C:\nxt\rd\opsys contains CHUI pf files used for chui sessions, logins, editor, and report manager, clippership sessions • C:\nxt\rd\opsys\admin\adminuser.pf protected directory that contains user/pass for secured database (disallow blank user) • C:\nxt\rd\log – log output

  19. Windows Database Scripts \nxt\rd\bin • Command Prompt calls nxt.env.bat • Nxt.env.bat retrieves all the variables used to tailor scripts for the environment, such as default TAPEDEV, directory locations, etc… • Follow unix counterparts, except they take some command line options to modify behavior • Use command: SCRIPTLIST for complete list • Use –help option for script specific help

  20. Windows Database Scripts new to 4.1 Changes to 4.1 (and 4.0.072 and higher): Enhance commands to work with TWL • Tapedev now takes filename for ntbackup, various backup.tape.bat enhancements, to take directory list • Backup.data/backup.full – new –install to create scheduled task and override tapedev • E.g backup.full –install -user myuser –pass mypass • Backup.db, Restore.db and rollforward.ai fixes

  21. Windows Database Scripts new to 4.1 • Addition of SXSERVICE.BAT in 4.1 to support RPTMGR queues and OpenEdge 10 (no procontrol)

  22. Windows Database Scripts new to 4.1 Aimage.BAT new, –disable, -enable etc.. • Aimage.query, show if disabled • Aimage.archive.bat – new –install for scheduled task for saving every 15 min…fix for db down • Chui.bat, -rcode <path> • RECOMPILE.BAT to support TWL CHUI compile

  23. Windows Database Scripts new to 4.1 • Minor DBLOAD enhancements/fixes, elapsed time, db security, migrations

  24. Windows Database Scripts new to 4.1 • Nxtall.shut, various performance/shut speed issues with TWL, and add –restart and –admin • Showuser/shutuser scripts, new to TWL, moved logic from rptmgr to these and sxservice.bat, twlservice.bat • E.g. shutuser sx 100sys • -pid <pid> • Nxt.env.bat, fixes for tapedev, esales (patch 4.0.072)

  25. DUMP / LOAD • Uses environment variable %DUMPDIR%, defaults to \DUMP directory on backup disk drive • Dbdump –reload (binary by default) • Confirms recreation of database • Can override with –ascii and –cono 1 • -silent avoid prompting • -newcopy preserves existing db

  26. DBLOAD migration • Uses environment variable DUMPDIR (as previously set or backup drive \DUMP) • Dbload (looks for .d or .bd and chooses method) • assumes .st and nxt.df exists in \DUMP (df name matches dbname) • -newcopy – preserves existing db in a PRIOR directory • -silent avoid prompts • AI is enabled if previously enabled, otherwise use aimage –enable • Summary Verification: Records verified [225845 records] 10 Min, 57 Sec Dump/Load 16 Min, 11 Sec Overall

  27. Questions on Scripts __________________________ __________________________ __________________________ __________________________ __________________________ __________________________ __________________________

  28. 4.1 Upgrades for windows db Upgrades

  29. SX Windows DB Upgrade Prompts • Always upgrade a test environment first • Select environment • Confirm upgrade to 4.1

  30. Upgrade Environment

  31. SX Windows DB Upgrade Prompts • Confirm Progress version • Confirm database ports/locations/tapedev • Check Database version, prompt if necessary • Convert DB, (e.g. proutil conv910) if necessary. Note: we don’t officially support OpenEdge10 with 4.1 release, but future versions may • Schema Comparison for custom • Create upgradedelta.df for upgrade in db directory

  32. UpgradeDelta.df (and customdelta.df) • Similar steps are done in schema patches for windows/unix databases (e.g. 4.2) • Create customdelta of customized schema by comparing database with the template for the older version. • Preserves any initial values or description/help/audit triggers on standard tables • Apply CustomDelta.df to new template for 4.1 (if nonsupported Progress 10.0A create dynamically) • Compare newly created template with custom changes at new version to the current database and create UpgradeDelta.df to be used later.

  33. Upgrade Options

  34. Upgrade Options • Apply database upgrade Delta (also applies .b) • Run interactive conversion (.ant) • Run non-interactive conversions (.a) • Set DB Version • No-Integrity

  35. .ant’s from 4.0 to 4.1 .ant’s

  36. .a’s from 4.0 to 4.1 .a’s

  37. Additional Upgrade Confirmations • Confirm Mail Server, and user sending STMP mail from for BLAT • Default Report Managers • Clippership poller • After Image Path • Backup during upgrade if AI selected • New to 4.1 – Windows Task Scheduler user/pass • Installation Options – Compile after install • If TWL also, you may want to turn off SX to save time • Patch install path (note that downloadable patch may have issue with current 4.1 cd)

  38. Upgrade Processing • Confirm Start of upgrade

  39. Automatic Upgrade Processing • Shutdown Adminserver • Disable AI • Disable Report Manager from starting • Run before upgrade programs (.b) • Load Upgradedelta.df • Confirm schema after upgrade • Run After upgrade programs (.ant and .a) • Re-enable AI • Install conmgr, ubroker properties, procontrol report managers, task scheduler tasks, etc.., copy baseline 4.1 code

  40. Post Upgrade Steps • Finish the install, allow compiles to finish • If TWL is being installed/upgrade proceed with TWL upgrades to compile code • Insure code is pushed out • Run CONV programs per README • Re-enable report manager • Rptmgr –enable • Verify everything works and do full backup at soonest time.. • Check Scheduled tasks for backups, aisave

  41. Questions on Upgrades __________________________ __________________________ __________________________ __________________________ __________________________ __________________________ __________________________

  42. TWL 4.1 ( and TWL 4.0.072) New TWL for Windows Database

  43. Select Windows environment to Add TWL to

  44. TWL New Install Options • Confirm Database Ports and locations for TWL, similar to SX • Confirm AI option, (defaults same as SX) • Confirm 1 Gig database • Confirm AI locations (defaults same as SX) • Confirm TWL install directory (TWL<env>) • Compile after install will Compile SX too • TWL Online compiles after CHUI/SX compiles • Finish install and perform post installation in doc

  45. TWL Script changes for Windows Database • Twlservice.bat, twlservice.start, twlservice.shut, twlservice.query • Twlsend • Twlrcv • Twlrcvpack • Autodrop • Twlall.start, twlall.shut • Twlrf, bothe, entrf, ibcrf, editors and logins for chui • Eod1, eod2 – end of day , called by twlclean.bat called by rdclean

  46. Questions on TWL New Installs __________________________ __________________________ __________________________ __________________________ __________________________ __________________________ __________________________

  47. eSales Center Installing eSales Center

  48. eSales Center Directories/Host Make sure adminserver / environments may be shut down!

  49. eSales Environment and Options

  50. eSales Configuration

More Related