GIS Connection Strings

GIS Connection Strings are created and modified within the Lucity Administration Tool. This is the connection that Lucity will try to use to recognize whether feature classes in ArcMap are configured to update Lucity. If the geodatabase is an SDE Lucity will also use this connection string to connect to and update the geodatabase, when changes are made in Lucity. (How those updates work are also controlled by other system settings.)

How to

Setup a GIS connection String

1. Within the Administration Tool go to GIS > Connection Strings. The following window will appear

   

2. If there isn't a connection string already click Add Connection String and fill out the following fields. If it is an SDE database most of the fields will be used. If it is a Personal or File geodatabase only the Database and Database Type fields will be used.
   • Name: This is simply a name for the connection. Note: One connection MUST be named DEFAULT, so if there is only one geodatabase configured with Lucity, it must be named DEFAULT.
   • Map Service URL: (Optional) The map service used to push edits to the geodatabase from the Lucity Web interfaces
   • Database: This must contain the name of the SQL Server geodatabase. The database listed in this field is not the SDE repository database. Instead, it is the geodatabase that contains the infrastructure data that is going to integrate with the desktop. For Oracle geodatabases this must be blank. For Access or File geodatabase this is the path to the .mdb/.gdb.
   • Server: (For SDE databases only) This must contain the name of the machine where ArcSDE is installed.
   • Instance: (For SDE databases only) The only thing that will differ between an ArcSDE spatial connection and a direct connection is the information stored in this field.
   • Version: (For SDE databases only) This information is always required; it designates the name of the ArcSDE version that the desktop will use when updating the geodatabase. For Oracle, the Version is case sensitive.
   • UserName: If using DB authentication a user must be specified. This user must have edit permission to ALL feature classes linked to Lucity as this is the user that the desktop app will attempt to use to push edits to the geodatabase from Lucity.
   • Password: If using DB authentication type a password must be specified for the user.
   • Authentication type: This is used by the desktop application when pushing edits to the geodatabase from Lucity. The desktop app will attempt to connect to the geodatabase using either Database Authentication or Operating System Authentication. If using "DB" the UserName and Password fields must also be populated.
   • Database Type: Specify either SDE, Personal, or File.

     Note: The GIS configuration supports having multiple geodatabases connected to Lucity at the same time.