Symantec Access Management

Hello -

can some one has any community tip or wiki available on the concept "JournalRefresh" on Policyserver . How does this work and how this value is being set ?

There are two parameters in the registry under ObjectStore, JournalRefresh and JournalDelete. (These will be set based on the settings from the PS management Console.)

JournalRefresh (in seconds): Amount of time in seconds you want SiteMinder to wait before it applies committed administrative changes to data in the cache.

The default value is 60 seconds.

JournalDelete(in hours): Amount of time in hours that you want SiteMinder to wait before it deletes journal entries. The journal keeps track of all administrative changes. Journal records are kept in the Policy Store. On the smconsole these settings are configured in the Administrative Journal under the Advance tab.

Say nLastTime is the time when Policy Server last checked for the updated server commands. Then, then by default, (when ServerCommandTimeDelay key is not present) when Policy Server checks for the updated Journal, it fetches all

the server commands with TimeStamps later than nLastTime.

ServerCommandTimeDelay: This key is not present by default. When this key is used it tells the policy server to fetch all the server commands which are current and older than the current time (in seconds) as defined in the ServerCommandTimeDelay.

Note : The MaxTimeDeltaBetweenServers setting replaces the ServerCommandTimeDelay setting. Use theMaxTimeDeltaBetweenServers and remove the other setting.

Note that the JournalRefresh time should be long enough to fit into your ServerCommandTimeDelay time window.

Hi Ujwal ,

Thank you , that was helpful !

As well , on what basis you think the value will be decided if you have multiple servers with fail-over stores ?

MaxTimeDeltaBetweenServers : The value for this is generally determined based on the time difference that you have between two policy servers. For e.g if the difference is 2 minutes, you would keep this to 120 seconds.

JournalRefresh time then should be adjusted (if needed) to be long enough to fit into your ServerCommandTimeDelay time window.