How To Check Session Persistence On BigIP F5, Cisco Ace, Citrix Netscaler or Radware AppDirector Load Balancer Appliances (Doc ID 601694.1)

Last updated on JUNE 07, 2016

Applies to:

Oracle Applications Framework - Version 12.1.3 to 12.1.3 [Release 12.1]
Oracle Applications Technology Stack - Version 11.5.10.2 to 12.1.3 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.

Goal

This document aims to help the customer verify their persistence settings on F5 BigIP and Cisco ACE load balancer appliances. It provides instructions on checking specific 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."

Section 1: F5 BigIp
Section 2: Cisco Application Control Engine Module (ACE)

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms