Lucity Migration Process - Identify, Create, and Restore for a Smooth Transition

2. Lucity Migration Process

3. 1. Identify your Current configuration • Which servers are currently hosting Lucity products? • Where is the Lucity production database sitting? • Where is the Lucity config, License codes, and Document hive? • If you have a system design from the initial installation of Lucity, this will make things easier.

4. Find your Configuration Directory Navigate to the Lucity Admin Portal > System Settings > Settings with Custom interface > Configuration Directory

5. Find your License Codes The License codes will more than likely be placed either within the configuration directory or in a folder on the same share as the configuration directory.

6. Find your Document hives Navigate to the Lucity Admin Portal > System Settings > Documents. Your Internal, External and sign Library Document hives will be listed here.

7. Don’t forget about your Report hive! Navigate to the Lucity Admin Portal > System Settings > Reporting. Your Report hive will be listed here.

8. 2. Create the destination servers for the Migration • Think about the future of the Lucity product with your organization. • Will you be adding new products or integrating with other software’s • Have your Max concurrent users surpassed your original servers' capabilities? • Lucity Technical Staff can assist with creating a new System Design for you if you wish

9. 15 Concurrent Users Example • DMZ and Internal Web 4 core, 8GB RAM, 140GB OS/Space, Offline Mobile 160GB OS/Storage. • Database Server 4 core, 8GB RAM (4GB RAM Dedicated to SQL), 250GB OS/Space • Lucity Services/File Server 4 core, 8GB RAM, 250GB OS/Space initially.

10. 15 Concurrent Users Example

11. 2. Create the destination servers for the Migration • Make sure your new Servers can communicate to the SQL Server, Document Server, and Arc Environments through the network properly.

