This step-by-step guide is intended to outline the main steps for the WebSpellChecker application upgrade and reinstallation on the same server (hardware). 

1. Stop AppServer

First step that you need to perform is to stop WebSpellChecker Application Server of the existing installation.


Stop AppServer on a Windows server

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:

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


Stop AppServer on a Linux server

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

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

2. Uninstall WebSpellChecker

Prior to installing the most recent version of the application on the same server, you need properly uninstall the existing copy of the application and backup all your custom settings including custom/user dictionary files


Uninstall WebSpellChecker on Windows

Choose between two options below to uninstall the application on Windows-based environments.

Option A:

  • Go to the WebSpellChecker installation folder.
  • Execute unins000.exe to uninstall the existing copy of the application.

Option B: 

  • Go to Windows Start –> Control Panel –> Program and Features.
  • Find WebSpellChecker on the list of the installed program.
  • Click Uninstall.


Uninstall WebSpellChecker on Linux

Run the next command to uninstall the application on Linux-based environments:

sudo rm -rf <WebSpellChecker_Installation_Path>/WSC

Prior to uninstalling, make sure you created a backup of the license file (license.xml). By default, the license file location is <WebSpellChecker_Installation_Path>/WSC/AppServer/license.xml.

3. Install New Version

Install a new version of the application referring to one of the manuals below.

 Installing WebSpellChecker Application on Windows...

 Installing WebSpellChecker Application on Linux...


Important: If you are reinstalling/upgrading the application on the same server, you must skip the License Activation step

  • On Windows-based environments the license is stored in the Windows Registry and will be applied automatically.
  • For Linux-based environments, you need manually recover your <WebSpellChecker_Installation_Path>/WSC/AppServer/license.xml from the previously saved backup.

4. Start AppServer

Once you completed all the upgrade/reinstallation steps, you need to start WebSpellChecker Application Server of your new installation.


Start AppServer on Windows

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:

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


Start AppServer on Linux

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

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

5. Verify Operability

First of all, you need to check the application version and status. The version check will confirm the exact version of the application that you are running. The status check will provide you the health statuses of the main application engines: Spell Check, Grammar, Thesaurus.

  • Version: http(s)://your_host_name:[port]/spellcheck/script/ssrv.cgi?cmd=ver
  • Status: http(s)://your_host_name:[port]/spellcheck/script/ssrv.cgi?cmd=status

In addition to the version and status checks, you have to ensure that integrated spell/grammar checking functionality works properly in your web-system after the migration. Go to your web-system and check the controls where you expect to have spell/grammar checking.