Page Comparison

...

Administration and Fulfillment System Changes

1. Administrators should Do not make any changes in Aspenware Commerce admin Administration when scaled out

   1. If an admin makes any change in Aspenware Commerce when scaled out, it will only take effect on one application service/site in real time. 

      1. The other scaled out sites will not be updated with the change until the cache expires on that machine or an action is performed on that machine that causes the cache to clear.

         1. For example, if product inventory is cached for 5 minutes

         then the longest any machine will have to wait to

         1. , then all instances will see updated values

         is

         1. in 5 minutes (some could see it sooner, but

         it could be sooner

         1. all will see it after the cache expires).

         2. Please see Static Cache Guidelines below for information about cache duration.

   2. Some settings, such as Queue-It API key, customer ID, and secret, require an application service restart after any change (whether scaled or not).   See Queue-It Release Guide

   3. Customer profile details

      1. If customer profile details are changed in the fulfillment system (RTP|ONE or Siriusware) while the guest is shopping, the changes won’t be seen until the cache is refreshed.

...