Changed configuration property values do not take effect

If you encounter an issue where configuration properties are not being picked up by your Unica Campaign application, you can disable caching as described in this procedure.

You change a configuration property but you do not see the expected change in application behavior.

Configuration property values for Unica Campaign and Unica Platform are cached to improve performance. This can cause old values to be used.

Set generic JVM arguments in the web application server where Unica Platform is deployed to disable caching.

  1. Set the following JVM argument, which disables the Hibernate L2 cache.

    -DUNICA_PLATFORM_CACHE_ENABLED=false

    By default, this value is set to true, which provides the best performance.

  2. Set the following JVM argument, which enables local caching.

    This improves performance when the Hibernate cache is disabled.

    -DUNICA_PLATFORM_LOCAL_CACHE_ENABLED=true

    When this local caching mechanism is enabled, configurations are updated at 60 minute intervals. If you want configuration changes to be picked up immediately, you must restart the application server.