837871e12425577ebe5d6f129d18ea78dd0e640eAllan FosterBuilding The OpenSSO MIB
837871e12425577ebe5d6f129d18ea78dd0e640eAllan FosterThe OpenSSO MIB for monitoring is supplied in SUN_OPENSSO_SERVER_MIB.mib
837871e12425577ebe5d6f129d18ea78dd0e640eAllan Fosterin the opensso/products/amserver/resources/mib directory (along with this
837871e12425577ebe5d6f129d18ea78dd0e640eAllan FosterThe monitoring sources are generated using the MibGen utility, taking
837871e12425577ebe5d6f129d18ea78dd0e640eAllan FosterSUN_OPENSSO_SERVER_MIB.mib as input. The existing files in
837871e12425577ebe5d6f129d18ea78dd0e640eAllan Fosteroptnsso/products/amserver/source/com/sun/identity/monitoring are extensions
837871e12425577ebe5d6f129d18ea78dd0e640eAllan Fosterof these generated class files. One exception is the
837871e12425577ebe5d6f129d18ea78dd0e640eAllan FosterSUN_OPENSSO_SERVER_MIB.java file, where the generated file has been
837871e12425577ebe5d6f129d18ea78dd0e640eAllan FosterThe "am-mib" target in opensso/products/build.xml does the following:
837871e12425577ebe5d6f129d18ea78dd0e640eAllan Foster 1. invokes com.sun.jdmk.tools.MibGen on SUN_OPENSSO_SERVER_MIB.mib,
837871e12425577ebe5d6f129d18ea78dd0e640eAllan Foster directing sources to ${amserver.built.dir}/mib
837871e12425577ebe5d6f129d18ea78dd0e640eAllan Foster 2. copies ${amserver.built.dir}/mib/*.java to