Oracle 1z0-599 Exam With Confidence Using Practice Dumps

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.

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