Oracle 1Z0-599 Exam Dumps

A Node Manager process is not associated with a specific WebLogic domain but with a

machine. You can use the same Node Manager process to control server instances in

any WebLogic Server domain, as long as the server instances reside on the same

machine as the Node Manager process. Node Manager must run on each computer

that hosts WebLogic Server instances---whether Administration Server or Managed

Server---that you want to control with Node Manager.

D: auto-kill-if-failed

Specifies whether the Node Manager should automatically kill

this server (the managed server) if its health state is failed.

(Interface=weblogic.management.configuration.ServerMBean Attribute=getAutoKillIfFailed)

When Auto Restart is enabled, Node Manager will try to restart the Managed Server if it crashes or goes down unexpectedly, for instance, as the result of a machine reboot.

E: When Auto Restart is enabled, Node Manager will try to restart the Managed Server if it crashes or goes down unexpectedly, for instance, as the result of a machine reboot.

The WebLogic Server Management Pack EE greatly improves application

performance by providing unique functionality to automatically detect performance

bottlenecks; quickly diagnose these performance problems, and identify their root

cause. Key application performance management features of the pack include the

following:

* (A) Manage multiple farms and WebLogic Domains centrally

* Monitor Oracle Coherence Cluster -- including all nodes within a cluster, all

caches, services, connection managers and connections

* Monitor middleware availability and performance out-of-box; track such data

historically, and receive notifications of potential problems

* Obtain real-time, in-depth JVM diagnostics without instrumentation overhead

* Trace transactions across containers as well as to the database

* (E) Analyze call paths and dependencies via graphical, architecture views

* (E) Automatically discover and model dependencies between Java components,

frameworks, and web services

An internal application may be configured to always use a minimum version of the same library. Applications that require no specific version can be configured to use the latest version of the library.

Note:

* Specification-Version (a manifest Attributes for Java EE Libraries)

An optional String value that defines the specification version of the shared Java EE library. Referencing applications can optionally specify a required Specification-Version for a library; if the exact specification version is not available, deployment of the referencing application fails.

The Specification-Version uses the following format:

Major/minor version format, with version and revision numbers separated by periods (such as '9.0.1.1')

Referencing applications can be configured to require either an exact version of the shared Java EE library, a minimum version, or the latest available version.

* Implementation-Version (a manifest Attributes for Java EE Libraries)

An optional String value that defines the code implementation version of the shared

Java EE library. You can provide an Implementation-Version only if you have

also defined a Specification-Version.

* Extension-Name (a manifest Attributes for Java EE Libraries)

An optional string value that identifies the name of the shared Java EE library. Referencing applications must use the exact Extension-Name value to use the library.

As a best practice, always specify an Extension-Name value for each library. If you do not specify an extension name, one is derived from the deployment name of the library. Default deployment names are different for archive and exploded archive deployments, and they can be set to arbitrary values in the deployment command.

* After a library is deployed, the extension-name, specification-version and implementation-version of the library can be found in Administration console.

By default, JMS messages never expire. When applications send messages to queues or topics with durable subscribers, WebLogic must retain the message until it is consumed. This is fine in most point-to-point messaging applications because consumers are constantly consuming messages. Any message sent to a queue will typically be consumed in a relatively short period of time. If the consumers get disconnected, they will usually reconnect as soon as possible and start processing any messages that might have built up in the queue.

D: For durable subscribers to a topic, this is not necessarily true. The messaging system is forced to retain any message that has not been consumed by a durable subscriber, regardless of whether that durable subscriber will ever return. In this case, WebLogic is at the mercy of the durable subscriber to unsubscribe when it no longer wishes to receive the messages. If the durable subscriber logic is flawed in such a way that the subscribers do not unsubscribe properly, the messaging system will start to fill up with messages that may never be delivered. This calls for real caution in using durable subscribers. Fortunately, there is another way to help deal with this problem. Message expiration can be set at the connection factory level. Using a connection factory's default time-to-live attribute, we can specify the number of milliseconds that WebLogic should retain an undelivered message after it is sent.