iManage WorkSite has a client-and-many-server application architecture. The profile records, structure, and metadata are stored in a relational database – SQL Server or Oracle. The content itself is stored on a file server – which can be encrypted to be HIPAA-compliant as of WorkSite 9.0. The client machines – running FileSite or DeskSite – never communicate directly with the database server. All communication is brokered directly through the WorkSite server. So, in theory, that database could be renamed at some levels and relocated to a new server: the end-users would have no way of knowing, and no reason to care.
The naming of the database is completely ‘up to you’ – it’s determined at installation and configuration time. You can give it one name on the relational database server, like “WorkSite”, so that you can distinguish it easily from other applications’ databases. This name is not visible to the users of the system, but it is certainly vital to the server configuration.
Read further for where the name is configured…
What’s in a database name?
The name users see is largely/completely determined by the name of the ODBC system data source created on the WorkSite server(s). That is the source of the name people see in the FileSite navigation pane in Outlook. I like to use a name that reflects the purpose of the content. Perhaps Legal (or Legal1 if you are planning for growth). Or Admin. Or, Active if you are planning ahead to the Active-Archive content lifecycle. So, to build on the earlier example, the SQL database is called “WorkSite” and the ODBC datasource and functional name is “Legal1”.
Next, the iManage dbAdmin tool has a table of metadata called ‘database’. This is used to populate the ‘preferred database’ setting on each user record. While this table may appear to be decorative in that no visible errors occur when it’s empty, substantial strangeness can result when users do not have consistent preferred database settings across multiple databases. Therefore, populate this table manually when you configure WorkSite. Make sure the database names are consistent with those ODBC names, on all of your WorkSite servers and in all of your SQL databases.
Does this satisfy your curiosity? Contact me for a quick chat or email discussion if you’d like to know more. Cersys can coach your department to become WorkSite gurus.