The next configuration steps of UserManagement Admin Web are done inside the file web.config, which can be found at the C:\inetpub\wwwroot\UserManagementAdminWeb directory.
The file web.config holds the connection information to access the UserManagement database(s) and the visibility settings for the wizards in UserManagement Admin Web. Every database connection has a connection profile (GeoUserManagementConnection).
From a technical point of view the connection is established via the file GeoProject.dll.
Note that you need at least a text editor capable of editing UTF8 text files for editing web.config, e.g. UltraEdit32, PSPad or Notepad++. Do NOT USE NOTEPAD instead – the web.config file would get corrupted then.
Note: The configured database user has to be granted at least Read (Select) and Write (Insert, Update, Delete) rights at the tables of the UserManagement model.
<GeoUserManagement>
<GeoUserManagementConnections>
<GeoUserManagementConnection>
<Profile>My MSSQL Profile</Profile>
<Host>MyServer\sql2008</Host>
<DatabaseType>MSSQL</DatabaseType>
<DatabaseName>MySQL_Database</DatabaseName>
<Username>MyUsername</Username>
<Password>KH4yhJLabVaPSxrXOGCb7g==</Password>
<ProviderExtension></ProviderExtension>
<KeepconnectionAlive>1</KeepconnectionAlive>
</GeoUserManagementConnection>
<GeoUserManagementConnections>
<GeoUserManagement>
Parameter |
Description |
Valid & Default Values |
Profile |
Name of the database connection, which is shown at the dropdown box at the UserManagement Admin Web login site. |
|
Host |
Database host name (if necessary) and database instance (if necessary) |
|
DatabaseType |
Database type |
ORACLE MSSQL MSACCESS |
DatabaseName |
Database name |
|
Username |
Database user name (Not needed if database type is MSAccess; the application requires from a not secured MSAccess database the default login user name "admin") |
|
Password |
Password of the database connection (if necessary) encrypted by the included software Note: For details how to encrypt your password, please see chapert Creating an Encrypted Password. |
|
ProviderExtension |
Connecting to a 64-bit OLEDB-Client for Oracle and MSSQL set the value ‚.1 |
Valid values: |
KeepconnectionAlive |
0: Defines, that the database connection is closed after every database access. 1: Defines, that the database connection keeps alive. Note: The value '1' improves the performance especially for MS Access, because the database connection keeps alive. But keep in mind that the session on the server also remains open for a bit longer. We recommend '1' -> MS Access '0' -> SQL and Oracle |
Valid values: 0 1 |
Overview of the User Management database connection properties
Note: See the subsequent chapters ORACLE Connection Parameter, MSSQL Connection Parameter, MSACCESS Connection Parameter and Menu Entries for details regarding the web.config configuration.