Skip to main content
Pentaho Documentation

Starting BA Server on Linux

Overview

Quisque mattis rutrum ligula et pellentesque. Pellentesque massa enim, pulvinar quis quam quis, aliquet dapibus augue. Aliquam feugiat suscipit turpis, nec ultrices dolor adipiscing ut.

Modify the Tomcat Linux Startup Script

The Tomcat startup script must be modified to include the CATALINA_OPTS variable. CATALINA_OPTS indicates the amount of memory to allocate. It also indicates where Pentaho licenses are installed. 

  1. Make sure the Tomcat web application server is not running by opening a Terminal window and typing ps -A at the prompt. If the server is running, stop it.
  2. Use a text editor to open the startup.sh file, which is in the pentaho/server/biserver-ee/tomcat/bin directory.
  3. Locate the #Check that target executable exists line and add this code above it.
DI_HOME=<your pentaho directory>/pentaho-solutions/system/kettle
  1. Add the Java option pentaho.installed.licenses.file to CATALINA_OPTS. You need to modify the setting of the CATALINA_OPTS variable at the end of the file by adding the java option.  See the following example.
export CATALINA_OPTS="-Xms4096m -Xmx6144m -XX:MaxPermSize=256m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dpentaho.installed.licenses.file=$PENTAHO_INSTALLED_LICENSE_PATH -DDI_HOME=$DI_HOME"
  1. Save and close the file.

Modifying the JBoss Linux Startup Script

The JBoss startup script must be modified to include the JAVA_OPTS variable. JAVA_OPTS indicates the amount of memory to allocate. It also indicates where Pentaho licenses are installed. Specific instructions on how to modify the startup script depend on your operating system.

  1. Make sure the JBoss web application server is not running by opening a Terminal window and typing ps -A at the prompt. If the server is running, stop it.
  2. Use a text editor to open the standalone.conf file. The file is located in the bin subdirectory of your JBoss home directory.
  3. Modify the Xms memory settings in the JAVA_OPTS line to be at least 4096 MB or more, if you have the resources and are concerned with performance. Change the Xmx value to at least 6144 MB.
  4. Add the following options to the JAVA_OPTS line: -Djava.awt.headless=true -Djava.io.tmpdir=/tmp/ -Dpentaho.installed.licenses.file=$PENTAHO_INSTALLED_LICENSE_PATH
# Specify options to pass to the Java VM.
    if [ "x$JAVA_OPTS" = "x" ]; then
        JAVA_OPTS="-Xms4096m \
        -Xmx6144m \
        -XX:MaxPermSize=256m \
        -DDI_HOME=$DI_HOME
        -Dsun.rmi.dgc.client.gcInterval=3600000 \
        -Dsun.rmi.dgc.server.gcInterval=3600000 \
        <b>-Djava.awt.headless=true \
        -Djava.io.tmpdir=/tmp/ \
        -Dpentaho.installed.licenses.file=$PENTAHO_INSTALLED_LICENSE_PATH

You may need to adjust these settings for your environment. For instance, if you do not have a /tmp/ directory, you may want to change that setting to /var/tmp/ or some other location.

  1. Save and close the file.
  2. Locate the bin subdirectory in the JBoss home directory and open the standalone.sh file with a text editor. 
  3. Find the section for # Setup JBOSS_HOME and add this after it.
INSTALL_HOME==`cd "$DIRNAME/../.."; pwd`
DI_HOME=$INSTALL_HOME\pentaho-solutions\system\kettle
  1. Save and close the file.

Start BA Server

  1. Run the startup script for your web application server by launching one these files.
    • Linux Tomcat: Launch the startup.sh file. The file is in the Tomcat bin directory.
    • Linux JBoss: Launch the standalone.sh file. The file is in the JBoss bin directory.
  2. Open a web browser and enter this URL: http://localhost:8080/pentaho. The User Console Log On window appears. Note that you will be prompted to install a license. Information on how to do that appears in the Set Up BA Server instructions.

After you install your licenses, there are a few things you will need to do to configure your new server