Filter
Top Products
Base Directory for Storing Operational State Data
EncrypTight User Guide 257
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%d [%t] %-5p %c - %m%n
## Console logging
#log4j.rootLogger=ALL,stdout
#log4j.appender.stdout.Threshold=INFO
#log4j.appender.stdout=org.apache.log4j.ConsoleAppender
#log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
#log4j.appender.stdout.layout.ConversionPattern=%d %t %-5p %c - %m%n
Base Directory for Storing Operational State
Data
This entry defines the database for storing the keys and current metapolicies.
# Base directory for storing operational state data
KeyDistDbLoc=..
Peer ETKMS and ETPM Communications Timing
The following entries define the communications timing between the ETKMS and peer ETKMSs and the
ETKMS and the ETPM.
#### KeyDist/ETPM Communications Timing
# Wait for peer key after deploy (1-1200 Seconds)
waitForPeerKeyTime=30
# Time to wait for status check to complete (1-3600 Seconds)
retryStatusCheckTime=315
# Check for message period in milliseconds (20-3000 mS)
recheckMessageWaitTimeMS=1000
# Time to wait for additional keys from peer KeyDist after key is received in
seconds (1-1200 S)
waitForReceivedKeyTime=5
waitforPeerKeyTime
Specifies in seconds how long the ETKMS waits to get any keys from
other peer ETKMSs.
retryStatusCheckTime
Specifies in seconds the time the ETKMS waits to receive status from
PEPs. If the status is not received from a PEP within the defined time,
an error status indication appears on the ETPM screen next to the
appropriate PEP.
recheckMessageWaitTimeMS
Specifies in milliseconds the elapsed time the ETKMS waits to check
for a command from the ETPM.
waitForReceivedKeyTime
Specifies in seconds how long the ETKMS should wait for additional
keys from a peer ETKMS.