PI17273: BUILD FORGE 8.0.0.1 ZLINUX INSTALL PLACES SERVICE-PLUGIN IN TEMP DIRECTORY INSTEAD OF SET SERVICES-PLUGIN DIRECTORY

Rational Build Forge Fix Pack 2 (8.0.0.2) for 8.0
Rational Build Forge Interim Fix 3 for 8.0.0.2
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 Interim Fix 1 for 8.0.0.2
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 installing Build Forge 8.0.0.1 under zLinux using the
  cmdline-install.sh, with plans to used an separate Application
  Server (Tomcat/WebSphere Application Server[WAS]), and setting
  the directory for the services plugin used for Rational Team
  Concert (RTC) integration, the services-plugin.jar file is
  placed under the Build Forge test directory.
  
  After the installation completes, the buildforge.conf files list
  the services-plugin directory that was specified during the
  installation, and the services-plugin.jar is expanded under the
  Build Forge temporary directory, but the Application server
  (Tomcat/WAS) is unable to find and load the plugin.
  
  Steps to reproduce:
  
  - Install Build Forge 8.0.0.1 under supported zLinux system.
  - During the question 'Enter the directory for the Build Forge
  Services Layer plugins' enter a directory different than the
  expected Build Forge temporary directory.
  
  ie:
  Enter the directory for the Build Forge Services Layer plugins:
  /opt/buildforge/temp/services-plugins
  
  - Configured the Build Forge temporary directory to the default.
  
  Enter the temporary storage path for the Services Layer:
  [/opt/buildforge/temp]
  
  
  Expected result:
  
  The Build Forge services-plugin.jar is placed under the
  directory specified under the installation and loaded under the
  Application server in question to allow the RTC/Build Forge
  integration to function.
  
  Actual result:
  
  The Build Forge services-plugin.jar is placed under the
  temporary directory (ie: /opt/buildforge/temp), while the
  buildforge.conf files are configured to expected the
  services-plugin to be under the directory specified during the
  installation.
  This causes the Application server is unable to load the
  services-plugin and the RTC/Build Forge integration will not
  function correctly.
  As builds started under RTC and executed under Build Forge will
  not be reported back to RTC, in which the RTC builds will run
  never ending.
  
  Workaround:
  
  Either update the buildforge.conf files to point the
  services-plugin setting to the Build Forge temporary directory,
  or copy the services-plugin jar and expanded directory to the
  specific directory set during the installation.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  After investigating the Linux  and Windows, there is no
  "directory for the Build Forge Services Layer plugins",
  there is a  temporary storage path(This is a physical
  directory on the server that runs your application server
  where we can temporarily store files and plugins) for the
  Services Layer:.
  

Problem conclusion

• Remove the  "directory for the Build Forge Services Layer
  plugins".  Use the "temporary storage path(This is a
  physical directory on the server that runs your application
  server where we can temporarily store files and plugins) for
  the Services Layer".
   The service plugin directory will be under "temp storage
  path"/services-plugins
  

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