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

SX / TWL 4.1 for Windows DatabasesInstallation 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 Code Pushes with TWL/SX CHUI separated eSales Center Code Patches Schema Patch Minor Upgrades (4.2)

New Installs of SX for Windows Databases

NEW INSTALLS

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.


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


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

Questions on Requirements

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

SX Windows DB New Install

SX.EnterpriseInformation 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, mailtoNew to 4.1 Scheduled Tasks Admin Username, password

Add New Environment

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

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


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"


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.

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

Creating RPTMGR queues

Rptmgr –add –queue myqueue –num 1 Create the

queue in SX

Questions on the Initial Install

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

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)

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

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

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


Addition of SXSERVICE.BAT in 4.1 to support RPTMGR queues and OpenEdge 10 (no procontrol)


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


Minor DBLOAD enhancements/fixes, elapsed time, db security, migrations


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.batE.g. shutuser sx 100sys -pid <pid>

Nxt.env.bat, fixes for tapedev, esales (patch 4.0.072)

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

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

Questions on Scripts

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

4.1 Upgrades for windows db

Upgrades

SX Windows DB Upgrade Prompts

Always upgrade a test environment first Select environment Confirm upgrade to 4.1

Upgrade Environment

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

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.

Upgrade Options

Upgrade Options

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

.ant’s from 4.0 to 4.1

.ant’s

.a’s from 4.0 to 4.1

.a’s

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)

Upgrade Processing

Confirm Start of upgrade

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

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

Questions on Upgrades

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

TWL 4.1 ( and TWL 4.0.072)

New TWL for Windows Database

Select Windows environment to Add TWL to

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

TWL Script changes for Windows Database

Twlservice.bat, twlservice.start, twlservice.shut, twlservice.queryTwlsendTwlrcvTwlrcvpackAutodrop

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

Questions on TWL New Installs

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

eSales Center

Installing eSales Center

eSales Center Directories/Host

Make sure adminserver / environments may be shut down!

eSales Environment and Options

eSales Configuration

eSales Center Install Processing

eSales Changes for Windows Database

No Appserver, Webspeed brokers act as appserver

Webspeed started and stoped with nxtall.start/nxtall.stop

Webbroker.start, webbroker.shut, webbroker.query

Questions on eSales

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

Code Push and TWL

Push Process now has options for separate pushes for Standard, SX CHUI, and TWL CHUI

Code Push and TWL

Standard.pl (and appserver) SX CHUI (rptmgr) TWL CHUI TWL D21 ( library for Symbol D21 RF unit)

IF PL files are locked, it will shutdown all services for you

Code Patches

Similar to Unix DB patches Uses same patch download No FTP process

Schema Patches (4.2)

Minor Upgrade to Database

A preview of what’s coming up

Schema Patch Extraction

Answer Yes to All if replacing files

Schema Patch Information

State of database may be down

Create UpgradeDelta.df

Same process as major upgrade to determine custom mods and preserver initial values, triggers, and changes to standard tables

Uses %TEMP%\ {f768f490-cd0d-11d3-83c0-00104b99c420}

Creates Customdelta.df holding custom changes to previous version

Create UpgradeDelta.df holding delta needed to upgrade to new version preserving custom

Start Schema Patch Upgrade

Backup during upgrade if AI was enabled

Schema Patch Steps to Similar to Major Upgrade

Shutdown Adminserver Disable AI Disable Report Manager from starting Run before upgrade programs (.b) Load Upgradedelta.df Confirm schema after upgrade Re-enable AI Run Install for regular SX Code Patch (assumes

4.1.xxx baseline)

Questions on Schema Patches

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

Finish Schema Patch

If installing TWL, you may want to turn off Compile until TWL is patched

Post Schema Patch 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..

TWL Schema Patches

Prompts

TWL Schema upgrade Info

No Schema changes in 4.2, but 4.3 will have them

TWL Upgrade Options

Leave at defaults in 4.2

TWL Upgrade Compile Options

Also Compiles both SX and TWL CHUI

TWL Upgrade Processing

Same upgrade steps as SX for database Compiles both SX and TWL

Finish TWL Schema upgrade

TWL Upgrade Questions

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

Uninstalling

Uninstall / Re-Install can be run instead of Major Upgrades – required if changing Progress Location/Versions

If uninstall keys left in registry may have difficulty Remove Registry Keys Remove Directories

Uninstalling Directories

\NXT - code \NXTDB - SX windows database \NXTAI - after image \NXTAISAVE - saved extents \NXTBACKUP - backup of db for ntbackup \NXTPROG - Progress install (prior to 3.2) \TWL (twltest) - TWL Online \TWLDB - TWL Windows Database \Nxtrend (nxtrendtest) - esales

Uninstalling Registry Manually

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

SX.E - {f768f490-cd0d-11d3-83c0-00104b99c420}Nxt TWL Live: {E5D57B5C-AB49-409F-AB44-603E6794AF86} TWL Test: {2F17550C-A3A3-4DD7-AD34-E0D01163C0EC} eSales Live: {0CFAC66F-DFB8-448B-9C56-

016386194AE6} eSales Test: {2b71f3d7-a789-4d66-b72b-4791d76bdf8f}

Any other Questions

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

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

Documents

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