PI06304: VARIABLES IN THE SSL.CLIENT.PROPS FILE ARE NOT HONORED BY THE MIGRATION CODE AS THE RUNTIME CODE DOES

APAR status

• Closed as fixed if next.

Error description

• Looking at the ssl.client.props the key and trust store paths
  
  have the ${CONFIG_ROOT} variable as part of its path.
  
  Further investigation shows that this variable is defined in the
  setupcmdline script.
  
  Given the fact that the runtime honors the variable in the props
  
  file, it should also be honored by the migration code.
  

Local fix

• Edit the ssl.client.props and setupcmdline scripts and hard
  code the paths to the profiles config directory of the source
  data, then run WASPreUpgrade.
  This will prevent WASPostUpgrade from failing to find the
  CONFIG_ROOT.
  Check the sas.client.props files as well.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Migration Tools where use of the     *
  *                  $CONFIG_ROOT variable cannot be resolved.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Property files can use the variable     *
  *                      ${CONFIG_ROOT} in defining a paths.     *
  *                      The WebSphere runtime honors this       *
  *                      variable because it is set by the       *
  *                      setupCmdLine script.  Migration         *
  *                      however relies on the variables.xml     *
  *                      for resolving most variables.           *
  *                      However, property files do not use      *
  *                      the variables.xml files to resolve      *
  *                      variables. When migration encounters    *
  *                      this variable in a properties file,     *
  *                      it cannot resolve the path.  If used    *
  *                      with a security related path, it        *
  *                      causes connection problems and the      *
  *                      migration process fails.                *
  ****************************************************************
  * RECOMMENDATION:  Migration should honor the ${CONFIG_ROOT}   *
  *                  variable from the setupCmdLine script as    *
  *                  it does the ${WAS_HOME} and                 *
  *                  ${USER_INSTALL_ROOT}.                       *
  ****************************************************************
  APAR PI06304 is being closed FIN with concurrence from the
  submitting customer. This means that a fix to this APAR is
  expected to be delivered from IBM in a release which is being
  developed at the time that the APAR was closed. The latest
  release of the product to exit development at the time this
  APAR was closed was:
  WebSphere Application Server 8.5.5.
  

Problem conclusion

Temporary fix

Comments

• This issue has existed since the migration tools were
  released, this is the first time we encountered this issue.
  Customer used circumvention with no problems and agreed that
  it could be fixed in a future release.
  
  In general the path with the property would be copied over as
  is.  But in this instance the migration code needed to resolve
  the path to a security file in order to make a connection to
  the repository.
  

APAR Information

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

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

Fix information

Applicable component levels

• R700 PSY

     UP

• R800 PSY

     UP

• R850 PSY

     UP