You may often need to change AppServer properties, settings, and parameters to do the following:
To verify if WebSpellChecker AppServer works properly, you may need to run one or several of four AppServer commands described in this section:
There are three possible options how you can start AppServer on Windows-based environments.
Option A: Go to Windows Start –> All Programs –> WebSpellChecker –> AppServer –> Start WebSpellChecker Application Server.
Option B: Open Command Prompt –> Switch to [WebSpellChecker_Installation_Path]/AppServer –> Run AppServerX -start
Option C:
To start AppServer on Linux, run the start.sh script using the following command below:
sudo sh <WebSpellChecker_Installation_Path>/WSC/AppServer/start.sh |
Or your can also run the start.sh script from the AppServer directory:
/<WebSpellChecker_Installation_Dir>/WSC/AppServer/# sh start.sh |
There are three possible options how you can stop AppServer on Windows-based environments.
Option A: Go to Windows Start –> All Programs –> WebSpellChecker –> AppServer –> Stop WebSpellChecker Application Server
Option B: Open Command Prompt –> Switch to [WebSpellChecker_Installation_Path]/AppServer –> Run AppServerX -stop
Option C:
To stop AppServer on a Linux-based environment, run the stop.sh script from the AppServer directory:
sudo sh <WebSpellChecker_Installation_Path>/WSC/AppServer/stop.sh |
Or your can also run the stop.sh script from the AppServer directory:
/<WebSpellChecker_Installation_Dir>/WSC/AppServer/# sh stop.sh |
To verify if WebSpellChecker Server works properly, you need to start AppServer Service and check its version.
To verify the WebSpellChecker server version, use ?cmd=ver сommand:
http(s)://your_host_name:2880/?cmd=ver |
The port 2880 is the default port used by AppServer Service. |
If you specified a custom port number, use the next following link:
Here is an example of a correct version response for WebSpellChecker Server:
{"COPYRIGHT":"(c) 2000-2019 WebSpellChecker LLC","PRODUCT WEBSITE":"webspellchecker.com","PROGRAM VERSION":"x.x.x x64 master:xxxxxxx (xxxx) #xx"} |
Option B. Connection to the Service via FastCGI, SSRV.cgi component, and Web or Java Application Server
To verify the WebSpellChecker server version, use ?cmd=ver сommand:
http(s)://your_host_name/wscservice/script/ssrv.cgi?cmd=ver |
If you specified a custom port number for a web server or a Java application server, use the following link:
http(s)://your_host_name:port/wscservice/script/ssrv.cgi?cmd=ver |
Here is a correct version response for WebSpellChecker Server x.x.x where x.x.x is a current WebSpellChecker version number:
(c) 2000-2019 WebSpellChecker LLC All rights reserved. | |
Program name: | ssrv |
Program version: | x.x.x.x x64 master:xxxxxxx (xxx) #xx for Windows |
To verify if WebSpellChecker Server works properly, you need to start AppServer Service and check its status.
To verify AppServer service status of connection with engines (SpellCheck, Grammar Check, and Thesaurus), use ?cmd=status сommand:
http(s)://your_host_name:2880/?cmd=status |
The port 2880 is the default port used by AppServer Service. |
Here is a correct status response for Spell Check, Grammar, and Thesaurus engines of WebSpellChecker Server:
{ "Spell Check Engine": { "active": true }, "Grammar Check Engine": { "active": true }, "Thesaurus Engine": { "active": true } } |
To verify AppServer service status of connection with engines (SpellCheck, Grammar Check, and Thesaurus) for FastCGI, SSRV.cgi component, and web server, use the following command:
http(s)://your_host_name/spellcheck/script/ssrv.cgi?cmd=status |
Here is a correct status response for Spell Check, Grammar, and Thesaurus engines of WebSpellChecker Server for FastCGI:
Spell Check Engine is ACTIVE Grammar Engine is ACTIVE Thesaurus Engine is ACTIVE Please find below the description of the statuses that are received from SSRV component: 'ACTIVE' status means that an Engine works properly. 'NOT ACTIVE' status means that an Engine is not enabled or does not work properly. For more details and assistance, please contact the technical support team at [email protected]. |