Page Comparison

...

...

Follow the instructions below to install the required applications and the WSO2 product SS on Linux or Mac OS X.

Install the

...

required applications

1. Establish a an 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 login via su or sudo command.
2. Be sure your system meets the the Install Installation Prerequisites, and then install the following applications:
   . Java Development Kit (JDK) Install Apache Maven (required only if you want to build the product from the source code or run samples)is essential to run the product.  

Installing the

...

product

1. If you have not done so already, download the latest version of the product SS as described in in Downloading the Product. 
   

2. Extract the archive file to a dedicated directory for the product, which will hereafter be referred to as <PRODUCTas <SS_HOME>.

Setting JAVA_HOME

You must set your your JAVA_HOME environment  environment variable to point to the directory where the Java Development Kit (JDK) is installed on the computer.

...

1. In your home directory, open the BASHRC file in your

...

1. favourite Linux text editor, such as vi, emacs, pico

...

1. or mcedit.

...

1. Add the following two lines at the bottom of the file,

...

1. replacing /usr/java/jdk1.6.0_

...

1. 25 with the actual directory where the JDK is installed.

   Code Block
   export JAVA_HOME=/usr/java/jdk1.6.0_25 export PATH=${JAVA_HOME}/bin:${PATH}

   The file should now look like this:

   Image Modified

...

1. 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".

...

...

1. To verify that

...

1. the JAVA_

...

1. HOME variable is set correctly, execute the following command:

   Code Block
   echo $JAVA_HOME

   Image Modified

   The system returns the JDK installation path.

Setting system properties

If you need to set additional system properties when the server starts, you can take the following approaches:

• 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 the secure vault.

You are now ready to to run the product.