Provides a count of the total number of attempts to access a
bean from the cache.

The sum of the Cache Hit Count and Cache Miss Count may not add
up to the cacheAccessCount in a running server because these
metrics are retrieved using multiple calls and the counts could
change between the calls.

Provides a count of the total number of times an attempt to
access a bean from the cache succeeded.

The sum of the Cache Hit Count and Cache Miss Count may not add
up to the cacheAccessCount in a running server because these
metrics are retrieved using multiple calls and the counts could
change between the calls.

Provides a count of the total number of times an attempt to
access a bean from the cache failed.

The sum of the Cache Hit Count and Cache Miss Count may not add
up to the cacheAccessCount in a running server because these
metrics are retrieved using multiple calls and the counts could
change between the calls.

Provides a count of the total number of times a failed attempt
was made to get an instance from the free pool. An Attempt to get a
bean from the pool will fail if there are no available instances in
the pool.

An alphanumeric name for this server instance. (Spaces are not
valid.)

The name must be unique for all configuration objects in the
domain. Within a domain, each server, machine, cluster, JDBC
connection pool, virtual host, and any other resource type must be
named uniquely and must not use the same name as the domain.

The server name is not used as part of the URL for applications
that are deployed on the server. It is for your identification
purposes only. The server name displays in the Administration
Console, and if you use WebLogic Server command-line utilities or
APIs, you use this name to identify the server.

After you have created a server, you cannot change its name.
Instead, clone the server and provide a new name for the clone.