Oracle 1z0-102 Exam With Confidence Using Practice Dumps

C: If more than one copy of myLibrary is registered, WebLogic Server selects the library with the highest specification version. If multiple copies of the library use the selected specification version, WebLogic Server selects the copy having the highest implementation version.

D: A Java EE application can reference a registered shared Java EE library using entries in the application’s weblogic-application.xml deployment descriptor.

B: To proxy requests by path, use the Location block and the SetHandler statement.

When to use

Use to apply directives to content that lives outside the filesystem. For content that lives in the filesystem, use and . An exception is , which is an easy way to apply a configuration to the entire server.

For all origin (non-proxy) requests, the URL to be matched is a URL-path of the form /path/. No scheme, hostname, port, or query string may be included. For proxy requests, the URL to be matched is of the form scheme://servername/path, and you must include the prefix.

E: Add an IfModule block that defines one of the following:

For a non-clustered WebLogic Server instance:

The WebLogicHost and WebLogicPort parameters.

For a cluster of WebLogic Servers instances:

The WebLogicCluster parameter.

If you are proxying requests by MIME type to a cluster of WebLogic Servers, use the WebLogicCluster parameter.

For example:

WebLogicCluster w1s1.com:7001,w1s2.com:7001,w1s3.com:7001

Note #1: The ... section is used to mark directives that are conditional on the presence of a specific module. The directives within an section are only processed if the test is true. If test is false, everything between the start and end markers is ignored.

The test in the section directive can be one of two forms:

module name

!module name

Note #2:

Directive

Description:Applies the enclosed directives only to matching URLs

Syntax: ...

Context:server config, virtual host

Status:Core

Module:core

The directive limits the scope of the enclosed directives by URL. It is similar to the directive, and starts a subsection which is terminated with a directive. sections are processed in the order they appear in the configuration file, after the sections and .htaccess files are read, and after the sections.

sections operate completely outside the filesystem. This has several consequences. Most importantly, directives should not be used to control access to filesystem locations. Since several different URLs may map to the same filesystem location, such access controls may by circumvented.

A WebLogic domain can be composed of a number of WebLogic instances, and

several of these servers may be grouped into clusters. For instance, you could set up a

cluster of WebLogic servers, all of which host your web application and related

resources. This cluster of servers could be fronted by a load balancer that distributes

requests evenly across all the members of the cluster. The load balancer could itself be

another WebLogic instance. All server instances must belong to the same WebLogic

domain. Thus, a WebLogic cluster is a group of servers working together with services,

such as clustered JNDI, to provide support for failover and load balancing. A domain

may in turn have a number of WebLogic instances, several groups of which can be

placed into different clusters.