12. 2. Create the destination servers for the Migration • Install IIS and the appropriate roles and features for IIS on Lucity web and Mobile Servers. • Install and configure SSL’s for Lucity web and Mobile Servers. • Create Domain Windows users LucitySVC and LucityDOC to run the services and document server. • (Make sure those user's passwords never expire) • .net framework 4.8 (full) • net 4.5 should be installed and enabled in IIS • IIS 6 Metabase Compatibility • IIS 6 WMI Compatibility • Windows Authentication • Application Initialization • WCF HTTP Activation Feature (under the .net framework 4.5 features) • Enable Dynamic Content Compression (For Mobile Server)

13. 3. Acquire Backups of the Database, Config Directory and Document Hives • Backup the Lucity production database and make it accessible on the new SQL Server machine. • Copy the Config directory and Document Hive folders and make then accessible on the new Lucity File Server. • NOTE: The Document Hive’s may be large so make sure the new file server can handle the amount of data within the hives

14. 4. Start the Migration process • Make sure you have Lucity_USER and Lucity_Gateway SQL Credentials available. • Make sure you have Database admin Credentials for BOTH Old SQL Instance and NEW SQL Instance. • Have your Install Media accessible on the Destination Lucity Servers

15. 5. Restore the Database to the new SQL Instance • Take the Backup of your production database and restore it to the new SQL Instance… • This part is Simple Enough

16. 6. Create Config Directory and Document Hives • Place the Config and Document Hives on a drive on the new File server and Share it out to the network. • Ensure End user machines can Read the Config fold over the network. • Ensure your LucityDoc User can Modify your Document Hives • Ensure your LucitySVC User can Modify the Config directory

17. FORK IN THE ROAD!!! • (A) Are You Staying on your Current version of Lucity? • (B) Or Are you upgrading to a new version of Lucity during the Migration

18. 7A. Staying on Current Version • At this point you will need to go to an existing Lucity desktop install and open Client Maintenance. • Open Client Maintenance and specify the Config directory and License codes file that are on the NEW Servers. • Enter the Database Admin credentials for the OLD SQL Server. • Lucity Config folder still thinks its connected to the old Database instance.

19. 7A. Staying on Current Version

20. 7A. Staying on Current Version • Once in Client Maintenance. Change the SQL instance to the new SQL instance that the database will now sit on. • Make sure the Lucity_User and Lucity_Gateway credentials are still populated, If they are blank, enter in the passwords. Then hit Next. • Once you hit Next, you may get prompted to enter in New database admin credentials. That’s because Lucity needs to connect to the new SQL instance now that you’ve changed it in Client Maintenance

21. 7A. Staying on Current Version

22. 8A. Current Version – Update existing Apps • Once Client Maintenance is finished, the config directory should be connected to the new SQL instance. • Install Lucity Services and Web apps on the new servers using the install media (BE SURE TO SPECIFY THE NEW SQL INSTANCE AND CONFIG DIRECTORY DURING INSTALLS) • Existing Desktop apps don’t need to be reinstalled, Just run the DSN Utility on those desktops and populate the New Config directory in the DSN Utility. This will point existing Desktops to the new SQL Instance and config

23. 7B. Upgrading to a new Version • Similar Process, except you will go through the install media and change the database instance and config locations during the Server installation. • Provide the UNC Path to the new config and License codes location during the server upgrade. • Enter the OLD Database Admin Credentials

24. 7B. Upgrading to a new Version • A Client Maintenance interface will open with the new UNC paths provided. Change the OLD SQL Instance to the New SQL Instance • Make sure the Lucity_User and Lucity_Gateway credentials are still populated, If they are blank, enter in the passwords. Then hit Next. • Once you hit Next, you may get prompted to enter in New database admin credentials. That’s because Lucity needs to connect to the new SQL instance now that you’ve changed it in Client Maintenance

25. 7B. Upgrading to a new Version • Once you Hit ‘Next’ the Database will start upgrading to the new version, then the Config file will be updated to represent the new Lucity version.

26. 8B. Upgrade – Install Apps • At this point most everything is ‘Migrated’. Follow Standard upgrade procedures on the new servers for the rest of the applications. • Make sure to specify the new SQL Instance and Config Location when installing web and Desktop apps.

27. 9. Repointing Documents • After everything is installed, We will need to get the Document and reports configured with their New Location on the file server. • First thing you’ll want to do is open Admin tools and Change the UNC Path of the document hives in system settings

28. 9. Repointing Documents

29. 9. Repointing Documents • Lucity Builds a folder structure from the UNC Paths you provided in system settings. • It also enters in the UNC Path where the document is stored in Tables in the Lucity database

30. 9. Repointing Documents

31. 9. Repointing Documents • We have a Simple Update statement that can make this process painless. • UPDATE WKDOC SET DOC_PATH = REPLACE(DOC_PATH, 'C:\OLDFILELOCATION\Example', '\\NewFileLocation\DocServer’) • This will need to be run against all Document tables in the database

32. 9. Repointing Documents • Let's Say my file share is now sitting at \\Lucity\LucityServer\DocShare\InternalDocuments • To Update the file paths in this table we would use the SQL Below • UPDATE WKDOC SET DOC_PATH = REPLACE(DOC_PATH, '\\MKONOVALSKE\LucityServer\DocShare\InternalDocuments', '\\Lucity\LucityServer\DocShare\InternalDocuments’) WHERE DOC_PATH LIKE '\\MKONOVALSKE\LucityServer\DocShare\InternalDocuments%'

33. DONE! • You’ve now completed your Server Migration! • Go ahead and make sure everything is working properly. • Also, go and set the Old Lucity production database (On the old instance) to offline. To ensure no one accidentally connects to that database.

34. Refresh Test environment with Production Data • Refreshing your Test environment with data from Production is very simple, you need a few things • Your test environment must be on a Version Equal too or greater than your production environment. (Can't place a 18r2 Database into a 16r2 Environment) • You need a list of the URL’s of the Test web apps that the test environment is hosting

35. Refresh Test environment with Production Data

36. Refresh Test environment with Production Data

37. Refresh Test environment with Production Data • Get a Backup of your Production database and Restore it OVER the Database connected to the Test environment. (Be sure to Keep the database name the same) • Open Client Maintenance for your Test environment and Click through it until it closes (you shouldn’t need to change anything). • Open Lucity Admin tools in Test and replace the URL’s you gathered earlier in the proper places in system settings. • (Optional) Repoint the Documents in the database to the document Hive

38. Helpful Links! • https://lucity.zendesk.com/hc/en-us/articles/115000229303-Migration-Overview • https://lucity.zendesk.com/hc/en-us/articles/115000229763-Database-Migration • https://lucity.zendesk.com/hc/en-us/articles/115000215366-Lucity-Config-Migration • https://lucity.zendesk.com/hc/en-us/articles/115005209406-Document-and-Web-Report-Migration

39. DONE! • Mkonovalske@Lucity.com • Jswain@Lucity.com