Possible issues we should take into account before increasing the Session Timeout values. — Oracle Analytics

Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Possible issues we should take into account before increasing the Session Timeout values.

Received Response
1
Views
2
Comments
Manoj Dixit
Manoj Dixit Rank 6 - Analytics Lead
edited Aug 13, 2024 5:30PM in Oracle Analytics Cloud and Server

Hi,

I have two questions related to the same topic - session timeout values: LogonExpireMinutes, ClientSessionExpireMinutes and ConnectionExpireMinutes. This question is 1/2.

OBIEE 10.1.3.4.2 dashboards have been embedded within another application. Let us call it as the Core Application. Mostly, the users are working on the Core Application. Sometimes some of them visit the OBI EE dashboards by clicking one of the menu options - "Dashboards". Currently, the session timeout values are set to 60 minutes. However, for the Core Application it's 4 hours (configured outside the OBI EE layer). Often, users switch between the application and the dashboards. They are finding it frustrating after an hour has elapsed to know that they have been logged out of the Dashboards while working in the Core Application or some other tasks at hand. After an hour has elapsed they have to re-do the steps (click "Dashboards", go to the same page where they were and re-apply the prompts) instead of just clicking 'Refresh' option to view the latest data on the same Dashboard page (this is one of the examples where they are feel frustrated).

They want us to make the auto-log off feature of the "Dashboards" same as the "Core Application" - four hours.

Would there be any adverse effect on the dashboards that we need to consider before we increase the session timeout values to four hours? Could you please guide?

Thank you.

Regards,

Manoj,

Answers

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    Edit: Never mind

  • Manoj Dixit
    Manoj Dixit Rank 6 - Analytics Lead

    Hi Christian,

    Thanks for your reply.

    Could you please let me know why you think that both the posts are the same?

    Here, I am trying to understand the negative impact, if any, of higher LogonExpireMinutes, ClientSessionExpireMinutes and ConnectionExpireMinutes parameter values (which, based on the same current value, I believe will be the same 240 minutes). Here, I am making myself aware of possible issues that may arise once all the parameters are set to 240 minutes. From users' perspective they will face the issue less frequently but may be some computing resources are reserved for the idle user for four hours which may cause some slowness in the front-end or a different user may not be allowed to log in, for example.

    In the other post, I am trying to understand the relationships among the three parameters if their values are different. There I shall prepare some scenarios, take actions according to the scenarios and monitor. I am reaching out to the community in order understand the relationships. For example value of x is set to 1 minute, value of y is set to 2 minutes and value of z is set to 3 minutes. What happens (and how to know what has happened)? Then value of x is set to 2 minutes, value of y is set to 1 minute and value of z remains the same. What happens, etc..

    Apologies if I was not clear.

    If still they are the same, please let me know how I can proceed ahead so that I can receive any response to the questions from you or someone else.

    Regards,

    Manoj.