Solution Upgrade Checklist

Use the following checklist when upgrading a Diver Solution from 6.4 to 7.x:

  • Start with a copy of the live environment
  • Watch out for different system paths for DI files
  • DI software: E:\DI_Solution versus D:\DI\Dev\Solution (standard varies by version)
  • ETL and user scripts: Integrator, Production, DIAL
  • Search and replace paths using Workbench, unless you already parameterized your scripts
  • Watch out for scripts dependent on the system PATH variable, for example:
  • Integrator scripts calling integ without a specific path
  • Execute nodes in Production scripts
  • Production scripts
  • Integrator driver-scripts
  • DIAL scripts
  • Batch and shell scripts
  • Windows scheduler
  • Dependence on PATH environment variable
  • Hard-coded paths vs parameterized paths
  • Input and output locations
  • Identify back-end processes and which scripts require testing
  • Identify front-end application test requirements:
  • How many ProDiver markers require testing?
  • How many DivePort portal pages require testing?
  • Consider automated as well as manual testing:
  • Use DIAL to open all models as individual users (to apply permissions)
  • Use DIAL dive results to compare before and after results
  • Capture DIAL summaries and rows for each user and build them into models for further analysis
  • Identify most-recently used markers and automate testing with DIAL
  • Make pathing adjustments (if needed) to markers deployed in DivePort
  • Obtain new 7.x Solution license
  • Upgrade the 6.4 installation to 7.x with installers
  • This migrates user licensing assignments—these should be verified (see Conversion of 6.x Licenses to 7.x)
  • OWN authentication users will be prompted to change passwords
  • To prevent the password change prompt, use dicfg set boolean: “reset_passwords_for_new_hash”, “keep_old_hashes”. See Set Commands.
  • NOTE:
  • By default, users are forced to change their passwords, and the old hash is left in place. If you disable the password reset, disable keeping the old hashes as well to avoid having two hashes for one password.
  • Solution 6.4 password hashes for authentication OWN are saved using the attribute "password". Version 7.x has a new password hash algorithm and passwords are stored using the "password_hash" attribute. Any updates to passwords using Workbench are saved as 7.x passwords.
  • Preserves knowledge of location of the 6.4 Production Sandbox
  • Alternatively— create a new installation, new dataroot with the 7.0 installers
  • Set the 6.4 Production Sandbox in Workbench:
  • Tools > Server Settings > Projects tab
  • Create users as needed
  • Run through the test plan:
  • Automated and manual testing
  • Verify results are the same for 6.4 and 7.x—see cBase versus Model Sorting and Using Cumulative Columns to Rank Values
  • Developers test back-end processing: extracts, processing, model builds
  • Users test presentation side:
  • ProDiver reports

  • With cBases, when rounding numbers for display, ProDiver uses the round half up method.

  • DIAL reports emailed
  • DivePort page displays and functions
  • Are you making full (or any) use of Production?
  • Use task-specific nodes in favor of Execute nodes
  • Use parallel processing with Fork and Loop control nodes
  • Avoid Integrator scripts that call Integrator scripts
  • Parameterize path configuration using a tab-delimited text-file plus a Parameter node
  • Eliminate use of batch and shell scripts and Windows scheduler
  • Best practice is to have only a few Production scripts scheduled per project in Workbench