YADE Installation
- YADE can be installed using the interactive installer GUI for Windows and Linux servers (with X-Servers).
- YADE can be installed from the command line using an installer parameter file.
1. Requirements
- Starting from release 1.9 an Oracle or openJDK Java Runtime Environment 1.8 or newer is required.
- Starting from release 1.6.4043 an Oracle Java Runtime Environment 1.7 or newer is required.
- Starting from release 1.3.7 an Oracle Java Runtime Environment 1.6 or newer is required.
2. Download YADE installer
- Download the YADE Client and transfer it to the server. You could use wget to download YADE directly on that server.
test@wilma:~/install> ls -la total 13763 drwxr-xr-x 2 test users 88 2014-05-22 11:24 . drwxr-xr-x 140 test users 18392 2014-05-22 11:24 .. -rw-r--r-- 1 test users 21997010 2014-12-19 19:35 jade_client.1.8.tar.gz
3. Unzip the YADE installer
test@wilma:~/install> gunzip jade_client.1.8.tar.gz test@wilma:~/install> tar xvf jade_client.1.8.tar jade_client.1.8/install_jade_client.txt jade_client.1.8/jade_client.1.8.jar jade_client.1.8/jade_client_install.xml jade_client.1.8/licence.gpl jade_client.1.8/setup.sh test@wilma:~/install> ls jade_client.1.8 test@wilma:~/install> cd jade_client.1.8 test@wilma:~/install/jade_client.1.8> ls -la drwxr-xr-x. 2 test users 4096 Jan 15 12:08 . drwxrwxr-x. 3 test users 4096 Jan 15 11:57 .. -rw-r--r--. 1 test users 1620 Dec 19 15:24 install_jade_client.txt -rw-r--r--. 1 test users 22123297 Dec 19 15:24 jade_client.1.8.jar -rw-r--r--. 1 test users 1173 Jan 15 12:08 jade_client_install.xml -rw-r--r--. 1 test users 17986 Dec 19 15:24 licence.gpl -rwxr-xr-x. 1 test users 2839 Dec 19 15:24 setup.sh
4. Prepare the installer parameter file
- Change the installpath tag in the jade_client_install.xml file and set the absolute installation path according to where you want to install YADE.
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!--
XML configuration file for YADE Client setup
If you call the setup with this XML file then
you accept at the same time the terms of the
GNU GPL 2.0 License agreement (see licence.gpl or
http://www.gnu.org/licenses/gpl-2.0.html)
-->
<AutomatedInstallation langpack="eng">
<com.izforge.izpack.panels.UserInputPanel id="home">
<userInput/>
</com.izforge.izpack.panels.UserInputPanel>
<com.izforge.izpack.panels.HTMLLicencePanel id="licence"/>
<com.izforge.izpack.panels.TargetPanel id="target">
<!-- SELECT THE INSTALLATION PATH
The path must be absolute!
Default paths are
/opt/sos-berlin.com/jade/client for Unix
C:\Program Files\sos-berlin.com\jade\client for Windows -->
<installpath>/home/test/sos-berlin.com/jade</installpath>
</com.izforge.izpack.panels.TargetPanel>
<com.izforge.izpack.panels.InstallPanel id="install"/>
<com.izforge.izpack.panels.ProcessPanel id="process"/>
<com.izforge.izpack.panels.FinishPanel id="finish"/>
</AutomatedInstallation>
5. Run the installer
- It is strongly recommended that you are not logged in as root
- It is not mandatory to install YADE with root permissions.
- The setup.sh script has the option -u
- If you use the option -u then the installer is started with the current user.
In this case, you have to make sure that this user has sufficient write permissions to create the installation path. - If you don't use the option -u then the installer calls sudo to get root permissions. The current user has to be configured as sudoer.
In this case the installation path is arbitrary.
- If you use the option -u then the installer is started with the current user.
Setup with option -u
[test@wilma jade_client.1.8-RC1]$ ./setup.sh -u jade_client_install.xml java -Dizpack.mode=privileged -jar ./jade_client.1.8.jar jade_client_install.xml [ Starting automated installation ] [ Starting to unpack ] [ Processing package: package.jade_client (1/1) ] [ Unpacking finished ] [ Starting processing ] +----------------------------------------------------------- | Update jar files in ./lib +----------------------------------------------------------- ... trying to delete obsolete jar files ... trying to install new SOS jar files ... trying to update 3rd-party jar files ... done +----------------------------------------------------------- | Change owner in /home/test/sos-berlin.com/jade/jade_client.1.8 to test +----------------------------------------------------------- ... nothing to do [ Processing finished ] [ Writing the uninstaller data ... ] [ Automated installation done ]
Setup without option -u
[test@wilma jade_client.1.8-RC1]$ ./setup.sh jade_client_install.xml sudo java -jar ./jade_client.1.8.jar jade_client_install.xml Password: [ Starting automated installation ] [ Starting to unpack ] [ Processing package: package.jade_client (1/1) ] [ Unpacking finished ] [ Starting processing ] +----------------------------------------------------------- | Update jar files in ./lib +----------------------------------------------------------- ... trying to delete obsolete jar files ... trying to install new SOS jar files ... trying to update 3rd-party jar files ... done +----------------------------------------------------------- | Change owner in /home/test/sos-berlin.com/jade/jade_client.1.8 to test +----------------------------------------------------------- ... the user group of "test" is "test". ... done [ Processing finished ] [ Writing the uninstaller data ... ] [ Automated installation done ]
6. Check YADE
test@wilma:~/install/jade_client.1.8> cd /home/test/sos-berlin.com/jade/jade_client.1.8 test@wilma:~/sos-berlin.com/jade> ls ThirdParty.txt Uninstaller bin examples lib licence.gpl logs test@wilma:~/sos-berlin.com/jade> cd bin/ test@wilma:~/sos-berlin.com/jade/bin> ls jade.sh jade4dmz.sh log4j.properties test@wilma:~/sos-berlin.com/jade/bin> ./jade.sh --version [main] INFO com.sos.DataExchange.SOSDataExchangeEngineMain - SOSDataExchange - Main routine started ... -- 1.8 (2014-12-19 13:22, revision 09c84ab471c46ee84989ed6f0a728ebd347ea1b2) Copyright 2003-2014 SOS GmbH Berlin