Free and Premium Oracle 1z0-599 Dumps Questions Answers

A, B: With Active GridLink for RAC, WebLogic instances are isolated from RAC configuration changes, and DBAs only need to contend with a single data source rather than multiple data sources.

D: Active GridLink for RAC distributes work based on different backend node capacities, automatically detecting and adapting to overworked nodes and hangs. It enables smart load balancing across RAC nodes. This makes it easier to route traffic around node failures, enhancing availability and performance.

* A WAR file deployed to WebLogic Server always includes the following files:

One servlet or Java Server Page (JSP), along with any helper classes.

An optional web.xml deployment descriptor, which is a Java EE standard XML document that describes the contents of a WAR file.

A weblogic.xml deployment descriptor, which is an XML document containing WebLogic Server-specific elements for Web applications.

A WAR file can also include HTML or XML pages and supporting files such as image and multimedia files.

* Built on top of Oracle Coherence (Coherence), Coherence*Web:

/ brings Coherence data grid's data scalability, availability, reliability, and performance to in-memory session management and storage.

/ can be deployed to many mainstream application servers such as Oracle GlassFish Server, Oracle WebLogic Server, IBM WebSphere, Tomcat, and so on

* Coherence*Web enables HTTP session sharing and management across different Web applications, domains, and heterogeneous application servers. Session data can be stored in data caches outside of the application server, thus freeing application server heap space and enabling server restarts without losing session data.

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.

* WebLogic Server supports Fast Connection Failover, a Oracle feature which provides an application independent method to implement RAC event notifications, such a detection and cleanup of invalid connections, load balancing of available connections, and work redistribution on active RAC instances.

* A GridLink data source uses Fast Connection Failover and responds to Oracle RAC

events using ONS. This ensures that the connection pool in the GridLink data source

contains valid connections (including reserved connections) without the need to poll

and test connections

Active GridLink for Oracle RAC

In Oracle WebLogic Server 10.3.4, a single data source implementation has been introduced to support an Oracle RAC cluster. It responds to FAN events to provide Fast Connection Failover (FCF), Runtime Connection Load-Balancing (RCLB), and RAC instance graceful shutdown. XA affinity is supported at the global transaction Id level. The new feature is called WebLogic Active GridLink for RAC; which is implemented as the GridLink data source within WebLogic Server.

Note:

* The WebLogic Server JDBC subsystem has supported Oracle RAC since WLS version 9.0, originally developed for Oracle9i RAC. This support is based on a particular type of data source configuration, called a multi data source. A multi data source is a data source abstraction over one or more individual data sources. It serves JDBC connections from each of the member data sources according to a specified policy. A RAC multi data source configuration requires that each member data source obtain connections to a particular RAC instance.

The major components of the WebLogic JMS Server architecture, as illustrated in the figure below.

*(A) JMS servers that can host a defined set of modules and any associated persistent storage that reside on a WebLogic Server instance.

*(B) JMS modules contains configuration resources (such as queues, topics, and connections factories) and are defined by XML documents that conform to the weblogic-jmsmd.xsd schema.

*Client JMS applications that either produce messages to destinations or consume messages from destinations.

*(E) WebLogic persistent storage (file store or JDBC-accessible) for storing persistent message data.

The following figure illustrates the WebLogic JMS architecture.

JMS queue    A staging area that contains messages that have been sent and are waiting to be read. Note that, contrary to what the name queue suggests, messages have to be delivered in the order sent A JMS queue only guarantees that each message is processed only once.

The Clone WebLogic Domain option launches a wizard that enables you to clone a WebLogic Domain from an existing reference domain that is already discovered with Cloud Control. It allows you to clone the Middleware Home and its binaries, and the domain configuration.

*If you selected the Cloning a WebLogic Domain option, the Middleware Provisioning: Domain Configuration page appears. This page contains a set of links to several pages where you can enter the properties that are most likely to be reconfigured like domain name, listen addresses for the administration server and managed servers, Node Manager/Machine configuration, and JDBC data sources.

The following principles encourage RESTful applications to be simple, lightweight, and fast:

* Resource identification through URI

* Uniform interface: Resources are manipulated using a fixed set of four create, read, update, delete operations: PUT, GET, POST, and DELETE. PUT creates a new resource, which can be then deleted by using DELETE. GET retrieves the current state of a resource in some representation. POST transfers a new state onto a resource. See Responding to HTTP Methods and Requests for more information.

* Self-descriptive messages

* Stateful interactions through hyperlinks

Note:

* Types of Security Roles: Global Roles and Scoped Roles

There are two types of security roles in WebLogic Server:

/ A global security role can be used in any security policy. Oracle provides several default global roles that you can use out of the box to secure your WebLogic resource

/ A scoped role can be used only in policies that are defined for a specific instance of a WebLogic resource (such as a method on an EJB or a branch of a JNDI tree). You might never need to use scoped roles. They are provided for their flexibility and are an extra feature for advanced customers.

Incorrect:

Not E: Role mapping is the process whereby principals (users or groups) are dynamically mapped to security roles at runtime. In WebLogic Server, a Role Mapping provider determines what security roles apply to the principals stored a subject when the subject is attempting to perform an operation on a WebLogic resource. Because this operation usually involves gainingaccess to the WebLogic resource, Role Mapping providers are typically used with Authorization providers.

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.

In addition to the coherence.jar file, Coherence provides a deployable shared library, coherence-web-spi.war, that contains a native plug-in to WebLogic Server's HTTP Session Management interface. Coherence also provides the active-cache-1.0.jar file that contains the classes that enable WebLogic Server to interact with Coherence.