Difference between revisions of "InContext Server Installation"
(→Checking InContext Server Installation) |
|||
Line 1: | Line 1: | ||
= Checking InContext Server Installation = |
= Checking InContext Server Installation = |
||
− | The typical G11n system is installed using the '''Lingoport Stack Installer |
+ | The typical G11n system is installed using the '''Lingoport Stack Installer'''. |
− | If that is the case, then the InContext Server should have been '''installed''' at that time. |
+ | If that is the case, then the InContext Server should have been '''installed''' at that time. If your system was updated with '''Lingoport Stack Updater''', the InContext Server needs to be installed manually. |
To check: |
To check: |
Revision as of 17:34, 6 May 2019
Contents
Checking InContext Server Installation
The typical G11n system is installed using the Lingoport Stack Installer. If that is the case, then the InContext Server should have been installed at that time. If your system was updated with Lingoport Stack Updater, the InContext Server needs to be installed manually.
To check:
$sudo systemctl status incontext-server
and output:
● incontext-server.service - InContext Server Service Loaded: loaded (/etc/systemd/system/incontext-server.service; disabled; vendor preset: disabled) Active: inactive (dead)
If the output says something about the service not found, then it needs to be installed following the Installation Steps below.
If the service exists, then proceed to the Running the InContext Server below and start the service.
Installing Manually
InContext Server Installation Requirements
The InContext Server requires the following:
- Java 8
- MySQL 5.5.3+
Since the Lingoport Suite already requires Java and MySQL, the only additional requirement for the InContext Server is Tomcat. The InContext Server provided by Lingoport installs Tomcat 8.5.x.
InContext Server Files
There are three files that comprise the InContext Server. The Lingoport InContext Server automated installation process will put these files in the appropriate location.
- incontext-server.war
- incontext-server.sh
- IncontextServerConfig.groovy
The incontext-server.war is the server itself and must be placed under the tomcat/webapps directory.
The incontext-server.sh file is a script for starting/stopping the InContext Server and must be configured and placed in the tomcat directory.
The IncontextServerConfig.groovy file is the configuration file for the InContext Server and must be configured and placed in the tomcat directory.
Installation Steps
1. Download and unzip the IncontextServer-<version>.zip file from our SFTP site.
2. Change directory: cd incontext-server
3. Modify install.conf to set the values required by the install. Any information left blank will be prompted by the install script.
MYSQL_ROOT_PASS
- this is the password that was used or created by the Stack Installer or Stack Updater.INCONTEXT_MYSQL_USER / INCONTEXT_MYSQL_PASS
- this is a new MySQL username and password.INSTALL_TOMCAT_HERE='/usr/local/tomcat'
- Unless there is reason to change the location, leave it at the default.
4. Run the install script (note you must have sudo privileges): ./install.sh
. If it is successful, one should see:
Incontext Server successfully installed.
Running the InContext Server
To start the InContext Server:
$sudo systemctl start incontext-server
Then browse to: http://yourserverurl:8081/incontext-server
To stop the InContext Server:
$sudo systemctl stop incontext-server
To check the status of the InContext Server:
$sudo systemctl status incontext-server
Next Steps
To continue installing InContext for Translation go to: InContext Capture Installation
For information on how to proceed after installation, please see the: InContext Server Users Guide