Available Licenses tab

The Available Licenses tab displays all Licenses that are currently not installed, allowing users to select licenses and install them. By selecting a license on the left, the information on the right side of the screen will change to reflect the license information. Licenses can also be installed from this screen.

How To Install a License

1. Client Maintenance will load the empty configuration.
2. At the top of the screen click the Available Licenses tab.

   

3. On the left will be a list of licenses that are in the LicensesCodes.xml but are currently not installed.
4. Select a license on the left. The right side of the window will display information about that license.

   Note: Licenses marked PRD are for production use. Licenses marked NPR are meant to setup Test or Development environments.

5. To install a license, highlight a licenses in the Available Licenses grid and click the Install button. The following window will be displayed:

   

6. This window is to specify a user-friendly name for the license, like the name of the agency, or department this license is for. Enter a name and press Ok. The following window will appear:

   

7. This displays a form to fill out connection information for a database. After this form is filled out another one will be displayed for the next database.
   • Database Information - This specifies the location of the database(s)
     • Database Name - Enter the actual name of the database to be connected to. This could be GBAComm, GBACommPRD, etc...
     • Database Platform - This is automatically filled out based on the License file. If this is incorrect please contact Lucity Support.
     • Instance Name - This is only for SQL Server or Oracle databases. Enter the name of the SQL Server or Oracle Server instance.
     • Path - This is only for Access databases. Enter the Path to where the databases will reside. This should be located in the Lucity Share's Data folder.
   • General Login Information - The items in this category indicate the Login credentials to use when connecting to the database. It is only required for SQL Server and Oracle server clients.
     • .NET Login ID - Indicates the Login ID to use when connecting to the database for applications that were developed using Microsoft .NET technologies. This login information is retrieved via the Gateway Login account.
     • .NET Login Password - Indicates the Login Password to use when connecting to the database for applications that were developed using Microsoft .NET technologies. This login information is retrieved via the Gateway Login account.

       Note: The .NET credentials are persisted to the GBAUser database.

     • Legacy Login - Indicates the Login ID to use when connecting to the database for applications that were developed prior to utilizing .NET technologies.
     • Legacy Login Password - Indicates the Login Password to use when connecting to the database for applications that were developed prior to utilizing .NET technologies.

       Note: The Legacy credentials are persisted to the GBALogin.mdb in the central CONFIG directory.

8. After filling out the above click Next >.
9. The above screen will appear again for the next database. The previously changed information should be there. Verify the information and click Next >.
10. Continue until the GBAUser database screen appears:

    

11. Fill out the Database Information and General Login information as before.
12. Fill out the Desktop Gateway Login Information. For more information about these settings and different configurations go here.
13. Fill out the Web Gateway Login Information - The Web Gateway Login Information section is required for all SQL Server and Oracle clients regardless of whether they use the web applications. It does not pertain to Access installations. Client Maintenance uses the information input into these fields to generate a new account in SQL Server or Oracle and assign permissions for that account. Changing the data in these fields (like updating to a new password) will update the password in SQL Server. If clients are using the Web applications, they must also go to each of their virtual directories and make the password changes there (or re-install the web apps).
    • Gateway Login ID - Indicates the Login ID used to connect to the GBAUser database and retrieve the connection information for the Lucity databases. If the Integrated Security for Desktop Gateway option is set to False, both the Web and Lucity Desktop applications will use this account.
    • Gateway Login Password - Indicates the Login Password to use to connect to the GBAUser database and retrieve the connection information for the Lucity databases. If the Integrated Security for Desktop Gateway option is set to False, both the Web and Lucity Desktop applications will use this account.

      Note: The Gateway Login Password should be at least 8 characters in length.

14. When all the information is entered click Next >.
15. Continue until all the databases are configured.
16. Click the Installed Licenses tab at the top of the tool.