Examples Of How One Can Possibly Check Session Persistence On BigIP F5, Cisco Ace, Citrix Netscaler or Radware AppDirector Load Balancer Appliances
(Doc ID 601694.1)
Last updated on JUNE 08, 2018
Applies to:Oracle Applications Framework - Version 12.1.3 to 12.1.3 [Release 12.1]
Oracle E-Business Suite Technology Stack - Version 126.96.36.199 to 12.1.3 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.
Oracle DOES NOT own any of the 3rd party appliances that are being mentioned. If one needs additional assistance or clarification around session persistence with the 3rd party Appliance, then one needs to create a Service Request directly with the 3rd party company and NOT Oracle. This note was created only to offer general guidance to help explain concepts, nothing more.
This document aims to help a customer check persistence settings on F5 BigIP and Cisco ACE load balancer appliances. It provides general guidance on checking persistence settings on the hardware device to ensure correct eBusiness suite functioning.
Maintaining session persistence is essential to ensuring a users session remains on the same middle tier throughout the duration of their session. When the session is not maintained on the one middle tier users may experience the 'Transaction context is lost' message See <Note 456906.1>.
Session Persistence is the act of keeping a specific user's traffic going to the same server that was initially hit when the site was contacted for the first HTTP transaction. This is especially important for E-Business Suite as various modules bundled with the suite need to maintain session state. Session persistence is sometimes referred to as "server stickiness."
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Section 1: F5 BigIp|
|Section 2: Cisco Application Control Engine Module (ACE)|
|Section 3: Radware AppDirector|
|Section 4: Citrix Netscaler|