Document Server

Lucity Document Server must be installed at the server on which the application will reside. Installation instructions will vary slightly depending on the type of database an agency uses (Oracle or SQL Server).

Lucity recommends closing all Windows applications before running the Lucity software setup.

Network Configuration Requirements

• To support citizens or internal users uploading images to Lucity Citizen Portal, the Lucity Citizen Portal Server (in the DMZ) must be able to make http requests to the Lucity Document Server (not in the DMZ).
• To support tablet users uploading and downloading documents, Lucity Mobile Server must be able to make http requests to the Lucity Document Server.
• All clients who use Lucity Mobile Server or the Lucity Citizen Portal must install Lucity Web to support document upload/download.

General Requirements

• General hardware and software requirements >>
• The Server installation must be completed before installing the Document Server.

Specific Requirements

• .NET Framework 4.7 (Full)
• ASP.NET 4.5 should be installed and enabled in IIS.
• When using IIS 7 or higher, the following Role Services are required:
  • IIS 6 Metabase Compatibility
  • IIS 6 WMI Compatibility

How to Install Document Server

1. Open the Lucity install media and run Setup.exe. The following screen appears:

    

2. Select the Lucity Document Server option on the menu. The Welcome screen appears:

   

3. Read the Welcome screen. Click to continue. The Database Connection Information dialog appears:

   

4. In the Database Type field, select the type of database you are using (Oracle or SQL Server).
5. Enter the appropriate Connection Information for the database type. Note: These databases must already exist. The installation will create databases for you.
   • SQL Server Users: Enter the Instance Name and Database Name (Lucity). The latter must be the database that stores your Lucity information; change the name if your agency uses something other than Lucity.
   • Oracle Users: Enter the Instance Name, Host Name, and Port.
6. Click to continue. The Existing Site dialog appears:

   

   Note: This screen will appear only if more than one site is defined in IIS. If there is only one web site, this screen will not appear.

7. Select an existing web site where the virtual directory for Documents is/will be located.
8. Click to continue. The Virtual Directory dialog appears:
   • Lucity recommends using the default settings. The Physical Directory defaults to the root of the existing web site.

   

9. Click to continue. The Document Server User Information dialog appears:
10. Enter a Domain, Username, and Password. The document server will use this account to add or remove Documents and Custom Web Reports from the agency's document or web report repositories. The location of these repositories are specified in Lucity Web > Admin Portal > Settings > System Settings > Documents.

    

11. Click to continue. The SSL/TLS Option window appears:

    

12. To use the Document Server over SSL/TLS, check the Use SSL/TLS option. Agency administrators are responsible for configuring the site to support SSL/TLS by installing a valid certificate and creating an https binding if these items do not already exist.

    Note: If this option is enabled and an administrator does not complete the required SSL/TLS configuration steps in IIS, the Document Server will not run properly.

13. Click to continue. The Website Hostname dialog appears:

    

14. Enter your server's internal Hostname. (Do not add anything in this field but the Hostname.)
15. Click to continue. The Web Gateway User Information dialog appears:

    

16. The dialog informs the reader that the Username and Password provided will be used to create a new database user. Citizen Portal will use this account to query application configuration information. The designated user will be granted minimal database privileges and access to several Lucity stored procedures.

    Consider the following when creating a Username:

    • Lucity recommends using the default Username provided.
    • If you choose to use a different username, it should not be that of an administrative user or any existing Lucity user. If you enter a Username that is disallowed, you'll be prompted to enter an alternative Username.

      Note: You cannot use Lucity_User for this login.

    Consider the following when creating a Password:

    • If the Username entered already exists, the installation will verify the Password by attempting to connect to the database as this user.
    • Lucity recommends a Password of at least eight characters for new accounts.

      Note: By default, SQL Server 2005 or higher enforces an agency's local or domain password policy when evaluating passwords for database users. If you are using SQL Server 2005 or higher, please ensure that the password you choose meets your organization's password policy.

17. Click to continue. The Database Administrator Login dialog will appear:

    

    DBA credentials are required to create or update the specified user account. Enter the following information according to your database type:

    • SQL Server Users: Provide system administrator credentials or those of some other database administrator.
    • Oracle Users: Enter the gba_admin account or another database administrator account.

      Note: If the credentials entered aren't sufficient, an error message will detail the possible problems.

18. Click to continue. The Ready dialog appears:
19. 

    Note: IIS will be restarted during the installation.

    Note: It may take up to one minute to create the virtual directory, depending on the speed of the web server. Please wait for this process to be completed.

    More Information about Lucity's Data Collection Policy >>

20. Click to begin the installation. This process may take a few minutes.  The following window appears when the installation is complete: