Publishing Property Changes

Changes made to properties are not propagated to the application until the changes are published. Application properties have a dynamic setting, which determines whether or not published changes to the application property will dynamically affect the system. If a property is defined as static, then published changes to this property will not take effect until the system is rebooted. The reason that static property changes do not take effect until reboot is that static properties contain information that cannot be updated while the application is running. An example of a static property would be 'curam.db.type=DB2', which indicates a connection to a DB2® database. This connection cannot be broken while the application is running. Thus, if the value is changed to 'curam.db.type=ORACLE', which indicates a connection to a Oracle® database, this change cannot be implemented until the server is rebooted.