Download Release
March 22, 2018

IBM Rational Build Forge

Automate and accelerate build and release processes

Rational Build Forge 7.1.3

Product Release / Trial | August 30, 2011
This is not the most recent version. We recommend Rational Build Forge . This is made available for archival purposes and may contain bugs and/or security vulnerabilities. If you do download this version, it is being provided AS IS, without warranties of any kind, including the implied warranties of merchantability and fitness for a particular purpose. We strongly advise you review the support pages for this version and update the product or take actions recommended therein. Security bulletins contain instructions for the security vulnerability addressed therein, and may require upgrading to a newer version. Link to security vulnerability blog: IBM PSIRT blog.

Rational Build Forge 7.1.3 Release Notes

Fixed APARs

The following APARs are fixed in this IBM® Rational® Build Forge milestone. In the Milestone column, a blank entry means that the APAR was fixed for this milestone. Otherwise, the entry identifies the milestone where the APAR was fixed.




M3 PM18448 Pause a step using BuildForge APIs
PM22627 bfclient.conf is not pulled from the services layer
M3 PM27549 HTML in Notifications seems to rely on specific HTML elements being present
PM28488 Matched string in step log is not highlighted although log filter is matched and login user is Japanese.
M1 PM28732 Error Connection to agent timed out with use of .monitor
PM29372 Import of customer generated certificate, fails during install
PM30986 Build Forge installation does not indicated HTTPS used for login page by default
M3 PM33124 Console redirect fails when accessing console via login page under Internet Explorer
M3 PM33896 BF - clicking to a new step while editing a cloned step does not warn that changes will not be saved
M3 PM34281 Case insensitive filter on step log causes a services exception with DB2
PM34382 .scan -ignore still scans the directories that should be ignored.
M2 PM34492 Document Java hot->IP caching mechanism, and how to turn it off if desired
M2 PM34605 Job page does not refresh to show the purge has been executed
M3 PM35173 Unable to delete copied access group due to reference LDAP users
M3 PM35255 Re-submit: Pull Down variables with 50+ do not show Details
M2 PM35364 Build Forge dot command .stop will fail build when set to PASS
M3 PM35776 A sticky project emits a faulty error on the foreground log.
M2 PM35847 Build Forge agent fails to start on RHEL without IPv6 module after install
M3 PM35952 Clarify verbage on error window appearing when QuickStarting Projects
M2 PM36147 Adaptor not able to put multple lines into BOM
M3 PM36614 Build Forge AdminDB password is stored under database as plaintext
M3 PM38058 Client Side Validation of Server Side Security
M3 PM38059 Security alert for reflected Cross Site Scripting
PM38451 Build Forge LDAP user unable to login after bad password login
M3 PM38894 Error message is incorrect when step name is changed to duplicated name and the step has customized access authority.
M3 PM39101 Clustered engines run scheduled jobs twice
M3 PM39103 A project with two threaded steps each broadcast to 30 servers for a total for 60 steps hangs
M3 PM39118 Build variable using .date resets on every step SET - Reopen
M3 PM39539 .bset, .tset and .set are allowed on read-only variables
PM39561 Steps are skipped upon restart even though build owner has access to all steps
M3 PM39587 .scan step should treat working directory name with trailing space as non-exist directory
M3 PM40036 Project step is not updated when opened under multiple browser tabs/windows
PM40058 Log filter does not check RESULT attribute in step logs with BF or later.
PM40065 BF UI : A step shown with incorrect check mark in Job Steps tab of Start Project
PM40242 Cannot send system alert mail if alias is not specified.
PM40416 flexhelper-AIX-ppc64 missing when using WAS instead of Tomcat
PM41585 Project sticky tag is not being honored with adaptor link steps
PM41745 Inactive schedule purges cause automatic purging not to occur
PM42297 Ability to determine which Libraries or Projects are called inline by other Projects or Libraries.
PM42735 Save Environment check is active even when users do not have permission to edit environments
PM42746 Two builds can obtain the same semaphore
PM42751 bfdispatch.exe is accumulating thread handles indefinitely
PM42801 Use of TAILNORMALLOG in an adaptor causes the associated build to not purge on fail
PM42892 Perl does not execute with CLEARCASE_VIEW set
PM42985 Some special characters in EV value may cause created schedule could not be editable
PM43193 License is consumed after failing log in Management Console
PM43194 Error Message on Management Console is incorrect when all the licenses are consumed.
PM43477 Server layer events are not purged from DB automatically after upgrading to
PM43943 BFAgent can't work on Solaris 10 due to lack of
PM44932 Regression: Hard Run Limit set to Y errantly increments the build tag when kicked off by a schedule

