Installing on Linux
Follow the instructions below to install the binary distribution of any WSO2 product on Linux from the command line.
Before you proceed to install the product, ensure that the Installation Prerequisites are satisfied.
Establish an SSH connection to the Linux machine or log in on the text Linux console.
Step 1. Obtain Installation Pack
Download the latest version of the program (for downloading instructions, refer to Obtaining the Product section).
Step 2. Extract the Archive
After the download is complete, extract installation files to your home directory. For example,
unzip wso2cep-2.0.x.zip
Step 3. Set up JAVA_HOME
JAVA_HOME
environment variable set up is needed to run WSO2 products. The variable points at the directory where the Java™ Development Kit (JDK) is installed on the computer.
Reference
Environment variables are global system variables accessible by all the processes running under the operating system.
Edit BASHRC file in your home directory to add the JAVA_HOME
environment variable. To set up JAVA_HOME
, perform the following steps.
1. Open the BASHRC file in your favorite Linux text editor - vi, emacs, pico, or mcedit.
2. Add the following two (2) lines at the bottom of the file as shown in the example below.
export JAVA_HOME=/usr/java/jdk1.6.0_25 export PATH=${JAVA_HOME}/bin:${PATH}
3. Save the file.
Tip
If you do not know how to work with text editors in Linux SSH session, run the following command:
cat >> .bashrc
Paste the string from the clipboard and press "Ctrl+D."
4. In order to verify the effective JAVA_HOME
variable set up, execute the following command:
echo $JAVA_HOME
The system returns the JDK installation path.
Step 4. Running the Product
1. Establish a SSH connection to the Linux server or log in to the text Linux console.
2. Go to <PRODUCT_HOME>/bin
, where "<PRODUCT_HOME>" is the actual folder where the product's distribution files are stored.
3. Execute the following command to start the server:
sh ./wso2server.sh
We do not recommend starting WSO2 products as a daemon, because there is a known issue that causes automatic restarts in the wrapper mode. Instead, you can configure the heap memory allocations in the wso2server.sh script and run it using the nohup command. For example:
nohup ./wso2server.sh &
4. The operation log is displayed. For example,
If the server is started and running, a message appears as "WSO2 Carbon started in 'n' seconds."
Step 5. Stopping the Server
Copyright © WSO2 Inc. 2005-2014