JR55762: Stagingprop utility fails to propagate the access control policy data of a newly published store into production database

APAR status

• Closed as program error.

Error description

• For new WebSphere Commerce V8 environments (that were not
  migrated from V7), you might encounter propagation errors when
  you run the stagingprop utility.
  In V8, WebSphere Commerce's instance creation splits the keys
  for the access control policy tables based on the type of
  instance:
  -For staging instances, the generated keys are in the middle and
   upper range
  -For production instances, the generated keys are in the lower
  range
  This key splitting causes the same bootstrap access control
  policy data to have different primary keys in the staging
  instance and in the production instance. During store publish,
  new access control policy data is created but the store's access
   control policies have references to the bootstrap access
  control policies from instance creation. When the stagingprop
  utility is run, it fails in propagating the store's access
  control policy data because it is a direct copy of data.
  However, the store's access control policies are pointing to the
   parent bootstrap access control policies which have different
  primary keys in production than in staging.
  

Local fix

• See
  http://www.ibm.com/support/knowledgecenter/SSZLC2_8.0.0/com.ibm.
  commerce.admin.doc/refs/rssstagepropfailacp.htm
  

Problem summary

• USERS AFFECTED:
  WebSphere Commerce Version 8 environments that are not migrated
  from Version 7, and have instances that were created on 8.0.0.8
  or earlier.
  
  PROBLEM ABSTRACT:
  Stagingprop utility fails to propagate the access control policy
   data of a newly published store into production database
  
  BUSINESS IMPACT:
  Cannot deploy a published store successfully from a staging
  environment to the production environment.
  
  RECOMMENDATION:
  

Problem conclusion

• Updated code to ensure that instance creation does not split the
   keys for access control policy tables.
  
  The propagation exception errors will not occur for new
  instances that are created after you apply 8.0.0.9 or later, or
  8.0.1.1 or later.
  For users who created staging instances on Fix Pack 8 and
  earlier, you need to replace the access control policy data that
   is on your production instance.
  
  For more information, see
  http://www.ibm.com/support/knowledgecenter/SSZLC2_8.0.0/com.ibm.
  commerce.admin.doc/tasks/twosynchstagingwithproduction.htm
  

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

  WC BUS EDITION

• Fixed component ID

  5724I3800

Applicable component levels

• R800 PSY

     UP