BuildForge Help

Post-Installation Setup

This section describes what you need to do after installing Build Forge on Windows. You need to perform the steps in this section only if you are setting up an existing database to be used by a Windows-based Management Console.

Install JDBC Drivers

Download and unzip JDBC drivers for your database. 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 driver for instructions.

Check PATH Variable

The PATH environment variable needs to include the path to database client or driver DLLs. Check PATH manually for these databases: For other databases (Microsoft SQL Server, Oracle, Sybase), installing the client or setting up the ODBC connection takes care of this requirement.

Identify Proxy Server

Optional: this step is needed only if the Management Console needs to use a proxy server to access its database. PHP needs to be configured to use the proxy server.

Perl Driver Setting for Oracle 9

This step is needed only for a Management Console using an Oracle 9.x database.

The ora_ph_type parameter in <bf-install>/db.ini must be set to a value that does not cause the driver to strip trailing blanks. The setting ora_ph_type=96 is recommended. If set to a value that strips trailing blanks (for example, SQL_VARCHAR), you see an error when running Build Forge: DBD::Oracle::st execute failed: ORA-01400: cannot insert NULL into ("BLDFORGE"."BF_RESULT"."BF_ENV") The problem does not occur with Oracle 10.

DB2CODEPAGE Setting for DB2

This step is needed only for a Management Console using a DB2 database. It is not needed if you are using the DB2 Express database provided.

You must set DB2CODEPAGE=1208 in the OS environment in order to display international characters correctly on non-English systems.