Introduction
This document is a section of the Installation Guide.
This section provides requirements, instructions, and troubleshooting information for installing LexEVS Grid Services.
Preliminary considerations
- The [Supported Platforms] are the same for this environment as they are for the Local Runtime and the Remote API.
- Before installing the LexEVS Grid Services environment you must have both a [LexEVS Local Runtime] installed and a [LexEVS Remote API] working.
- Just like the Remote API install, it is not required that you load a terminology into the Local Runtime in order to complete the installation of the Grid Services environment. However, the Grid services are not very useful if they have nothing in the underlying Local Runtime to query against.
- This environment currently has no additional [Prerequisite Software] beyond that of the the Remote API.
- Complete the [Downloading and installing the LexEVS Data or Analytical Grid Services] steps below.
Once you have completed the Grid Services environment install steps and the verification test as described in this guide then you should be ready to start using the Grid Services features to meet the needs of your application. Not counting prerequisite software products the installation and verification should not take more than 30 minutes.
Downloading and installing the LexEVS Data or Analytical Grid Services
Step |
Action |
---|---|
1. Download the latest version of the LexEVS Analytical or Data Services ZIP file from the right. You have a choice between ZIP files tailored for JBoss or Apache Tomcat installations. The location you have chosen to save this on your computer will be referred to as the |
|
2. Unzip the file or files you have downloaded to {{ Unknown macro: {SAVE_DIRECTORY}
}} |
Unable to render embedded object: File (Warning.jpg) not found.
WARNING: Each ZIP contains a file by the same name. This is by design because you can not deploy the Data or Analytical Grid Services to the same server. Therefore you must do these one at a time or unzip them to multiple locations.
Note: Windows typically understands ZIP files and can extract files. Unix has an unzip
command. Other utilities can be used such as WinZip or 7-Zip. | Unable to render embedded object: File (Unzip_lexevs_services.png_) not found.. The command to do the shut down will be web server specific. See the documentation for your web server for information on how to do this. There may be many alternatives.
JBoss example:
Windows:
shutdown.bat -S
Unix:
./shutdown.sh -S
If you experience Java errors then the server may already be down. | [[Image:jboss_shutdown.PNG | frameless | center | 600px |
4. Create a directory for the web archive. Unknown macro: {WEB_SERVER_HOME}
{DEPLOYMENT_HOME}_* where _ _ is your application server home directory |
_
_ is the Web Archive deployment directory for your application server
JBoss example:
Windows:
c:\jboss-4.0.5.GA\server\default\deploy
Unix:
/jboss-4.0.5.GA/server/default/deploy
For example:
Windows:
mkdir wsrf.war
Unix:
mkdir wsrf.war
| [[Image:Create_wsrf_war_dir.png | frameless | center | 600px |
5. Unzip the |
JBoss example:
Windows:
From: c:\scratch\wsrf.war
To: c:\jboss-4.0.5.GA\server\default\deploy\wsrf.war
Unix:
From: /scratch/wsrf.war
To: /jboss-4.0.5.GA/server/default/deploy\wsrf.war
Windows does not see WAR files as compressed files, therefore you must obtain an unzip utility such as 7-zip or WinZip. In Unix you should be able to use the unzip command. | Unable to render embedded object: File (GridService_deploy.PNG_) not found.