on 09-25-2005 2:42 PM
Hello everybody,
In some of the iViews of our portal we are calling
SAP transactions (iViews of type SAP transaction).
Every time one of this iViews is being called it opens a new session in the R3 (we know that since our system is slow and we can see the logon screen each time).
Can anyone tell me if this is the normal stat for using this transaction iViews.
or is there a way to make the portal use the same SAP R3 session as long as we are in the same session in the portal?
Thanks for any information,
Adi
This is normal. if you use webgui or ITS, DSM terminator will automatically close the session.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If I understand correctly you are asking whether it is possible to pool SAP GUI (DIAG) sessions. No, as far as I know it isn't possible to pool DIAG sessions. Pooling is implemented for RFC sessions, for example in the Java Connector (JCo). Pooling is also implemented in ITS (AGate) so maybe you should look into using Webgui (SAP GUI for HTML) transactions, assuming that Webgui can be used for your scenario (browser based transactions differ from the native SAP GUI ones).
As long as you don't close the SAP GUI session, the connection to the backend will remain open. If you are running a SAP GUI session inside the browser navigating away from the transaction corresponds to one closing the SAP GUI session.
User | Count |
---|---|
78 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.