Content

First, make sure that your Rational Build Forge console has been stopped. You can verify this by examining the service in the Services control panel, or by looking at the process list for a 'buildforge.exe' executable.

Upgrading Apache:

First, download the latest 2.2.x Win32 Binary including OpenSSL version of the Apache httpd server from the Apache Web site.

The Windows binary distributions of the Apache httpd server is only available as a 'msi' installer package, so there will need to be some prep-work before proceeding. Browse to the directory that Build Forge is installed to, by default, this is "C:\Program Files\IBM\Build Forge", and rename the "Apache" directory to "Apache-old".

Launch the Apache httpd installer by double-clicking on the downloaded filename.

The default options are fine for all pages until it prompts for the "Destination Folder." At this point, change the destination to be "C:\Program Files\IBM\Build Forge\Apache" (Adjusting if Build Forge was installed in a different location) and continue with the installation process.

Once the installer completes, it will install itself as a service and start the Apache2.2 service, this will need to be stopped and disabled via the Services Control Panel, since Apache will be started and stopped by the Build Forge Service. The installer will also put a "Monitor Apache Services" application in the "Startup" folder in the Windows Start menu, this should be removed as well.

Copy the httpd.conf file and the ssl subdirectory from Apache-old\conf to the "new" Apache\conf directory.

Upgrading Tomcat:

First, download the latest 5.5.x or 7.0.x version of Apache Tomcat from the Apache web site (5, 7).

As of Build Forge version 7.1.2.3 & 7.1.3.1, Tomcat 7.0.14, Tomcat 7.0.26 as of 7.1.3.3, and Tomcat 7.0.55 as of 7.1.3.6.

For the purposes of this exercise, it is easiest to work with the Binary Core distribution packaged in the zip file.

Extract the zip file and rename the resulting top level directory to be simply "tomcat". Move the new "tomcat" directory to be under the newly installed Apache from the previous section.

Copy rbf-servcies.war and BuildForegeHelp.war files from the Apache-old\tomcat\webapps directory to the "new" Apache\tomcat\webapps directory.

Copy the icu4j-3_6.jar and JDBC driver for your database (Oracle: ojdbc14.jar, MySQL: mysql-connector-java-5.<version>.jar, IBM DB2: db2jcc.jar and db2jcc_license_cu.jar, MS SQLServer: sqljdbc.jar) from the Apache-old\tomcat\common\lib directory to the "new" Apache\tomcat\common\lib directory.

Copy the server.xml file from the Apache-old\tomcat\conf\server.xml to the "new" Apache\tomcat\conf directory, overwriting the existing file.

This concludes the Tomcat upgrade.

Upgrading PHP:

Download the latest 5.2.x or 5.3.x Thread Safe version of PHP for Windows from the PHP archive site. Just like for Tomcat, it will be easier to deal with the .zip version.

As of Build Forge version 7.1.2.3 & 7.1.3.1, PHP 5.3.6, and PHP 5.3.6 as of 7.1.3.4.

Uncompress the archive that was downloaded. Rename the top-level directory to be simply "php". Move the new "php" directory to be under the newly installed Apache from the first section.

Copy the php.ini file from Apache-old\php to the "new" Apache\php directory.

If Apache has also been upgraded, copy the files libeay32.dll and sslea32.dll from the Apache-old\bin directory to the Apache\bin directory, overwriting the existing files.

If the console is backed by Oracle, MySQL, or Microsoft SQL Server, the upgrade is complete.

If the console is backed by IBM DB2, download the php_ibm_db2 module from this compressed file. Extract the archive and copy the resulting php_ibm_db2.dll file into the "new" Apache\php\ext directory.

Now that everything has been upgraded, it is safe to start the Rational Build Forge console service again and test for functionality. Once things have been tested and proven to work, it is safe to move it back into production.