Page History

You may often need to change the properties of AppServer or change the Server AppServer settings and parameters, for example:

• configure personal user dictionaries,
• exclude the words from the dictionaries,
• apply changes made to your Web Servers or Java Application ServersAppServer.  

To verify if WebSpellChecker AppServer works properly, you may need to run several AppServerXrun one of four AppServer commands described in this section.

Anchor
startAppServerWindowsLinux startAppServerWindowsLinux

Starting AppServer on Windows and Linux

...

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:

1. Go to Windows Start –> Control Panel –> Administrative Tools –> Services.
2. Find WebSpellChecker Application Server Service on the list of all services.
3. Click Start.

To start AppServer on Linux, run the start.sh script using the following command below:

sudo sh <WebSpellChecker_Installation_Path>/WSC/AppServer/start.sh

...

Anchor
stopAppServerWindowsLinux stopAppServerWindowsLinux

Stopping AppServer on Windows and Linux

...

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:

1. Go to Windows Start –> Control Panel –> Administrative Tools –> Services.
2. Find WebSpellChecker Application Server Service on the list of all services.
3. Click Stop.

Run the stop.sh script to stop AppServer using the following command below:

sudo sh <WebSpellChecker_Installation_Path>/WSC/AppServer/stop.sh

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

Checking AppServer Version

To verify if WebSpellChecker Server works properly, you need to start AppServer Service and check its version.

Option A (Direct connection to the AppServer Service):

Use the following link: 

http(s)://your_host_name:2880/?cmd=ver

If you specified a custom port number for the AppServer Service, use the next following link: 

...

Checking AppServer Version

To check the AppServer version, use the following commands: 

...

http(s)://your_host_name:2880port/?cmd=ver 

...

ver

Option B (Connection to the Service via FastCGI, SSRV.cgi component and Web Server):

Use the following link: 

http(s)://your_host_name/spellcheckwscservice/script/ssrv.cgi?cmd=ver 

...

ver

If you specified a custom port number for a Web Server, use the following link: 

http(s)://your_host_name:port/wscservice/script/ssrv.cgi?cmd=ver

Correct version response for WebSpellChecker Server 5.5.x on a Windows server looks the following way:

Checking AppServer Status 

To verify if WebSpellChecker Server works properly, you need to start AppServer Service and check its status.

Use the following link to check the connection to the Service via FastCGI, SSRV.cgi component, and Web Server

...

Checking AppServer Status 

To check the AppServer status, use the following commands: 

...

:

http(s)://your_host_name:2880//spellcheck/script/ssrv.cgi?cmd=ver

...

status

Accessing Default Demo Samples

To access the default Demo Samples, use the following link:

http(s)://your_host_name/spellcheckwscservice/script/ssrv.cgi?cmd=statussamples/