BEA-WEBLOGIC-MIB :: domainLibrarySecurityDDModel

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsBEA-WEBLOGIC-MIBdomainLibrarySecurityDDModel

domainLibrarySecurityDDModel

Module: BEA-WEBLOGIC-MIB

OID (symbolic): BEA-WEBLOGIC-MIB::domainLibrarySecurityDDModel

OID (numeric): 1.3.6.1.4.1.140.625.900.1.16

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-only

Description: The security model that is used to secure a deployed module. To set this value, you can use the weblogic.Deployer command-line tool, the Deployment Assistant in the Administration Console, the WebLogic Scripting Tool (WLST), or some other JMX client. If you deploy a module using one of the previously mentioned tools and you do not specify a security model value, the module is secured with the security realm's default model ( see {@link weblogic.security.RealmMBean#getSecurityDDModel RealmMBean SecurityDDModel}). If you deploy a module by modifying the domain's config.xml file and restarting the server, and if you do not specify a security model value for the module in config.xml, the module is secured with the DDOnly model, which is the default value of this AppDeploymentMBean attribute. In summary, the order of precedence for the value of this attribute is as follows: If you deploy a module using a runtime deployment utility, the order of precedence is: The value set by the deployment utility. The value set as the security realm's default security model. If you deploy a module by modifying config.xml and restarting the server, the order of precedence is: The value that you specify for the module in config.xml. The default value of this AppDeploymentMBean SecurityDDModel attribute.

What is domainLibrarySecurityDDModel?

This OID stores the security realm model used to protect the deployed module. The value is set via command-line tools, the Deployment Assistant, or WLST; if not specified, the realm's default model is applied. Example: 'XACMLAuthorization' indicates the module uses XACML-based authorization; 'SimpleSecurityModel' uses basic realm authentication.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.140.625.900.1.16
snmpwalk -v2c -c public <target> BEA-WEBLOGIC-MIB::domainLibrarySecurityDDModel

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.140.625.900.1.16.1
snmpget -v2c -c public <target> BEA-WEBLOGIC-MIB::domainLibrarySecurityDDModel.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> domainLibrarySecurityDDModel.1

Start monitoring BEA/Oracle WebLogic Server (Java EE application server) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BEA-WEBLOGIC-MIB::domainLibrarySecurityDDModel OID value, configure state conditions and alerts, and monitor any BEA/Oracle WebLogic Server (Java EE application server) from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
Numeric OIDNameModule
1.3.6.1.4.1.140beaBEA-WEBLOGIC-MIB
1.3.6.1.4.1.140.625wlsBEA-WEBLOGIC-MIB
1.3.6.1.4.1.140.625.900domainLibraryTableBEA-WEBLOGIC-MIB
1.3.6.1.4.1.140.625.900.1domainLibraryEntryBEA-WEBLOGIC-MIB
1.3.6.1.4.1.140.625.900.1.16domainLibrarySecurityDDModelBEA-WEBLOGIC-MIB