How Can We Help?
< All Topics

Environment Variables

Environment Variables:

To store the values of the frequently used parameters environment variables are required. Setting and using placeholders instead of specifying the required values in the app’s code each time they are needed makes your application more portable and flexible. It brings even more convenience if these values may differ from one host to another.

There is a number of environment variables for the commonly used directories that are set by default at BitssCloud application servers – see the lists below.

BitssCloud also gives you the possibility to declare your own custom environment variables (user-defined parameters to be used with applications) by means of adding the needed values to a special config file and in such a way, keeping them out of the code. Inside this file, you can set placeholders for your folder’s names, user names, passwords, hostnames, IP addresses, etc instead of hardcoding their values to every file they are required in.

The most common way of adding your own custom variables to any of the servers in your BitssCloud environment is described in the Setting Custom Env Variables via SSH guide. Also, there is a separate instruction on setting custom variables and JVM options through the BitssCloud dashboard for Java app servers.

And the next section provides names and values for the predefined environment variables, grouped according to particular app servers. Feel free to use them while adjusting your apps.

Default Environment Variables

The following environment variables are set for Tomcat 6, Tomcat 7 and TomEE application servers:

VariableValue (server path)

The following environment variables are set for Glassfish 3:

VariableValue (server path)
logs  /opt/glassfish3/glassfish/domains/domain1/logs/

The following environment variables are set for Jetty 6:

VariableValue (server path)

Note: despite the names, temp and tmp directories are NOT automatically cleaned by BitssCloudsystem. 

Table of Contents