1z0-599 Questions and Answers

Use the Administration Console to:

* (A) Configure, start, and stop WebLogic Server instances

* Configure WebLogic Server clusters

* (D) Configure WebLogic Server services, such as database connectivity (JDBC) and messaging (JMS)

* Configure security parameters, including managing users, groups, and roles

* Configure and deploy your applications

* Monitor server and application performance

* View server and domain log files

* View application deployment descriptors

* (F) Edit selected run-time application deployment descriptor elements

* (B) Control (start, stop, and restart) standalone Coherence cache servers

* (B) Create and configure Coherence clusters

Incorrect:

Not C: The separate Domain Template Builder is used for creating Domain Templates.

fair-share-request-class—Specifies the average thread-use time required to process requests. The default fair share value is 50.

For example, assume that WebLogic Server is running two modules. The Work Manager for ModuleA specifies a fair-share-request-class of 80 and the Work Manager for ModuleB specifies a fair-share-request-class of 20.

During a period of sufficient demand, with a steady stream of requests for each module such that the number requests exceed the number of threads, WebLogic Server will allocate 80% and 20% of the thread-usage time to ModuleA and ModuleB, respectively.

* Example:

<work-manager>

<name>lowpriority_workmanager

<name>low_priority

10

<work-manager>

<name>highpriority_workmanager

<name>high_priority

100

Note:

* A request class expresses a scheduling guideline that WebLogic Server uses to allocate threads to requests. Request classes help ensure that high priority work is scheduled before less important work, even if the high priority work is submitted after the lower priority work.

Incorrect:

Not C: response-time-request-class—Specifies a response time goal in milliseconds. Response time goals are not applied to individual requests. Instead, WebLogic Server computes a tolerable waiting time for requests with that class by subtracting the observed average thread use time from the response time goal, and schedules requests so that the average wait for requests with the class is proportional to its tolerable waiting time.

Not A, D: Not related to thread constraints.

For example, assume that WebLogic Server is running two modules. The Work Manager for ModuleA specifies a fair-share-request-class of 80 and the Work Manager for ModuleB specifies a fair-share-request-class of 20.

Note:

You can use the 12.1.1 WebLogic Upgrade Wizard to upgrade domains created in WebLogic Server 8.1. You can also use the WebLogic Upgrade Wizard to upgrade a WebLogic domain created in WebLogic Server 9.x or 10.x to 12.1.1, but this is optional.

The JRockit JVM is included in all Oracle WebLogic products – Oracle WebLogic Server Standard Edition, Oracle WebLogic Enterprise Edition, WebLogic Suite, and Oracle WebLogic Application Grid. JRockit will also be used across the Oracle Fusion Middleware and Oracle Applications product families, with the certification process happening over the coming months. For current status, see the certification matrices available from Oracle Metalink.

WebLogic GridLink Data Sources supports transaction-based affinity.

To manage work in your applications, you define one or more of the following Work Manager components:

Fair Share Request Class:

Response Time Request Class:

Min Threads Constraint:

Max Threads Constraint:

Capacity Constraint

Context Request Class:

Note:

* max-threads-constraint—This constraint limits the number of concurrent threads executing requests from the constrained work set. The default is unlimited. For example, consider a constraint defined with maximum threads of 10 and shared by 3 entry points. The scheduling logic ensures that not more than 10 threads are executing requests from the three entry points combined.

A max-threads-constraint can be defined in terms of a the availability of resource that requests depend upon, such as a connection pool.

A max-threads-constraint might, but does not necessarily, prevent a request class from taking its fair share of threads or meeting its response time goal. Once the constraint is reached the server does not schedule requests of this type until the number of concurrent executions falls below the limit. The server then schedules work based on the fair share or response time goal.

* WebLogic Server prioritizes work and allocates threads based on an execution model that takes into account administrator-defined parameters and actual run-time performance and throughput.

Administrators can configure a set of scheduling guidelines and associate them with one or more applications, or with particular application components.

* WebLogic Server uses a single thread pool, in which all types of work are executed. WebLogic Server prioritizes work based on rules you define, and run-time metrics, including the actual time it takes to execute a request and the rate at which requests are entering and leaving the pool.

The common thread pool changes its size automatically to maximize throughput. The queue monitors throughput over time and based on history, determines whether to adjust the thread count. For example, if historical throughput statistics indicate that a higher thread count increased throughput, WebLogic increases the thread count. Similarly, if statistics indicate that fewer threads did not reduce throughput, WebLogic decreases the thread count. This new strategy makes it easier for administrators to allocate processing resources and manage performance, avoiding the effort and complexity involved in configuring, monitoring, and tuning custom executes queues.

Note:

* 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.

* In managing multiple servers, Node Manager uses multiple configuration files and outputs log files to multiple directories.

* nodemanager.domains

This file contains mappings between the names of domains managed by Node Manager and their corresponding directories.

* Node Manager in the WebLogic Server Environment

Reference; Node Manager Administrator's Guide for Oracle WebLogic Server 12c