What does the Web Session Affinity feature of Active GridLink for RAC provide?

Question

Exhibit

Options

• AIt mandates that HTTP sessions must be stored in an Oracle RAC database for the highest
• BIt pins a connection to the thread associated with a web session such that subsequent connection
• CIt stores a reference to the connection associated with an HTTP session in the session object.
• DIt allows developers to modify how their web application reserves and releases database
• EIt provides improved performance by associating a database connection with an HTTP session.

• A
  3% (1)
• B
  8% (3)
• C
  5% (2)
• D
  13% (5)
• E
  72% (28)

Explanation

Session Affinity Policy Web applications where a user session has backtoback 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 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. * 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 reques is load balanced using Runtime Connection LoadBalancing (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

No community discussion yet for this question.