Configure the Core Application

Once the host is installed, it is time to log in to the host application where the core application is configured.

1. Click Go to core app configuration.

2. Log in as the Host Admin User you just created.

3. Click the edit icon next to Encryption Key.

The key file that was created for the host should be used for the core app as well.

4. Click Import Key File.
5. Enter the Password that was created earlier.
6. Click the Drop here field on the panel to browse to the file or drag and drop the file to upload it.

7. Click Save Key.

8. Click Return.

9. Click the edit icon next to Database.
10. Add the same connection string that you added in the host configuration.

IMPORTANT: If you are an Oracle user, the azteca user must be used here for the User and Password fields.

11. Select the connection string you just added from the Active Connection String drop-down list.

12. Next, click DB Schema Manager and click Update Database on the Database Schema Manager panel.

This creates and updates the core database tables to the latest version.

IMPORTANT: The red Database is not up-to-date message might not appear under certain circumstances. Even if it does not appear, you still need to complete the steps to update the database.

The Database Schema Manager panel shows the progress while it checks the CWVERSION and migration history tables. The Log displays messages from Database Schema Manager.

Once it's successfully completed, users receive a message indicating that the database was successfully updated. If not, the log shows where any issues were encountered. The Log also states any data migrations that need to be completed. See Data Migration Manager Guide for more information.

13. Click Verify Database to identify any additional schema changes that need to be made. If there are any errors in the log after verifying the database, you can fix them by running the SQL scripts provided at the bottom of the log.
14. Click Identify Customizations to locate any customizations in the database.
15. Click Identify Other Schema Items to locate anything that's been added to the database, such as additional tables, views, or procedures.
16. Click Close.

TIP: If you need to manually open Database Schema Manager, it can be accessed from the Cityworks 23.14 download file under host-setup > tools > DatabaseSchemaManager > CwDbSchemaManager.exe. See Database Schema Manager for more information.

17. Click Return.

18. Click the edit icon next to Cityworks License.

There are two options for activating your license key: Online Activation or Upload. Online is the preferred method, while Upload is only used in rare cases when a site is unable to reach the authorization servers that Azteca Systems uses. Please note that this is usually caused by a proxy server being involved with internet access at the site. See Offline Activation for more information.

19. Click Online Activation to activate the license key.

20. Enter the License Key number.
21. Click Activate.

When the license information has been retrieved a success message displays.

22. Click Return.

A Cityworks domain and administrator login needs to be created.

23. Click the edit icon next to Users.

24. Click Add record on the Employees panel.

25. Enter the First Name, Middle Initial, and Last Name.

26. Click Add.

27. Click Create New Domain.

28. Enter the Domain Name and Description.

29. Click Create.

30. Select the new user and assign licenses to them.
31. Select the user's Domains and Current Domain.

32. Click Create Log In.

33. Enter the Email and Password.

34. Click Create.

Now that the user has been created, they can be assigned as the Domain Administrator or Cityworks Administrators.

35. Select the newly created domain from the Domains drop-down list in the Domains panel.
36. Click Add record.

37. Select the user and click Add.

38. Click Add record on the Administrators panel to add a Cityworks administrator.

39. Select an employee and click Add.

40. Click Return.

41. Click the edit icon next to System Settings.

42. Select the Timezone.
43. Select Secure Session Cookies to only send session cookies over HTTPS. Selecting the check box might cause issues if your Cityworks site isn’t running in HTTPS or if it’s behind a reverse proxy that terminates HTTPS before it reaches the site.

44. Select Enable Windows Authentication to set the site to use Windows Authentication.

IMPORTANT: Starting in 23, Cityworks handles Windows Authentication in the app rather than in IIS. The following settings need to be configured manually in IIS Manager to support this. Anonymous Authentication should be set to Enabled and Windows Authentication should be set to Disabled.

45. Select Enable Multifactor Authentication (MFA) to enable MFA in the site. Once it's enabled, set up the Multifactor Authentication preferences for your site in Admin. See Configure Global Preferences in the Admin 3.10 Guide.
46. Enter the Form Multipart Body Length Limit (in Bytes). To support attachments larger than 1 GB being uploaded to a work activity, enter 2147483648. Increase the number as needed.
47. Enter the Form Value Length Limit (in Bytes). To support attachments larger than 1 GB being uploaded to a work activity, 4194304. Increase the number as needed.

These values need to match what is entered in the settings in the app-settings.yaml file as well. See Attachment File Size Update for more information.

48. Click Return.

TIP: To access your new site, enter https://<server>/<site>/login in a browser.

IMPORTANT: If you are installing Cityworks with a brand new database, a site admin (CWDBA) needs to be manually created. See Database Schema Manager for more information.