Black Box ET0010A, ET1000A, EncrypTight, ET0100A Policy Refresh Timing, PEP Communications Timing

Modifying the ETKMS Properties File

Policy Refresh Timing

The policy refresh timing controls the timing between the initiation of a renew keys and policy lifetime and the deletion of the expired keys. The following entries specify the timing for the policy refresh.

#### Policy refresh timing

#Policy refresh delete delay (1-120 minutes) minutesAfterRefreshExpireBeforeDelete=30

#Policy refresh buffer for daily refresh (1-120 minutes) maxBufferMinutesBeforeDailyRefresh=20

minutesAfterRefreshExpireBeforeDelete Specifies in minutes the time the PEP waits after a Refresh before it deletes the old keys.

maxBufferMinutesBeforeDailyRefresh	Specifies in minutes the earliest time in which a
	Refresh is issued.

PEP Communications Timing

The following parameters define the ETKMS to PEP communications timing.

####General Communication Timing

# Initial wait (1-1200 Seconds) initialRetryWaitTime=300

#Retry wait (1-1200 Seconds) retryWaitTime=300

#Retry count (1-100) retryCount=1

#Max retry wait (1-1200 Seconds) maxRetryWaitTime=300

#### PEP Extended Communication Timing

#Initial PEP retry wait (1-1200 Seconds) initialPEPRetryWaitTime=360

#PEP retry count before starting final wait (1-100) initialPEPRetryCount=12

#Final PEP retry wait (1-1200 Seconds) finalPEPRetryWaitTime=600

These entries divide the timing into general communications timing and extended communications timing.

The general timing defines a group of communication attempts defined by retryCount. The time between the first communication attempt and the second is defined by the initialRetryWaitTime. The time between the second and third attempt is defined by maxRetryWaitTime. This continues for n communications attempts as defined by retryCount or until maxRetryWaitTime is reached. This process is repeated as defined by the extended communications parameters.

258 EncrypTight User Guide