Apache Tomcat installation and configuration

Installation Manager installs and configures Apache Tomcat as the application server for Build Forge. Using the provided Apache Tomcat application server is the quickest way to configure an application server for Build Forge.

As an alternative to the standard configuration, you have the option to use an existing Apache Tomcat instead of the one provided by Build Forge. This section describes the prerequisite software, pre-installation setup, installation, and post-install requirements for this alternative. The instructions provided assume that you have experience setting up and configuring Apache Tomcat.

Software prerequisites

Install the jar file for the JDBC driver

Download and unzip the JDBC driver for your database.
Important: The JDBC driver download may contain many files and subdirectories. Locate the jar file for the JDBC driver and copy the jar file only to $CATALINA_HOME/common/lib.

$CATALINA_HOME is the Tomcat installation root and must be set as an environment variable. See the installation documentation for your JDBC driver.

Configuring your Apache Tomcat server in Installation Manager

These instructions identify the information that you need to configure Apache Tomcat through Installation Manager.

  1. Shut down Apache Tomcat.
    Important: Before you start Installation Manager, Apache Tomcat must be stopped.
  2. Start Installation Manager.
  3. On the Start page, click Install.
  4. Follow the instructions in the Installation Manager wizard to install the product.
  5. On the Application Server Configuration page, click Yes to configure your own application server.
    Check list: Application server configuration
    Field Description
      Redirection URL Enter the host name and port number of your application server. You must specify rbf-services as the context path. For example: http: | https://<app_server_host>:<app_server_port>/rbf-services.
      Specify the directory where you want to install the BF Services Plug-ins Specify a directory local to the application server host. Installation Manager installs the Build Forge services layer application plug-in extensions in this directory. The user who is running the application server must have read, write, and execute permission to this directory.
    Note: In previous versions of Build Forge, it was necessary to specify the WAR deployment directory. In Build Forge 7.1.2, the WAR deployment directory is automatically set to bfinstall/PrepForExternal.
  6. Complete installation through Installation Manager.

Post-installation configuration of Apache Tomcat

After you have completed installation through Installation Manager, complete the following post-installation steps.

  1. You must manually add the buildforge.conf file to the rbf-services.war file.

    The location of the rbf-services.war is dependant upon your operating system. UNIX and Linux place this file in /opt/buildforge/PrepForExternal; Windows places this file in C:\Program Files\IBM\Build Forge\PrepForExternal. See Updating the buildforge.conf file and complete the relevant steps.

  2. Increase JVM heap size for the Apache Tomcat server.

    Set the JVM maximum heap size option -Xmx to 1024 M.

    Use the CATALINA_OPTS or the JAVA_OPTS environment variable in catalina.bat or catalina.sh to set this JVM option.

  3. Before you start Build Forge, start Apache Tomcat:

    $CATALINA_HOME/bin/catalina.sh start

    .

Feedback