on 02-04-2007 4:25 PM
hi
I have a webdynpro appliaction which doesnot open in portal Content but in new Window.I have 2 scenario:
1.User logs off the portal
2.User just closes browser on which portal is running.
Scenario 1:
if user click on my Webdynpro application it opens in new Window ,now he minimize the browser window in which the Webdynpro appliaction is running.And then logs off from the Portal.In this scenario my Webdynpro session is killed by the Portal.
Scenario 2:
if user click on my Webdynpro application it opens in new Window ,now he minimize the browser window in which the Webdynpro appliaction is running.And simply closes browser on which portal is running.In this case portal doesnot kill the session of my Webdynpro application and user can do the transcation using the Webdynpro application.
I want this 2nd Scenario to be solved.Please help me out.
Regards
Nidhideep
Hi,
The 2 scenario u have explained are the normal functions of the browser and the portal. When the application is opened from portal, it maintains the cookie of the session. Now when the main portal is logged off, this cookie is killed and so the application is timed out. On the other hand, if the browser is closed, the session cookie is not killed and so the webdynpro application can still function. These are the usual cases which happen in any browser. If u want the session to be closed in the second case also, then u may have to do some searching. I think it can be done. I have seen some post like this before few months. Searching in SDN will get u the answer.
Regards,
Harini S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The portal session stays alive as long as the logoff is not done in the portal. Since you are saying log off in the scenario 1, it is killing all sessions connected with the portal. You can check the properties of log off in this <a href="http://help.sap.com/saphelp_nw04/helpdata/en/38/5dc53e5ae84d3be10000000a11405a/frameset.htm">url</a>.
Next, in the scenario 2, the portal session keeps working as long as it times out.
In order to close the session you can change the java script code in the log off component of the portal.
You can import the login par (\usr\sap\Instance id\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd)and edit the logoff page jsp accordingly.
Again export and deploy the edited login project and create a new par file.
Now paste this par as the default one in the same location with the name (com.sap.portal.runtime.logon.par.bak)
Regards,
Sujana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.