PM84510: RAF update.sh/update.bat script does not updated build.xml from older RAF environments with new

Rational Automation Framework 3.0.1
Rational Automation Framework Fix Pack 2 (3.0.1.2) for 3.0.1

APAR status

• Closed as program error.

Error description

• When upgrading or migrating a RAF environment pre-3.0 to 3.0
  version, the update.sh script does not update the environment
  build.xml file with new properties.
  The update.sh script does not update existing custom templates
  either.
  
  For example, the following WAS 7 environment cell build.xml file
  pre- upgrade appears as follows.
  
  WAS 7 Environment Cell build.xml
  
  ?project basedir='.' default='default'?
    ?description?
        Build file for cell WAS7Cell01
    ?/description?
  
    ?!-- Include cell configuraqtion properties --?
          ?property file='configure.properties'/?
  
    ?!-- Import WAS ND Configure tasks  --?
            ?import
  file='${RAFW_HOME}/product/actions/configure/was/70/nd/configure
  _was70_nd.xml'/?
  
          ?!-- Import WAS ND Deploy actions applicable to the cell
  scope  --?
          ?import
  file='${RAFW_HOME}/product/actions/deploy/was/70/nd/deploy_was70
  _nd.xml'/?
  
  ?/project?
  
  After executing the update.sh script, the build.xml is updated
  only under the configure action from 'configure_was70_nd.xml' to
  'configure_was70_nd_managed.xml'.
  
  ?project basedir='.' default='default'?
    ?description?
        Build file for cell WAS7Cell01
    ?/description?
  
    ?!-- Include cell configuraqtion properties --?
          ?property file='configure.properties'/?
  
    ?!-- Import WAS ND Configure tasks  --?
            ?import
  file='${RAFW_HOME}/product/actions/configure/was/70/nd/configure
  _was70_nd_managed.xml'/?
  
          ?!-- Import WAS ND Deploy actions applicable to the cell
  scope  --?
          ?import
  file='${RAFW_HOME}/product/actions/deploy/was/70/nd/deploy_was70
  _nd.xml'/?
  
  
  The update.sh does not updated the build.xml with the 'Import
  custom actions' and 'Import WAS ND model actions applicable to
  the cell scope' configuration.
  As seen under the available template build.xml file.
  
  Template WAS 7 Cell build.xml
  ?project default='default' basedir='.'?
          ?description?
        Build file for cell @CELL_NAME@
    ?/description?
  
          ?!-- include RAFW custom ant tasks, types, conditions
  and filters --?
          ?import file='${RAFW_HOME}/product/lib/core.xml' /?
  
          ?!-- Include cell configuraqtion properties --?
          ?property file='configure.properties'/?
  
          ?!-- Import custom actions  --?
          ?import file='build_local.xml' /?
  
          ?!-- Import WAS ND Configure tasks  --?
          ?import
  file='${RAFW_HOME}/product/actions/configure/was/70/nd/configure
  _was70_nd_managed.xml'
  /?
  
          ?!-- Import WAS ND Deploy actions applicable to the cell
  scope  --?
          ?import
  file='${RAFW_HOME}/product/actions/deploy/was/70/nd/deploy_was70
  _nd.xml'
  /?
  
          ?!-- Import WAS ND model actions applicable to the cell
  scope  --?
          ?import
  file='${RAFW_HOME}/product/actions/model/was/70/nd/model_was70_n
  d.xml'
  /?
  
  Steps to reproduce:
  
  - Migrate Build Forge/RAF 7.1.2.x environment to RAF 3.0.x.x
  installation.
  - Execute $RAFW_HOME/bin/update.sh script.
  
  Expected result:
  
  Migrated RAF environment build.xml files are updated as needed.
  
  Actual result:
  
  Migrated RAF environment build.xml files are partially updated
  as needed.
  
  Workaround:
  
  Manually update build.xml with additional configuration under
  respective template build.xml file.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During the upgrade to Rational Automation Framework v3.0.0.x
  the build.xml files in both existing configuration
  environments and in custom templates were not being updated
  to include the additional imports currently available in the
  latest product templates.  This caused some actions to no
  longer be found in scopes in which they used to exist as the
  new xml file in which they now exist was not being imported
  by the older, pre-existing build.xml files generated by
  older versions of the product.
  

Problem conclusion

• build.xml files for both existing configuration environments
  and custom templates are now updated as part of the update
  scripts which run at install time so that changes to the
  newer build.xml files are reflected in pre-existing
  build.xml files generated by older versions of the product.
  

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

  RATL AUTOMATION

• Fixed component ID

  5725E2600

Applicable component levels

• R300 PSN

     UP