BuildForge Help

Documentation Updates for the Installation Guide

This section describes updates or changes that were made to the Build Forge Installation Guide after the 7.0.2 documentation was shipped.

The information documented here supersedes information in the installation guide.

Installation Guide: DB2 Setup, db2 CREATE DATABASE Statement

In the DB2 Setup sections for both installation on Windows and installation on UNIX and Linux, the example scripts show a db2 CREATE DATABASE statement that shows parameters in the wrong order. The correct statement is shown here.

$ db2 CREATE DATABASE BFT ALIAS BUILD USING CODESET UTF-8 TERRITORY US AUTOCONFIGURE USING MEM_PERCENT 40 APPLY DB ONLY

Installation Guide: DB2 Express Database and User Name Now Created by Installer

If you choose to install the provided DB2 Express database when you install the Management Console, you no longer have to create a database user name/password in Windows prior to installing the Management Console.

The installer creates a DB2 Express database build and user name for you. You must supply a password for the user name. (You can change the user name but not the build database name.)

The DB2 Express database and user name are created for you only if you create them at installation time and only if you select the Use IBM Rational supplied database option.

Installation Guide: Complete Post-Upgrade Tasks (UNIX/Linux)

The following step was added to this topic as Step 3 for users upgrading from version 3.8 to version 7.0 or later.

3. Copy the JDBC driver (jar file only) for your database to $CATALINA_HOME/common/lib. See the Install JDBC Drivers topic in the Build Forge Installation Guide

Installation Guide: Upgrading from Version 7.0 or Later on UNIX or Linux

The following step was added to this topic as Step 11:

11. Copy the JDBC driver (jar file only) for your database to $CATALINA_HOME/common/lib. See the Install JDBC Drivers topic in the Build Forge Installation Guide

Installation Guide: Upgrading from Version 7.0 or Later on UNIX or Linux

For the task prerequisite, the following path and command information was corrected:

Stop the Tomcat server. Execute the shutdown command in the Tomcat bin directory:
cd $CATALINA_HOME/bin
./shutdown.sh

Installation Guide: Install JDBC Drivers (SQL Server 2005 JDBC driver required)

JDBC Drivers are required to enable standard reports and the separately licensed Quick Report option.

The installation guide does not state that Build Forge requires the SQL Server 2005 JDBC driver.

For Microsoft SQL Server, Build Forge requires the SQL Server 2005 JDBC driver. Earlier versions of this driver are no longer supported. If you installed an earlier version of this driver, replace it with the 2005 driver.

Installation Guide: Install JDBC Drivers (only JDBC jar file required)

JDBC drivers for your Build Forge database are required to enable standard reports and the separately licensed Quick Report option.

The installation guide instructs you to download and unzip the JDBC drivers for your database to $CATALINA_HOME/common/lib.

Instead, copy the jar file for the JDBC driver to $CATALINA_HOME/common/lib.

Installation Guide: Upgrading from Version 7.0 or Later on UNIX or Linux

If you are upgrading from 7.0.1 or later, you must remove the quickReport and rbf-services directories. After removing the directories, restart Tomcat. Do the following after Step 10, copying the war file for the reporting application:

Stop the Tomcat server if it is running:

./catalina.sh stop

Delete the quickReport and rbf-services directories from the Tomcat webapps directory:

cd $CATALINA_HOME/webapps

rm -r quickReport

rm -r rbf-services

Restart the Tomcat server:

cd $CATALINA_HOME/bin

./catalina.sh start

Installation Guide: Installing the Agent on System i Platforms

The CRTJOBD statement in the example for configuring the system to run the bfagent at start up changed:

CRTJOBD JOBD(BFAGENT/BFAJOBD) JOBQ(BFAGENT/BFAJOBQ) TEXT('Build Forge Agent autostart') 
USER(BFAGENT) RQSDTA('CALL PGM(QP2SHELL) PARM(''/bin/bfagent'' ''-s'')')

Installation Guide: Running the Agent on System i

In the example showing how to set library lists for all projects and steps run on the System i host, the job name was changed from BLDFRGAGNT to BFAJOBD:

The agent specifies this job description in its startup routine. For example, if it were named BFAJOBD, the line in the system startup routine would be as follows:
ADDAJE SBSD(BFAGENT/BFAGENT) JOB(BFAGENT) JOBD(BFAGENT/BFAJOBD)

Installation Guide: Running the Agent on System i

The statement about running as the QSECOFR user to allow users to login as any user is incorrect. If the agent is run as the QSECOFR user, authentication does not work and the agent is unusable. The following statement was removed from the installation guide:

You can run the agent as the QSECOFR user. That allows the agent to use System Authentications to log in with a different user name and password. See bfagent.conf for more information.

It was replaced with the following statement:

To allow for authentication, configure the the magic_login setting in the BFAgent.conf file. (Do not run the agent as the QSECOFR user.)

Installation Guide: Installing the Agent on System i Platforms

Added the following step:

5. Edit the shell configuration in the bfagent.conf file. Set the shell value to /bin/sh.

Installation Guide: BFAgent.conf Reference (Shell Setting Required for System i)

Added the following update for System i configuration:
shell shell_name [options]
System i: /bin/sh

Installation Guide: Database Requirements (Perl module list incomplete)

Two Perl modules required for the Management Console for 7.0.2 are not listed in the Perl modules table:
  • HTTP::Request
  • LWP::UserAgent

Installation Guide: Database Requirements (db_tcp_port not documented)

The 7.0.2 version of the installation guide does not document the following requirement. (This requirement will be added in a subsequent release of the installation guide.)

Build Forge assumes that you are using the default connection port for your database. If you are using another port number, you must add the db_tcp_port keyword to the buildforge.conf file and set its value to the correct database connection port.

Installation Guide: Configuring Tomcat for Build Forge

The 7.0.2 version of the installation guide does not document the following requirement. (This requirement will be added in a subsequent release of the installation guide.)

The Apache Tomcat server is required to support the services-layer APIs for Java and Perl.

When configuring Build Forge for Tomcat, you must copy the rbf-services.war file to the Tomcat webapps directory. The following step was updated to reflect this requirement:

3. Copy the .war files for the reporting application and the services-layer APIs for Java and Perl.

$ cd /usr/local/buildforge/tomcat/webapps
$ cp quickReport.war $CATALINA_HOME/webapps
$ cp rbf-services.war $CATALINA_HOME/webapps

Default Installation Path for Windows Management Console

In the installation guide and in the online help documentation, the default installation path for the Management Console on Windows changed to:
C:\Program Files\IBM\Build Forge
Previously, it was:
C:\Program Files\BuildForge

Default Installation Path for Windows Agent

In the installation guide and in the online Help documentation, the default installation path for the Agent on Windows changed to:
C:\Program Files\IBM\Build Forge\Agent
Previously, it was:
C:\Program Files\BuildForge\Agent
Note: The variable part of the installation directory is C:\Program Files\IBM\Build Forge. The installer always appends the Agent directory to the path.