The remote method invocation service of LexEVS (Distributed LexEVS) is being sunsetted. NIH/NCI no longer hosts this externally. If you choose to install this for your own service be aware that it will be deprecated in the near future. This section provides requirements, instructions, and troubleshooting information for installing the LexEVS Distributed environment.
- The Supported Platforms are the same for this environment as they are for the Local Runtime.
- Before installing the LexEVS Distributed environment you must have a LexEVS Local Runtime installed and working.
- It is not required that you load a terminology into the Local Runtime in order to complete the installation of the Distributed environment. However, using the APIs in the Distributed environment requires that a terminology be loaded into the Local Runtime.
- The Distributed environment has additional Prerequisite software beyond the Local Runtime. The additional web application server does not have install steps given in this guide. The web application server can be on the same server or a different server from the Local Runtime.
- Complete the #Downloading and Installing LexEVS Distributed steps below.
Once you have completed the additional prerequisite software install, the Distributed environment install steps, and the verification test as described in this guide then you should be ready to start using the Distributed 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 LexEVS Distributed
1. Download the latest version of the LexEVS Distributed WAR file from the right. You have a choice between WAR 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
Access to the downloads does not require an account. If you are having trouble downloading files then you may need to disable pop-up blockers or check any firewall settings at your site.
2. Shut down your application or servlet container. This presumes that you have already installed a web server as outlined in the LexEVS 6.x Prerequisite Software Supported to Include. 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.
3. Rename the WAR file. These files are distributed with an application server designation in their name for clarity while downloading them.
4. Copy the WAR file to the appropriate web application server directory, like this:
5. Create a text file named
6. (OPTIONAL) The
7. Adjust the
Testing LexEVS Distributed
1. Start your application or servlet container if it is not already started. The start command will be web server specific. See the documentation for your web server for information on how to do this.
2. Verify the installation by opening a browser to:
If you are using
If you see the Enterprise Vocabulary Services "Welcome to LexEVS" web page then you have successfully installed the LexEVS Distributed. Congratulations!
- If the Local Runtime environment is properly installed and tested then the Distributed environment should have few problems.
- If you receive deployment errors in JBoss and are unable to see the EVS home page then you may not have configured the properties attribute in JBoss's properties-service.xml.
- You may also need to adjust the path in lexevs.properties where lbconfig.props location is defined.
- We recommend no threading limits less than 512mb being applied when starting JBoss. (These would usually be configured as a JAVA_OPTS variable in a run.conf or similar file and would be set as follows: -Xss512M )
- We recommend a minimum heap size of -Xmx750m when starting JBoss and about 1000m per million entities loaded. (Also a JAVA_OPTS variable)
We recommend a minimum Perm Gen size of 256m.