Disclaimer:
BiWhy is available again for FREE to everyone on biwhy.net
Sessions do not necessarily reflect concurrency, as they may be stale or inactive. Because of that, new functionality was added to analyze only new users/sessions separately.
BOBJ session overview, analysis, and administration:
Overview and analysis:Session/User chart: the lines should run in parallel, ideally close to one another. Divergence usually indicates a problem.Summary Table – sessions aggregated by User / Authentication / Client.Simultaneous Sessions – high numbers are a sign of a session leak.Unique Sessions – how frequently a user logged in with a given method.Max and Avg Duration – high values indicate that sessions are not being closed, either explicitly or by timeout, or that there is real activity on those sessions.Detailed Table – shows details for each session.Only new users/sessions per minute (configurable).The chart is also available for any BiWhy table.Bucket analysis (here session duration) shows that most sessions last about 60 minutes. This indicates that they are being terminated by timeout, meaning users either do not close reports or explicit session termination on tab/browser close is not working. It also means that most of the sessions we see are idle.The duration line chart visualizes the 60-minute pattern (timeout).Duration Gantt view – session dynamics.
Admin Page:Analysis: It allows you to see live users and sessions in the system, similar to the CMC functionality, but with all analytical features available in BiWhy tables and charts.Administration: It allows you to cancel selected users/sessions. Unlike in the CMC, you can do this in bulk, which is particularly useful when you have a large number of unwanted sessions. For example, VTO scripts often generate test users but fail to clean them up. Instead of waiting for timeouts or restarting the system (which may not be possible if a non-VTO script is generating sessions in a PROD environment), you can simply terminate all of them directly from BiWhy.
You can also see days-old stale sessions that somehow survive system restarts and are not visible in the CMC. They appear to be harmless, but for cleanup purposes, it is a good idea to cancel them as well.
Screenshots:
Session/User chart: the lines should run in parallel, ideally close to one another. Divergence usually indicates a problem that causes a session leak.
Detailed Table – shows details for each session.
Summary Table – sessions aggregated by User / Authentication / Client.
Simultaneous Sessions – high numbers are a sign of a session leak.Unique Sessions – how frequently a user logged in with a given method.Max and Avg Duration – high values indicate that sessions are not being closed, either explicitly or by timeout, or that there is real activity on those sessions.
Only new users/sessions per minute (configurable).
The chart is also available for any BiWhy table.
Bucket analysis (here session duration) shows that most sessions last about 60 minutes. This indicates that they are being terminated by timeout, meaning users either do not close reports or explicit session termination on tab/browser close is not working. It also means that most of the sessions we see are idle.
The duration line chart visualizes the 60-minute pattern (timeout).
Duration Gantt view – session dynamics.
Admin Page. Analysis & Administration.
Disclaimer:BiWhy is available again for FREE to everyone on biwhy.net Sessions do not necessarily reflect concurrency, as they may be stale or inactive. Because of that, new functionality was added to analyze only new users/sessions separately.BOBJ session overview, analysis, and administration:Overview and analysis:Session/User chart: the lines should run in parallel, ideally close to one another. Divergence usually indicates a problem.Summary Table – sessions aggregated by User / Authentication / Client.Simultaneous Sessions – high numbers are a sign of a session leak.Unique Sessions – how frequently a user logged in with a given method.Max and Avg Duration – high values indicate that sessions are not being closed, either explicitly or by timeout, or that there is real activity on those sessions.Detailed Table – shows details for each session.Only new users/sessions per minute (configurable).The chart is also available for any BiWhy table.Bucket analysis (here session duration) shows that most sessions last about 60 minutes. This indicates that they are being terminated by timeout, meaning users either do not close reports or explicit session termination on tab/browser close is not working. It also means that most of the sessions we see are idle.The duration line chart visualizes the 60-minute pattern (timeout).Duration Gantt view – session dynamics. Admin Page:Analysis: It allows you to see live users and sessions in the system, similar to the CMC functionality, but with all analytical features available in BiWhy tables and charts.Administration: It allows you to cancel selected users/sessions. Unlike in the CMC, you can do this in bulk, which is particularly useful when you have a large number of unwanted sessions. For example, VTO scripts often generate test users but fail to clean them up. Instead of waiting for timeouts or restarting the system (which may not be possible if a non-VTO script is generating sessions in a PROD environment), you can simply terminate all of them directly from BiWhy.You can also see days-old stale sessions that somehow survive system restarts and are not visible in the CMC. They appear to be harmless, but for cleanup purposes, it is a good idea to cancel them as well.Screenshots:Session/User chart: the lines should run in parallel, ideally close to one another. Divergence usually indicates a problem that causes a session leak.Detailed Table – shows details for each session.Summary Table – sessions aggregated by User / Authentication / Client.Simultaneous Sessions – high numbers are a sign of a session leak.Unique Sessions – how frequently a user logged in with a given method.Max and Avg Duration – high values indicate that sessions are not being closed, either explicitly or by timeout, or that there is real activity on those sessions. Only new users/sessions per minute (configurable).The chart is also available for any BiWhy table.Bucket analysis (here session duration) shows that most sessions last about 60 minutes. This indicates that they are being terminated by timeout, meaning users either do not close reports or explicit session termination on tab/browser close is not working. It also means that most of the sessions we see are idle.The duration line chart visualizes the 60-minute pattern (timeout). Duration Gantt view – session dynamics. Admin Page. Analysis & Administration. Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
