Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update the list of options that were added with the release WSC 5.5.0


Tip
Before you begin:



Panel

Table of Contents
stylenone


1. Create Configuration File

Before you run the automated_install.pl script, you need to prepare a special configuration file and specify proper values for all the required installation parameters. This information will be used by the script for the automated installation of the WebSpellChecker application on your server.

1.1. Configuration File Syntax

Info
  • Configuration file has a simple structure resembling *.ini files. 
  • Each row of the file should contain one parameter with an assigned corresponding value.
  • You are allowed to use indentation, spaces and tabs and add blank lines.
  • You can comment some of the parameters using a hash sign “#” at the very beginning of the row with a parameter name (e.g. #activate_license = 0).

This is an example of a simple configuration file that can be used for the automated installation of the application on a Linux-based server with utilizing Apache HTTP Server assuming that you will be using the WProofreader product or Web API over HTTPS.

Code Block
titleinstall_config.ini
install_path = opt/WSC/ 
rewrite_old_installationproducts = 1
file_owner = 33:33
service_host
protocol = 1
certificate_file = https://your_host_name:443/spellcheck
web_server_type  = 1
apache_install_mod_fastcgi/opt/WSC/cert/cert.pem
certificate_key_file = /opt/WSC/cert/key.pem
certificate_password = ***************
service_port = 2880
domain_name = localhost
web_port = 443
virtual_dir = wscservice
web_server_type  = 1
apache_auto_enable_modules = 1
activate_license = 1
#licenselicense_ticket_id = ***************

1.2. Configuration File Parameters

In the table below, you will find a list of all available parameters and their possible values that you can used in the configuration file. Some of the parameters are mandatory and must be defined. The rest of the parameters are optional. If you do not define values for the optional parameters, they will be either auto-defined by the script or the default values will be used accordingly. 

The parameter defines a hostname, protocol, virtual directory and port which will be used to access the application.

#Parameter

Parameter Type

Default ValuePossible ValuesDescription
1install_pathOptionalopt/WSC/
  • opt/WSC/
  • Any other appropriate location on the server
The parameter defines the installation path for the application.
2rewrite_old_installationOptional1
  • 0 – Do not create a backup file
  • 1 – Create a backup file (WSC.bak)
The parameter is responsible for a backup file creation. If you have an existing copy of the application in the specified install_path, the script will reserve the whole folder in a WSC.bak file.
3file_owner

Mandatory

33:33
  • user:group (e.g. 33:33)

The parameter sets permissions for the application. It should define the files ownership, a user and group in the user:group format.

4productsMandatory1
  • 1
  • 2
  • 3
  • 4
service_hostMandatory
  • 5

5install_samplesOptional1
  • 0 – Do not install Demo Samples and Documentation.
  • 1 – Install Demo Samples and Documentation.

6protocolMandatory1
  • 1 – HTTPS
  • 2 – HTTP

7certificate_fileMandatory


8certificate_key_fileMandatory


9certificate_passwordOptional


10service_portMandatory2880

11domain_nameMandatorylocalhost

12web_portMandatory443 or 8443


  • 443
  • 80
  • 8443
  • 8080
13virtual_dirMandatorywscservice

14
Note

You shouldn't forget to indicate a port number when setting a service_host parameter. You may use any available port except 2880. It is used by WebSpellChecker Application Server.

5web_server_typeMandatory1
  • 1 – Apache HTTP Server
  • 2 – Java Application Server (Apache Tomcat, Oracle WebLogic Server, Oracle GlassFish Server, etc.)
  • 3 – Other
The parameter specifies a type of web or application server which will be used for the application server running.15path_to_jvmOptional


166activate_licenseOptional1
  • 0 – Skip the license activation step.
  • 1 – Run the license activation step.
The parameter defines whether to run or not to run the license activation process. You can skip the license activation step if you already have a license activated or you prefer to proceed with the license activation step later.717license_ticket_idOptional
  • You valid license ticket ID. It can be a trial (30 day) or a commercial license (1 year).
The parameter specified a License Ticket ID that will be used during the license activation procedure.818apache_versionOptionalCurrent Apache HTTP Server version installed
  • 2.2.x
  • 2.4.x
The parameter defines the current version of Apache HTTP Server.919apache_config_dirOptionalCurrent Apache HTTP Server configuration directory
  • /etc/apache2
  • /etc/apache2/conf.d
The parameter defines location of the Apache HTTP Server configuration file (httpd.conf). It can be autodefined by the installation script.1020apache_install_mod_fastcgiOptional0
  • 0 – Do not install a generic mod_fastcgi module shipped with the installation package.
  • 1 – Install a generic mod_fastcgi from the package.

The parameter installs a generic mod_fastcgi module which is shipped with the installation package. 

Excerpt Include
IN:_include_mod_fastcgi_apache_webserver
IN:_include_mod_fastcgi_apache_webserver
nopaneltrue

Note

This parameter is needed in case of the installation of WSC Dialog plugin for CKEditor 4.


2111apache_auto_enable_modulesOptional1
  • 0 – Do not enable extra modules.
  • 1 – Enable all required extra modules.
The parameter enables additional Apache HTTP Server mod_mime and mod_headers modules. They are required for a proper work of the application.1222restart_apacheOptional0
  • 0 – Do not restart Apache HTTP Server.
  • 1 – Restart Apache HTTP Server.
The parameter is responsible for restart of Apache HTTP Server. It is required for changes to take effect.

2. Run Automated Install Script

As soon as a configuration file with all the required parameters defined, you need to run the automated_install.pl script with the install_config.ini configuration file as a first parameter as follows:

Code Block
languagepowershell
themeEmacs
$ sudo ./automated_install.pl install_config.ini

OR

Code Block
languagepowershell
themeEmacs
$ sudo perl automated_install.pl install_config.ini


Note
titleTroubleshooting

If you specified a non-existing parameter in the configuration file, the automated installation will instantly fail and throw an error message indicating an incorrect parameter. Moreover, with an incorrect  parameter, the script may suggest possible valid parameters and their default values. However, if there is an error in a specified value, the installation will fail only on the specific step and might not give you a clear message for error handling.

3. Activate License

If you assigned “1” as a value for the activate_license parameter, the installer will attempt to activate a license automatically using a License Ticket ID.

Note

The automatic license activation mode requires the Internet connection available on the machine where you are trying to install WebSpellChecker.

Otherwise, you need to proceed with the license activation procedure according to the License Activation on Linux manual manually.

4. Configure Grammar Engine

Excerpt Include
IN:_include_wsc54x_server_configure_grammar_linux
IN:_include_wsc54x_server_configure_grammar_linux
nopaneltrue

5. Integrate WebSpellChecker

Excerpt Include
IN:_include_wsc54x_server_integrations_products
IN:_include_wsc54x_server_integrations_products
nopaneltrue