When setting up Lucity the Lucity Server should only be installed in one location *. This installation should take place at a workstation connected to the server rather than at the server itself (except in the case of a completely local server install). Installation instructions may vary slightly depending on which database being used (SQL Server or Oracle). It is recommended to close all Windows applications before installing the Lucity software suite.
* When setting up a dedicated Testing environment it is necessary and ok to install another copy of Lucity Server.
Database Setup
SQL Server Users:
In the Lucity install media under Database\SQL Server\Clean locate the clean SQL Server database backups.
Using SQL Management Studio restore the backups into the SQL Server.
Note: The GBAComm and GBAUser backups must be restored, as well as the databases for any other products the agency owns.
Note: SQL Server Authentication MUST be enabled.
Oracle Users:
In the Lucity install media under Database\Oracle\Clean locate the clean Oracle .dmp file.
Restore the .dmp file and run the accompanying script.
Create a Lucity "Share"
Prior to running the Server Installation, a new directory needs to be created on the file server. This folder will contain connection information, reports, and other shared objects that Lucity workstations will use to connect to the databases.
Create the folder on the file server. All machines that will have a Lucity product installed must have access to this folder.
Name the folder LUCITY_APPS, or something similar.
All users that need to access Lucity must have the following permissions for the folder: Modify, Read & Execute, Read, Write.
Share the directory
All users that need to access Lucity must have the Change and Read permissions to the share.
Note: All machines that will have a Lucity product installed must have access to this folder.
Note: After the Server/Database install this folder will contain a Config folder. The location of that folder will be required by all other Lucity installations.
This shared folder will be used when performing subsequent installs. Lucity recommends using UNC pathing. While we do support accessing this folder as a Mapped Drive Letter, every user that accesses Lucity must have the same Drive mapped on their machine.
Install Lucity Server
Open the Lucity install media and run Setup.exe, the following screen will appear:
Note: It is highly suggested to run the Server installation/upgrade directly on a desktop machine. This ensures that the paths used during the installation/configuration are valid network paths.
Select the Server/Database option on the menu. The following window will appear:
Read the Welcome screen.
Click to continue. The License Agreement window will follow.
Read the License Agreement and make sure the I AGREE option is marked.
Click . The License Codes window will then appear.
The agency's license codes were provided electronically as an .xml file via email or a downloaded link.
Browse to the directory where the license file (LicenseCodes.xml) is located.
Note: If no license file was received, please contact a Lucity support representative.
Click to continue. The Required Components window will then appear.
Read the Required Components screen.
Click to continue. The Server Install Options screen will appear:
Use the Browse button to specify the path to the Lucity Share (covered above).
Click to continue. The following prompt will appear if the installer determines that this is a new install instead of an upgrade:
The installer makes this determination based on the location of the config directory selected above, if no pre-existing shared file directory is found. Click OKto proceed.
Note: If this should be an Upgrade instead of a New Install, click the < Back button on the next screen that appears. This will return to the Shared Directory screen and allow the proper location to be designated.
Click to continue. The following summary screen will appear. Read the information on the screen to confirm the choices.
Note: For SQL Server and Oracle users, the Client Name will read "N/A". This is normal.
Click to continue. Client Maintenance will be launched to configure Lucity's connection to the databases. For more information about Client Maintenance go here.
After running Client Maintenance, the following dialog will appear:
Choose Run or Skip depending on the status of the administrative user setup in Security. Read the dialog for more information about.
The install will complete after clicking Skip, or clicking Run and making the necessary Lucity Security changes.
to continue. The License Agreement window will follow.
. The License Codes window will then appear.
to continue. The following prompt will appear if the installer determines that this is a new install instead of an upgrade: 
