Note |
---|
Before you begin, please see our compatibility matrix to find out if this version of the product is fully tested on LinuxLinux or OS X. |
Follow the instructions below to install ES on Linux or OS X.
Install the required applications
- Establish a SSH connection to the Linux machine or log in on the text Linux console. You should either log in as root or obtain root permissions after you log in via the
su
orsudo
command. Be sure your - Log in to the command line (Terminal on Mac).
- Ensure that your system meets the Installation Prerequisites. Java Development Kit (JDK) is essential to run the product.
...
- If you have not done so already, download the latest version of the product as described in Downloading the Product.
Extract the archive file to a dedicated directory for the product, which will hereafter be referred to as
<PRODUCT_HOME>
.
Setting up JAVA_HOME
You must set your JAVA_HOME
environment variable to point to the directory where the Java Development Kit (JDK) is installed on the computer.
...
- In your home directory, open the BASHRC file in your favorite Linux text editor, such as file (.bash_profile file on Mac) using editors such as, vi, emacs, pico or mcedit.
Add the following two lines at the bottom of the file, replacing
/usr/java/jdk1.6.0_25
with the actual directory where the JDK is installed.Code Block On Linux: export JAVA_HOME=/usr/java/jdk1.6.0_25 export PATH=${JAVA_HOME}/bin:${PATH}
The file should now look like this:
On OS X: export JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Save the file.
Info If you do not know how to work with text editors in a Linux SSH session, run the following command:
Code Block cat >> .bashrc
Paste the string from the clipboard and press "Ctrl+D."
To verify that the
JAVA_HOME
variable is set correctly, execute the following command:Code Block On Linux: echo $JAVA_HOME
The system returns the JDK installation path.
On OS X: which java If the above command gives you a path like /usr/bin/java, then it is a symbolic link to the real location. To get the real location, run the following: ls -l `which java`
Setting system properties
...
- Set the properties from a script
Setting your system properties in the startup script is ideal, because it ensures that you set the properties every time you start the server. To avoid having to modify the script each time you upgrade, the best approach is to create your own startup script that wraps the WSO2 startup script and adds the properties you want to set, rather than editing the WSO2 startup script directly. - Set the properties from an external registry
If you want to access properties from an external registry, you could create Java code that reads the properties at runtime from that registry. Be sure to store sensitive data such as, username and password to connect to the registry in a properties file, instead of in the Java code and secure the properties file with the secure vault.
Info | ||
---|---|---|
| ||
When using SUSE Linux, it ignores |
...