/etc/jdmk.security.template).
The text file is read when the engine is created. The Java DMK API objects that make the engine to be created are :
The USM configuration text file can be updated remotely using the USM Mib.
User that are configured in the Usm (jdmk.security file) text file are nonVolatile.
Usm Mib userEntry supported storage type values are : volatile or nonVolatile only. Other values are rejected and a wrongValue is returned)
- volatile means that user entry is not flushed in security file
- nonVolatile means that user entry is flushed in security file
- If a nonVolatile row is set to be volatile, it will be not flushed in the file
- If a volatile row created from the UsmMib is set to nonVolatile, it will be flushed in the file (if the file exist and is writable otherwise an inconsistentValue is returned)
- Since:
- Java DMK 5.1
getEngineTime
int getEngineTime()
- Gets the engine time in seconds. This is the time from the last reboot.
- Returns:
- The time from the last reboot.
getEngineId
SnmpEngineId getEngineId()
- Gets the engine Id. This is unique for each engine.
- Returns:
- The engine Id object.
getEngineBoots
int getEngineBoots()
- Gets the engine boot number. This is the number of time this engine has rebooted. Each time an
SnmpEngine
is instantiated, it will read this value in its Lcd, and store back the value incremented by one.
- Returns:
- The engine's number of reboot.
getUsmKeyHandler
SnmpUsmKeyHandler getUsmKeyHandler()
- Gets the Usm key handler.
- Returns:
- The key handler.
Copyright 1998-2007 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.