Most installations of ContactsLaw will begin with a single SharePoint server/site, however as the library grows it may be necessary to configure additional site collections (content databases) and/or servers to balance load and maintain good performance. The most typical example of this is when a separate site collection is configured for
documents on
archived files.
| As a general rule of thumb, no individual content database should exceed 100GB. System administrators should monitor the size of the document library and provision a new site collection (and content database) before the library exceeds these limits. There is no requirement to create additional web applications or servers unless addressing a specific performance problem. |
As servers and site collections are provisioned, entries are added via the document server settings editor.
For each entry, the following options can be set:
The purpose of the library (main or long-term archive)
The server name and port
This may be a machine on the local network, LOCALHOST or an Internet server
For servers with multiple site collections, the server name may include a path component
For network shares, this is the UNC path to the shared folder
The name of the document library that ContactsLaw will use to store documents
The plug-in that will be used to interact with the document library
The URL to the ContactsLaw
web service (this will be passed to the plug-in)