Session Affinity Policy

Web applications where a user session has back-to-back online transaction processing (OLTP) have

better performance when repeated operations against the same set of records are processed by the

same RAC instance. Business applications such as online shopping and online banking are typical

examples of this pattern.

A GridLink data source uses the Session Affinity policy to ensure all the data base operations for a

web session, including transactions, are directed to the same Oracle RAC instance of a RAC cluster.

Note:

The context is stored in the HTTP session. It is up to the application how windows (within a browser

or across browsers) are mapped to HTTP sessions.

Note 2:

* GridLink Affinity

WebLogic Server GridLink affinity policies are designed to improve application performance by

maximizing RAC cluster utilization. A GridLink data source monitors RAC load balancing advisories

(LBAs) using the AffEnabled attribute to determine if RAC affinity is enabled for a RAC cluster. The

first connection request is load balanced using Runtime Connection Load-Balancing (RCLB) and is

assigned an Affinity context. All subsequent connection requests are routed to the same Oracle RAC

instance using the Affinity context of the first connection until the session ends or the transaction

completes.

* Session Affinity

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/1Z0-599/page_29_img_1.jpg

Reference; Configuring and Managing JDBC Data Sources for Oracle Weblogic server 12c, Using

GridLink Data Sources

B: A domain consists of one or more WebLogic Server instances (and their associated resources) that

you manage with a single Administration Server.

D: In a domain, server instances other than the Administration Server are referred to as Managed

Servers. Managed Servers host the components and associated resources that constitute your

applications.

Incorrect:

Not A: Each WebLogic Server domain must have one server instance that acts as the Administration

Server.

Not C: A domain can include multiple WebLogic Server clusters and non-clustered WebLogic Server

instances.

Not E: 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.

Reference: Overview of WebLogic Server Domains

Using the Domain Template Builder to Create Domain Templates

To create a domain, start the Configuration Wizard and choose a domain configuration template.

Reference: Creating and Configuring Domains Using the Configuration Wizard

C: Spring Console Extension. WebLogic provides an Admin Console extension for Spring to provide

administrators with visual tools for monitoring the Spring parts of deployed applications (first

navigate to WebLogic Admin Console's P

| Extension menu option and and enable spring-

console). This Spring console extension is basically a set of pages which are added amongst the

normal pages of the standard WebLogic admin console, rather than being a separate console per se.

The extension provides a view onto the values of the WebLogic generated Spring MBeans

D: If you have an issue, you use the Oracle Support organisation for help with WebLogic specific

problems and any Spring parts to your application are treated just like your own custom code is, from

an Oracle Support perspective.

E: WebLogic Injected Spring Beans is a Weblogic feature that is enabled by default.

Reference: WebLogic and Spring

Similar to the configuration information, WebLogic Server runtime MBeans are arranged in a

hierarchical data structure. When connected to an Administration Server, you access the runtime

MBean hierarchy by entering the serverRuntime or the domainRuntime command. The

serverRuntime command places WLST at the root of the server runtime management objects,

ServerRuntimeMBean; the domainRuntime command, at the root of the domain-wide runtime

management objects, DomainRuntimeMBean.

Reference: WebLogic Scripting Tool, Browsing Runtime MBeans