Milan connects to WorkSite, Milan, and billing databases through the use of connection strings. A typical connection string, like the one below, specifies a database server and connection method.
Data Source=SQLServer;User Id=sa;Password=password;Initial Catalog=milan;Integrated Security=false;MultipleActiveResultSets=True
As can be seen in the above example, when using SQL authentication (Integrated Security = false), the user id and password are passed as clear text and visible to any Milan user with access to the Application Configuration page in Milan. For greater security, you can instead connect to any database with Windows authentication (Integrated Security = true), which uses the credentials of the account running the Milan application pool to authenticate with the SQL server.
Note: Connection strings are stored in encrypted form in the Milan.AppSettings table.
While most connections strings used by Milan can be configured during the initial web-based setup, it is possible to add or edit connection strings at any time through the web client by opening Administration → Application Configuration → Connection Strings.
Note: If you will be using Billing To Milan, you must configure the required connection strings on the Connections Strings tab before attempting to run the program. Refer to Configuring Billing To Milan for more information.
As far as Milan is concerned, there are only two kinds of connection strings: WorkSite connection strings and non-WorkSite connection strings. WorkSite connection strings point to WorkSite libraries, while non-WorkSite connection strings point to everything else, including the Milan database, Billing To Milan, and SQL-based billing systems.
The two connection strings used by Milan to connect to its own database, adminSiteAudit and milanlog, are created during the initial web setup. Although it is possible to edit either connection string, neither can be deleted.
By default, the milanlog connection string points to the primary Milan database, i.e. the adminSiteAudit database. Milan uses two tables within this database, Milan.EventLog and Milan.Audit, to store provisioning service events and audit events, respectively.
If you would prefer to store Milan's logs in a separate database dedicated to event logging, you must make a copy of the Milan database, keeping the full schema intact, and configure the milanlog connection string.
To configure a separate database for event logging:
Setting | Description | ||||||
---|---|---|---|---|---|---|---|
Data Source | Name of the SQL server hosting the Milan log database | ||||||
User ID | An SQL account with db_owner access to the Milan log database | ||||||
Password | Password for the SQL user account specified in User ID | ||||||
Initial Catalog | Name of the Milan log database | ||||||
Integrated Security |
|
Billing To Milan recognizes three specific connection string names, which correspond to its three modes of operation. By default, these string names are billing, archive, and security.
Refer to Configuring Billing To Milan for more information on how to specify different connection strings for each type of operation.
To add a non-WorkSite connection string:
Field Name | Description | ||||||
---|---|---|---|---|---|---|---|
Connection String Name | Name of the connection string | ||||||
SQL Server Name | Name of the SQL server | ||||||
SQL Database Name | Name of the target database in SQL Server | ||||||
Trusted / Integrated Login? |
|
||||||
SQL User Name | Name of user with access to target SQL database Note: This and the following field should only be filled in when using SQL authentication. |
||||||
SQL Password | Password for user account specified above |
During the initial web setup, you can only specify one WorkSite database for Milan to manage. However, Milan can be configured to manage as many WorkSite libraries as you require.
To add a WorkSite connection string to Milan:
Field Name | Description | ||||||
---|---|---|---|---|---|---|---|
DMS Name | Name of the WorkSite server or server cluster | ||||||
Database (Library) Name | Name of the WorkSite database | ||||||
SQL Server Name | Name of the SQL server hosting the WorkSite database | ||||||
SQL Database Name | Name of the WorkSite database on the SQL server | ||||||
Trusted/Integrated Login |
Note: When using Trusted Login, the service used by the Milan application pool must have db_owner access to the Milan database. | ||||||
SQL User Name | A user on the SQL server with db_owner access to the WorkSite database. Note: This and the following field should only be filled in when using SQL authentication. | ||||||
SQL Password | Password for the user account specified above |
ias_<DMS Name>_<ODBC Name>
, where DMS Name is the name of the WorkSite server and ODBC Name is the name of the ODBC connection to the WorkSite library.Both WorkSite and non-WorkSite connection strings can be edited and deleted in the same fashion.
To edit an existing database connection string:
To delete an existing database connection string from the Milan web client:
Note: The adminSiteAudit and milanlog connection strings cannot be deleted.