Once you uninstall v20, you will no longer be able to run the v21PreMigration Analysis tool. Be certain that all Pre-analysis and setup is complete and valid before uninstalling v20!
B. Upgrade CM4D Installation to v21.2.0
C. Upgrade Database to Site Schema 21b and Schema 21a
At this point, you should be absolutely sure that all settings in your map files are Valid and no errors were returned when analyzed by the v21PreMigrator Analysis tool. Do not delete the two map files generated by the PreMigration Analysis tool (v21MigrationMapManDocs.txt and v21MigrationMapReportPaths.txt).
As with any upgrade, it is highly recommended that you back up your system before changing the version or updating your databases. With v21 in particular, you should back up all of your Managed Documents and your Database, in addition to the usual configuration files.
CM4D v 21 uses a new version of the ATS Licensing Server and requires a new version of all CM4D license files. Once you upgrade to the new ATS Licensing Server and CM4D v21, your 20.0 CM4D License files will no longer work. Contact [email protected] for help with license requests.
If you are using Named Licenses, you should save all of your existing Machine Identifiers for each license that has Named Leases assigned, before uninstalling the Licensing Server to avoid having to reset them all from scratch.
1. Uninstall ATS Licensing Server 2.0.
2. Install ATS Licensing Server 2.1.
3. Import your new ATS CM4D v21.0 license file(s).
4. Add Named Leases manually as needed, or wait until the applications request licenses and approve them at that time.
See the ATS Licensing Server Manager documentation for information on some of the new features available in this version.
All PreMigration Analysis must be complete AND valid before you continue!
Follow typical backup and upgrade procedures, but in particular, make sure to back up all Managed Documents as these are particularly affected by this upgrade.
1. Uninstall CM4D v20.
2. Install CM4D v21.2.0.
Refer to the topic Upgrading an Installation as a general guide.
Beginning in v21, the Site Database will potentially get much larger due to new information now being stored in the Site Database. Please check that you have sufficient resources to accommodate this significant size increase.
Run the database update scripts provided with the v21 installation.
1. Run UpdateSite21a.sql on all Site databases.
The Site Database 21a update script will result in Caution messages similar to the following. These messages are expected for this update and do not indicate a problem.
(1 row(s) affected)
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
(58 row(s) affected)
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
2. Run UpdateSite21b.sql on all Site databases.
a. If you are using SQL Authentication, also run Site Grant.sql on your Site databases.
3. Run Update21a.sql on all CM4D databases.
a. If you are using SQL Authentication, also run Grant.sql on your Site databases.
The CM4D Scheduler and CM4D Launcher services need to be started before the migration can process. You may choose to wait until you have set up and activated the migration in the Migrate S21 dialog in Site Manager before you start the services. Either way, the services must be started for the Migration to actually proceed.
1. Go to Services.
2. Start CM4D Scheduler.
3. Start CM4D Launcher.
If your Services are not starting, check to make sure that the CM4D Server license feature has been approved for a Named Lease in the ATS Licensing Server Manager.
You may also start the DataSmithBatch Service at this time. See the topic v21 Migration Notes for information on what will happen to new DataSmithBatch jobs while the migration is in process.
Continue to Step 3: Execute the Migration.