<p>The password (community name) that you want this SNMP
agent to use to secure SNMPv1 or v2 communication with SNMP managers.
Requires you to enable community based access for this agent.</p>
<p>SNMPv3 does not use community names. Instead, it encrypts user names
and passwords in its PDUs. </p>
<p>When you use SNMPv1 or v2, there are two community names that
are needed when the WebLogic SNMP agent and SNMP managers interact:</p>
<ul>
<li>
<p>The name that you specify in this community prefix. All SNMP
managers must send this name when connecting to this SNMP
agent.</p>
</li>
<li>
<p>The community name that the SNMP manager defines. The
SNMP agent must send this name when connecting to the manager. (You
supply this community name when you configure a trap
destination.)</p>
</li>
</ul>
<p>In addition to using the community prefix as a password, an
SNMP agent on an Administration Server uses the prefix to qualify
requests from SNMP managers. Because the Administration Server can
access data for all WebLogic Server instances in a domain, a
request that specifies only an attribute name is potentially ambiguous.
For example, the attribute
<code>serverUptime</code> exists for each WebLogic Server instance
in a domain. To clarify requests that you send to SNMP agents on
Administration Servers, use the community prefix as
follows:</p>
<ul>
<li>
<p>To request the value of an attribute on a specific Managed
Server, when you send a request from an SNMP manager, append the
name of the server instance to the community prefix:
<code><i>community_prefix@server_name</i></code>.</p>
</li>
<li>
<p>To request the value of an attribute for all server instances in
a domain, send a community name with the following form:
<code><i>community_prefix</i></code></p>
</li>
</ul>
<p>To secure access to the values of the WebLogic attributes when using
the SNMPv1 or v2 protocols, it is recommended that you set community prefix
to a value other than <code>public</code>.</p>
<p>You cannot specify a null (empty) value for the community prefix. If
you delete the prefix value, WebLogic Server resets the value to
<code>public</code>. If you do not want this agent to receive SNMPv1 or
v2 requests, instead of trying to set the community prefix to a null value,
disable community based access. With community based access disabled, WebLogic
Server ignores the community prefix value.</p>
(Interface=weblogic.management.configuration.SNMPAgentMBean Attribute=getCommunityPrefix)