Knowledgebase Home Page  >  RapidSpell Web ASP.NET  >  Misc
Search the Knowledge Base
How to use user dictionaries in a server farm environment.
https://keyoti.com/kb/Default.aspx?ToDo=view&questId=90&catId=60

Options

Print this page
Email this to a friend

RapidSpell Web for ASP.NET is compatible with server farms, however one natural question that arises with this type of usage related to user dictionaries.  Since user dictionaries are server based (stored in developer specified files for each user) the standard setup would cause each server to have it's own copy of a user's dictionary (depending on which server handled the request when the user added a word).
 
The recommended way to work around this problem is to use a network share for the UserDictionaryFile property.
 
eg.
 
C#
RapidSpellWebLauncher1.UserDictionaryFile = @"\\serverA\userDictionaries\"+theUsersDictionaryFile;
 
VB
RapidSpellWebLauncher1.UserDictionaryFile = "\\serverA\userDictionaries\" & theUsersDictionaryFile
 
 
Provided that each server in the farm can access \\serverA they will all use the same file.
 
 
Config Notes
 
Permission needs to be given to each server in the farm to write to the dictionary directory \\serverA\userDictionaries
 
1. The ASPNET user account on each web server needs to have the password reset to whatever you want, but the password needs to be the same on each web server.
2. A local user ASPNET account needs to be created on the "serverA", with the same password as the web servers.
3. In the Machine.config (usually in C:\WINDOWS\Microsoft.NET\Framework\v1.x.xxxx\CONFIG\) file on each of the web servers, there is an node called
two of this node's parameters are username and password. These need to be set to username="ASPNET" and password="Whatever you set it to".
4. Finally, on each web server, under Control Panel --> Administrative Tools --> Local Security Settings the ASPNET account needs to be given permissions to "Act as part of the operating system".

If you have any problems please email support@keyoti.com
 


Related Questions:

Attachments:

No attachments were found.