How to avoid huge system resource consume , when SSO can login in many time

[Former Member]

Hi all.

We implement the EP-SSO LogonTicket -- SAP R/3.

But user can use EP-SSO login in R/3 for many sessions, there is no session control.

If in this situation, how R/3 system can avoid the huge system resource consume ? Because users can connect to R3 for many sessions.

Its urgent question because without give customer a good reply, they cannot put the project online.

Is there some experts ?

[Former Member]

Hi

You're right. DSM should handle this.

Note 596698 shows some possible restrictions.

DSM didn't work for us because of different domains and protocolls (http:
<portal> /https:
<its>).

Regards

Nicolaj

[Former Member]

Hi all.

Is there anybody can help me confirm this problem ?

[Former Member]

Hi Jianhong,

I saw in this link that you can control the no of sessions and the length the session.

Check this link

http://help.sap.com/search/highlightContent.jsp

http://help.sap.com/search/highlightContent.jsp

Refer SAP Note 314568.

Search for "SAP Sessions" in help.sap.com

Hope this solves your problem

Regards

Arun

[Former Member]

Hi Arun.

http://help.sap.com/search/highlightContent.jsp

does not show anything, it returns me session expired.

[Former Member]

Hi Jianhong,

Logging Off Inactive Users

You can set up your SAP System to automatically log off users with no activity after a specified period of time. This improves system security by assuring that SAP sessions at unattended terminals do not stay active indefinitely.

By default, automatic logoff is not activated in the SAP System. Users remain logged on no matter how long they may be inactive. You activate automatic logoff by setting the system profile parameter rdisp/gui_auto_logout to the number of seconds of inactivity you want to permit. Enter as a value for this parameter the number of seconds of inactivity that must elapse before a user is automatically logged off.

If you activate this function, the inactive users are logged off after the specified period expires. The system does not save data before logging off the user. Unsaved data in the user session is lost. The system also does not display a logoff confirmation prompt.

Procedure

To activate automatic logoff, proceed as follows:

1. Call the system profile maintenance functions with Administration ® CCMS ® Configuration ® Profile maintenance (transaction RZ10).

2. Define or maintain parameter rdisp/gui_auto_logout. Enter as a value for this parameter the number of seconds of inactivity that must elapse before a user is automatically logged off.

To activate automatic logoff throughout the system, set the parameter in the default profile (DEFAULT.PFL). However, if you want to activate automatic logoff only for a specific SAP application server, set the parameter in the profile for that particular instance.

Remember that some users are inactive for extended periods of time. Such users may include:

· Programmers or other users of SAP editors, who regularly work for long periods of time only using the front end software.

· Users that enter data only rarely, such as production employees who only enter data in the SAP System during certain procedures, such as when materials are delivered.

You should either set a high value for parameter rdisp/gui_auto_logout, or deactivate automatic logoff on the servers on which such users are active. This protects these users from loss of data or the inconvenience of having to log on again.

To deactivate automatic logoff, delete the parameter from your profile(s) or set it to the value 0.

Regards

Arun

[Former Member]

Hi Arun.

Thanks.

However, I see in EP, there is a component

Session Release Agent

From my understanding, if the user closes the browser window or navigates to another position, the DSM will terminator the sessions ( which connect to backend R3 )

Is it true ?

If it works in this way, it can solve my problem.

What I need is where can I find some tool to monitor the sessions connected from EP in R/3