Siebel Open UI, Tools, Scripting and EAI (MOSC)

MOSC Banner

Re: Query regarding "SWSENoSessInPref" parameter in eapps.cfg file

We have below setting in eapps.cfg.

SessionTokenTimeout = 390

SessionTimeout = 21600

SessionTokenMaxAge = 390

SWSENoSessInPref = TRUE

This allows us to have session tokens valid for 6hrs 30 minutes.

But when we have emergency bounce in PROD, upstream system still have tokens which are valid from server 1 & 2.

During rolling bounce all server 1 Tokens create task in Server 2.

This over flood the tasks in Server2.

How can we handle this situation.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center