Migrate Business Rule Changes to the system without an Application Restart

Currently in the PAS system when the application.mode in the PAS.properties file is set to “Production” the application does not regularly refresh the cache for control reasons. This means that when Rules Palette migrates configuration to an environment where the application.mode is set to “Production”, the PAS application must be manually restarted in order to acknowledge and utilize the new configuration. To avoid this situation, the PAS system has been modified to clear cache based on specific settings activated by release management when a package is successfully deployed.

This is a requirement that is part of OIPA’s capability to be 24x7 available. This is especially critical in the context of group administration since coverage changes within a group could be made from OIPA and such changes may include rule changes from rules palette which need to be migrated more often than usual rule migrations which would follow a periodic schedule

Currently when a migration package is deployed to an OIPA environment, the application must be restarted manually to clear the cache and pick up the new configuration. This is applicable to all deployments to all OIPA environments.

OIPA must be enhanced to accept a request to clear the OIPA cache when application.mode is set to “PRODUCTION”.

Two components are needed: a new sequence record and a new application property for all OIPA property files.An AsSequence record named ConfigurationUpdatedGMT.

 The record contains a GMT marking completion of a Rules Migration.

 The request for a cache clearing is associated to Palette's update of this sequence record.

A property in called application.configurationCacheTimeout.

 This will denote the time in minutes that OIPA should keep objects in cache before checking for updates.

 A value of 0 or less or the property is missing (compatibility): OIPA will never check for updates to ConfigurationUpdatedGMT.

 A value greater than 0: OIPA will check for updates to ConfigurationUpdatedGMT after the specified number of minutes has passed.

OIPA process to determine when to clear the cache.

OIPA keeps in cache the value of ConfigurationUpdatedGMT from AsSequence.

 This value must be obtained from AsSequence upon application restart.

 The value in the cache is updated to the value in AsSequence after the cache is cleared.

When the application.mode indicates "PRODUCTION" and objects have been held in the configuration cache for the requisite number of minutes indicated by application.configurationCacheTimeout:

 If OIPA's cached value of ConfigurationUpdatedGMT is equal to the value of ConfigurationUpdatedGMT from AsSequence, the configuration cache is left untouched.

 If OIPA's cached value of ConfigurationUpdatedGMT is less than the value of ConfigurationUpdatedGMT from AsSequence, the configuration cache is cleared.

 When the cache is cleared, OIPA stores the new value of ConfigurationUpdatedGMT from AsSequence in the cache.

 Clearing the configuration cache forces OIPA to go to the database to fetch rules and configuration data (no change to existing functionality).

     
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. About Oracle Insurance | Contact Us