Known issues

  • Documentation for integration with Rational Team Concert: please see the Build Forge Team Wiki on for complete information on integrating with RTC 2.x and RTC 3.0. Documentation in the Build Forge information center has been updated to clarify differences between integrating with versions 3.x and versions 2.x and 1.x.
  • Dashboard, License Seats: In Internet Explorer 7 and 8, a limitation in the browser prevents numbers from being shown on this dashboard.
  • The build number variable ($B) is not interpreted correctly if it is used in a schedule rather than a project. The value returned is "B" rather than the build number. Workaround: use .bset in a step to set a variable that uses $B. Example:
    .bset env "TESTDIR=Test2\${B}_${BF_D}_${BF_T}" 
  • Bad UI on Jobs page: Symptom - on some systems, the Job Notes and other links on the Jobs page do not work. Workaround: On line 630 of the functions.php file, remove the semicolon character ";".
    • On Windows systems: <bfinstall>\webroot\includes\functions.php
    • On UNIX and Linux systems: <bfinstall>/Platform/webroot/includes/functions.php
  • Step failure during failover in Oracle RAC: If the Oracle RAC database goes through a failover, a step in progress may fail. Specifically, if the step is performing a write operation when the failover occurs, Oracle RAC might not respond to Build Forge quickly enough for the step state to be determined. This issue was discovered during testing but is considered rare. Build Forge logs grow quickly during a failover as the system continues to poll the database.
  • Password encryption and reinstallation: If you have implemented password encryption and want to preserve user information when you delete and reinstall Build Forge, you must first back up the <bfinstall>/keystore directory and the <bfinstall>/bfclient.conf file. Restore those files in the new installation.

Documentation updates

The following items are corrections or updates to the Information Center.
  • Archive path when using Java 2 security in WebSphere Application Server. The path is listed as in the local file system as follows, which is correct for Windows systems:

    The correct path for UNIX and Linux systems is as follows:

  • _SUPPRESS_AGENT_OUTPUT_LOG: set this variable to 1 to prevent agent log data from being sent back to the engine. It differs from _SUPPRESS_LOG_OUTPUT, which causes the log data to be filtered out after it is sent back to the engine.
  • read_timeout directive for bfagent.conf: The agent can be configure to disconnect if it does not receive requests from the engine in the specified number of seconds. The default is 1800 seconds (30 minutes). Set the value to 0 to disable the timeout.

    The directive helps prevent client connection contacts from holding the port open if a legitimate engine request is not received. Some network port-scanning software behaves this way.

    Do not set very small values for this directive. Normal engine behavior may include gaps between requests of several minutes.

  • Additional AIX prerequisites: When using the MySQL database on AIX, you need to install the Connector/J driver and the 5.0-51a client drivers. Obtain them from the MySQL web site. The drivers are compatible with AIX version 6.1.
  • Broadcast step behavior on restarts: When a broadcast step is restarted, it does not broadcast. That setting applies only new new starts of the step. Upon restart the engine picks a single server at random for the step.
  • Audit logging encoding option: the correct flag is -E, rather than -e as listed in the Information Center. You can also use --encoding.
  • Pausing the engine: The correct values in the UI are "Yes" and "No," rather than "Y" and "N" as documented.