The diagram below illustrates the current structure of the Server version of the WebSpellChecker application that installed on a separate server (instance, VM, etc.) and communicates with customer's web application via Web or Application Server.

  • WebSpellChecker application versions: 5.0.0+
  • Deployment type: WebSpellChecker application is installed and running on a separate server. Customer's web applications are deployed on other servers and accessing the server with the WebSpellChecker application. The WebSpellChecker application will process all the requests for spelling and grammar checking which are coming from customer's web applications and return the results of proofreading (detected spelling errors, grammar problems, and generated corrections).



Legend

Administrator is an administrator of both WebSpellChecker application and a customer web application. Administrator can perform or manage the the following actions:

  • Install and configure application on the server;
  • Activate the application license (enter a Ticket ID and request a License Response string);
  • Customize and adjust the default settings to meet end users' and business needs;
  • Create custom wordlists with specific terms to extend the default dictionaries (Custom and User Dictionaries);
  • Monitor the application performance and troubleshoot issues.

End User is a user of a customer web application. End user can perform the following actions (within scope of the WebSpellChecker application functionality):

  • Send input text for spell and grammar checking;
  • See and correct defined misspelled words with suggested corrections;
  • Ignore words or grammar problems;
  • Add words to a personal dictionary called “User Dictionary”;
  • Choose and change a language for spell checking.  By default, there are 16 languages available.
Customer Web Application(s) where proofreading functionality is required and will be used. 

WebSpellChecker is a web-based application. Thus, it requires a properly configured Web or Application Server. Check WebSpellChecker System Requirements to find our more about the supported Web or Application Server(s).

FastCGI is a binary protocol for interfacing interactive programs with a web server. It is aimed at reducing the overhead associated with interfacing the web server and CGI programs, allowing a server to handle more web page requests at once.

For a proper work of the application components, FastCGI module must be enabled for a chosen Web Server.

Web/Application Server requests JS files, WSC Dialog and CSS files, then sends all requests with text for spelling and grammar checking to AppServer via FastCGI. Words from the input text are sent by Web/Application Server to AppServer for processing through a FastCGI component and returned back with marked misspelling or grammar problems and defined corrections.


WebSpellChecker Server Application
Web Components is set of various static files that are required for the WebSpellChecker application functioning. All these files are shipped with the standard package and installed automatically.
AppServer 5.0 is an application server that is responsible for combining all the components of the system together to provide the multi-language proofreading functionality.
Engines includes a list of integrated engines that are responsible for spelling and grammar checking, and thesaurus processes. These engines are shipped with the default installation package.

Dictionaries combines a list of various types of dictionaries either shipped with the package or created during the application operation and use.

There are three main categories of dictionaries available:

  • language dictionaries,
  • custom dictionaries,
  • user dictionaries.

AppServerX.xml is a configuration file which contains a list of settings for the WebSpellChecker application configuration. You can find a detailed description of all available parameters in the Configuring WebSpellChecker Server Parameters guide.

Logs is a logs folder that keeps a registry of events, processes, and messages that occur within the application.