When setting up Lucity, the Lucity Server should be installed in only one location*—preferably a workstation connected to the server, rather than at the server itself (except in the case of a completely local server install). Installation instructions will vary slightly depending on whether an agency uses a SQL Server or Oracle database.
* When setting up a dedicated Testing environment it is necessary and acceptable to install another copy of Lucity Server.
Close all Windows applications before installing the Lucity software suite.
Database Setup
SQL Server Users:
Note: The Lucity database backup must be restored
Note: SQL Server Authentication MUST be enabled.
Oracle Users:
Create a Lucity "Share"
Before running the server installation, a new directory must be created on the file server to store connection information, reports, and other shared objects that Lucity workstations use to connect to the databases.
Note: After the Lucity Server/Database installation, this folder will contain a Config folder. The location of that folder is referenced in all other Lucity installations.
This shared folder is used in subsequent installs. Lucity recommends agencies use UNC pathing. While we support accessing this folder as a mapped drive letter, doing so means that every user that accesses Lucity must have the same drive mapped on their machine.
Install Lucity Server
Note: Lucity strongly suggests that agencies run the server installation/upgrade directly on a desktop machine to ensure that the paths used during the installation/configuration processes are valid network paths.
Note: If your agency did not receive a license code, contact a Lucity support representative.
Note: If you are attempting to upgrade rather than perform a new install, click the < Back button on the next screen to return to the Shared Directory dialog and choose the correct directory.