PI25452: UPGRADING BUILD FORGE 8.0.0.2 WITH WAS INTEGRATION USING IM 64-BIT FAILS

Rational Build Forge Fix Pack 3 (8.0.0.3) for 8.0
Rational Build Forge Fix Pack 4 (8.0.0.4) for 8.0
Rational Build Forge Fix Pack 5 (8.0.0.5) for 8.0
Rational Build Forge Fix Pack 6 (8.0.0.6) for 8.0
Rational Build Forge Fix Pack 7 (8.0.0.7) for 8.0
Rational Build Forge Fix Pack 8 (8.0.0.8) for 8.0
Rational Build Forge Fix Pack 9 (8.0.0.9) for 8.0
Rational Build Forge Fix Pack 10 (8.0.0.10) for 8.0
Rational Build Forge Interim Fix 1 for 8.0.0.10
Rational Build Forge Fix Pack 11 (8.0.0.11) for 8.0
Rational Build Forge Interim Fix 1 for 8.0.0.11
Rational Build Forge Fix Pack 12 (8.0.0.12) for 8.0
Rational Build Forge Fix Pack 13 (8.0.0.13) for 8.0
Rational Build Forge Fix Pack 14 (8.0.0.14) for 8.0
Rational Build Forge Fix Pack 15 (8.0.0.15) for 8.0
Rational Build Forge Interim Fix 1 for 8.0.0.15
Rational Build Forge Fix Pack 16 (8.0.0.16) for 8.0
Rational Build Forge Fix Pack 17 (8.0.0.17) for 8.0
Rational Build Forge Fix Pack 19 (8.0.0.19) for 8.0
Rational Build Forge Fix Pack 18 (8.0.0.18) for 8.0
Rational Build Forge Fix Pack 20 (8.0.0.20) for 8.0
Rational Build Forge Fix Pack 21 (8.0.0.21) for 8.0
Rational Build Forge Fix Pack 22 (8.0.0.22) for 8.0

APAR status

• Closed as program error.

Error description

• When attempting to upgrade Build forge 7.1.x that has been
  configured to use a separate application server, upgrading to
  Build Forge 8.0.0.2 fails.
  This is caused by the update.res response file for the internal
  installer "main" is configured with the incorrect setting
  "tomcat_modify = y", which causes the internal installer to fail
  when attempting to copy the JDBC from the tomcat directory.
  
  ie:
  
  Attempt to stop the service
  Looking for: mysql-connector-java-5.0.8-bin.jar
  Copy failed for
  /opt/buildforge/server/tomcat/common/lib/mysql-connector-java-5.
  0.8-bin.jar
  
  Since Tomcat was not initially installed, the directory does not
  exist.
  This causes the internal installer to fail, and the upgrade
  Under the Installation Manager to be marked as pass for an
  incomplete upgrade.
  
  Steps to reproduce:
  
  - Install Build Forge 7.1.3.x with the option to supply separate
  application server.
  - Attempt to upgrade to Build Forge 8.0.0.x.
  
  Expected result:
  
  - Upgrade completes without issue.
  
  Actual result:
  
  - Upgrade fails under the internal installer, but the
  Installation Manager upgrade is marked as completed.
  - The Build Forge installed files have not been changed, but
  Installation Manager list Build Forge 8.0.0.x as the installed
  version.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * UPGRADING BUILD FORGE 8.0.0.2 WITH WAS INTEGRATION USING IM  *
  * 64-BIT FAILS                                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The issue was fixed in Build Forge 8.0.0.3 release
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  RATIONAL BUILDF

• Fixed component ID

  5724S2700

Applicable component levels

• R800 PSN

     UP