Portal Session Timeout - ICM/Webdynpro/POWL

Hi Experts,
We are having SRM Portal which has POWL Webdynpro and other applications running.
SRM Portal is a seperate JAVA Instance and integrated to backend with SSO enabled.
We have Logon Ticket Timeout set as default 8 Hours and the Session Timeout in Portal set as 2 Hours (Server>services>webcontainer>properties>Session Timeout).
For the ABAP backend, we have rdisp/plugin_auto_logout-->7200 (2 Hours) and ICM timeout as remommeded by SAP as icm/server_port_0 = PROT=HTTP,PORT=8012,TIMEOUT=90,PROCTIMEOUT=600
Now the problem is:
1. Users connected to portal and work on any POWL Iviews has an idle time of two hours-->we get the ICM session timeout error page.
2. Sometimes Users get the Login screen of portal within the Navigation Frame which can be identified as the Ticket Expiration
Is there a possibility to control the behavior of portal to avoid these error pages to Users like if the timeout happened in backend, there should be auto refresh if the user clicks the application.
And if the ticket expired, the portal should refresh to the home screen on clicking any Iview.
We tried the IDLE timeout pop up and in Vain, you could see my another post on the same.
Portal Idle Pop Up
Regards,
Sethu

Hi,
Read SAP note 705013,
I think adjusting the kernel parameters, rdisp/gui_auto_logout and rdisp/plugin_auto_logout will help.
Try adding below parameters in the Instance profile.
icm/keep_alive_timeout 3600
icm/conn_timeout 5000
Regards,
Venkata S Pagolu

Similar Messages

Portal session Timeout

Hi,
I want to increase the portal session timeout to 2hrs. We have 2 Portal server which are load balanced. The configuration is as below:
Portal Version: 10.3.0.337003
.NET Version: 2.0
OS: Win 2003 Server
Database : Oracle 11g
IIS:6.0
On both the server I have edited the session time out parameter corresponding to the file as mentioned below:
Portalconfig.xml :
<setting name="BrowserLoginTokenExpiration">
<value xsi:type="xsd:integer">120</value>
</setting>
BEA Web.config
<sessionState cookieless="false" timeout="120" />
.NET Web.Config
<sessionState timeout="120" />
But still the we are not able to achive 2 hrs of session timeout. Do we have to make entry in .NET machine.config? Please let me know if thier is any other file where changes is required?
Also in lower environment, we have our portal installed on .NET 2.0 framework ( only one instance of portal server ), we are able to achive 2Hrs of session time out by modifying the state management session time out value ( default website-> properties->asp.net tab->edit configuration->state management tab)
Please help me!!
Edited by: Oracle WCI on Oct 10, 2011 1:43 PM

As per the documents share by oracle support..only place in WCI 10gr3 (10.3.0.1) and IIS where we set timeout value is State Management tab (default website->portal ->properties->asp.net->edit configuration-state management)..we have this valye set to 2Hrs (120 min) on both the portal server ( load balanced)..but still portal is getting time out after 1 hrs..I am not sure which external factore is limiting this to 1 hrs..
both portal server are load balanced and IWA is implemented...
Any light on the external factor line SSO setting, Load balanced ..etc will be higly appriciated..Please help!!

Portal session timeout judge

Hi everybody,
I have a question about portal session timeout. Now we have a javascript for session timeout in Masthead iview, which can increase the time for the active user. It uses EPCM to rase the event. But our page has four iveiws, and there is a iview form that use the javascript to submit the request, and don't refresh the whole page, so it can't call our session timeout javascript to increase the time.
Whether we can call the javascript from other iviews? Or do we have other ways to do the session timeout judge and increase the time by user's activity in sap portal ?
Thanks

Hi,
Try to subscribe to EPCM events on all navigations in your code, which will in turn update the timer
EPCM.subscribeEvent("urn:com.sapportals:navigation", "Navigate", pop);
EPCM.subscribeEvent("urn:com.foo.bar.myapp", "myEvent", pop);
You can also call the update timer method (in masthead) from your I view form code using AJAX, which will be more simpler.
Regards,
Santhosh

Portal Session Timeout Setting

There is a JServ session and a portal session. I know how to control session timeout and session clean up frequency in JServ - that's in zone.properties. But, I dont know how to set timeout for portal session, i.e., I'd like to have the user be forced to login again when he has been idle for 15 mins - and only if he has been idle. Jserv session settings are not sufficient for this because Portal has it's own session that must time out.
How to set this timeout value (I'm using my own provider which has a timeout setting in zone.properties and includes a bunch of JSP portlets)? Also, is there a clean up thread for which the frequency has to be set?

I've contacted metalink weeks ago, and this is NOW, a know bug...
Incredible... Oracle just DO NOT TEST their products... Even a simple SESSION timeout do not work. Also, if I click back after "I log In and Log out" ... Session still up without have to login again!
BUG 2442268

Portal Session Timeout and Logon Ticket Timeout

Hi All,
Can anyone give me answers to the following:
- If my Portal session times out, but my logon ticket is still valid, will I lose my session data?
- Is there any way of determining the size of a users session information in memory (or the size of all user sessions in memory). I can see in the Monitoring service in Visual Admin the number of sessions but not their individual or total size.
I'm using EP7.
Cheers,
Steve

Hi,
the Logon Ticket is only used for SSO between the portal and the integrated system. Your session data is stored in the session. If the session times out or gets closed, the session data is lost.
br,
Tobias

How to Sync the session timeout of Portal with CMS Server

Hi Experts,
We have a custom application build on our portal which will launch the reports of InfoView. It works fine untill the portal session timeout. Whenever the session timeout occurs and reloads it I am unable to launch the reports and getting the below exception.
com.crystaldecisions.sdk.exception.SDKException$OCAFramework: Unable to reconnect to the CMS server_ip:6400. The session has been logged off or has expired. (FWM 01002)
Portal is configured with SSO. Please adviese how to set the settings of session timeout in such way that Portal sync session timeout with CMS server.
Thanks in Advance,
Chinaa.

Hi ,
There is no such option to sync Portal timout with CMS server.
To resolve your problem you have only option to set your CMS server timout to MAX value.
Thanks
Anil

Need to warn user of session timeout in BSP app hap_document......

Hi,
We're using the hap_document app to allow employees to change appraisal documents in ESS and for managers to create them thru MSS....
When employees have their documents open for more than 1 hour, the next time they click on save, it takes them to the session timeout (ICM, version 6040, module icxxthr_mt.c)....
Is there a way to add a timer to the document.htm or body.htm pages in the application to start a timer, reset it each time user clicks on save, and warn him with a popup when we're within 5 minutes to a timeout...
I've read messages on the BSP thread that say...
"Document.htm is split in two frames. One hidden to enable session handling, the second one visible which contains the document.
So the document.htm is not refreshed, the second frame is refreshed. I tried your approach as well and was not able to tie the script to the second frame.
Regards and Groetjes,
Maurice"
I've also read Thomas's stateful/stateless timeout parameters article...
Can anyone help me with where I would put the timer javascript code (if not in document.htm or body.htm) and which timeout parameter to check...
Thanks for all your help,
Venkatesh

Look at the sample code..Will solve your problem..
<%@page language="abap" %>
<%@extension name="htmlb" prefix="htmlb" %>
<script type="text/javascript">
function remind() {
var msg = "Your Session will be timed out in 10 Secs";
alert(msg);
</script>
<htmlb:content design="design2003" >
<%
data: v_rem type string.
DATA: port TYPE STRING.
port = request->get_header_field( if_http_header_fields_sap=>server_port ).
DATA: services TYPE TABLE OF ICM_SINFO.
CALL FUNCTION 'ICM_GET_INFO' TABLES SERVLIST = services.
FIELD-SYMBOLS: <service> TYPE ICM_SINFO.
DATA: wait TYPE STRING.
READ TABLE services ASSIGNING <service> WITH KEY service = port.
wait = <service>-KEEPALIVE - 10.
CONDENSE wait.
concatenate `'remind(` wait `)',2000` into v_rem.
%>
<htmlb:page onLoad = "setTimeout(<%= v_rem %>)"
              title = " " >
    <htmlb:form>
      <htmlb:textView text   = "Hello World!"
                      design = "EMPHASIZED" />
      <htmlb:button text    = "Press Me"
                    onClick = "myClickHandler" />
    </htmlb:form>
</htmlb:page>
</htmlb:content>
<i>* Reward each useful answer</i>
Raja T

How to check and change the dafault session timeout of the Portal?

Hello,
When leaving a portal page open without using it for a certain amount of time and then accessing it again the Session times-out.
Where can I check and change this default time-out time in case I would like to extand it for the end users?
Roy

Hi Roy,
Session timeout includes multiple settings (J2EE setting and SSO setting at User Management).
Defining the Timeout in J2EE Session
1. Open file web.xml (path depends on the version of EP6.0. If it is based on NW04, then
..\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF
2. Enter a value in minutes under <session-timeout>. The value should roughly correspond to the length of a synchronization cycle. The default is 30 minutes.
After a successful login, it receives a SSO ticket which is valid for longer duration (generally 8 hrs, default which you can changed using "System Admin" as mentioned by Yoel.
Thanks,
Swapan

Setting Session Timeout for HANA Cloud Portal

Hi all,
is there any way for setting the session timeout period on HANA cloud Portal?
If not, what is the predefined session timeout?
Thank you in advance.
Silvia Grabmann

Hi Silvia,
Session timeout is 20 minutes and cannot be changed. In fact it is configured at the platform level.
Regards,
Ifat.

How to configure session timeout for SAP Netweaver Portal

Hi,
I would like to know the way to configure the session timeout for SAP Netweaver Portal.

Hi Kim,
the solution for your question is in this thread.
500 Connection timed out
if it is helpful award me points.
Regards,
R.Suganya.

How to configure a session timeout for DynPro applications?

Hello,
1. Where can I configure the session timeout of the DynPro applications?
2. Can I configure a session timeout per application and how do I do that?

Hello Heidi,
I am not familiar with this property:
1. Where can I configure it?
2. Does it apply to every application at the portal?
3. What if I would like to configure just one application?
By the way, I have noticed that the DynPro application has an expirationTime property. The documentation says this:
Specifies the lifetime in seconds of a Web application on the server before the Web application is terminated by the server. The value of the DefaultExpirationTime parameter of the system configuration is used as the default value.
My question is if someone tried to use this property?
Message was edited by: Roy Cohen

Re: [iPlanet-JATO] Re: session timeout when not submitting to a handler

Mark--
I know what's happening here, but am curious about your approach. You said
in an earlier email that you were generating links directly to JSPs, but
from what you are describing, you are generating JATO-style links to access
JATO pages. Nothing wrong with that, but there is a signficant difference.
Actually, it just occurred to me, I'm wondering what your URLs look like.
The way the request dispatching works in JATO is it ignores anything after
an initial "." in the final part of the URL path. For example, a request
for "/myapp/module1/MyPage.jsp" doesn't actually try to hit the JSP, instead
it tries to hit the JATO page "/myapp/module1/MyPage".
The end result is that you may think you are accessing a JSP directly, but
are instead accessing a JATO page. The reason the request dispatching works
this way is because it is illegal to access JATO JSPs directly, and there is
actually a (disabled) JATO feature that piggybacks on the use of the
dot-delimited URL.
So, now I need to understand your intent. I wasn't really sure why you were
generating direct JSP/page links to begin with. This works against the Type
II architecture JATO uses, in which all JATO requests go back to the
controller servlet.
If you are trying to design something like a menu page, you may have thought
that it was burdensome to create a number of HREF children, plus implement
event handlers for each of them. This definitely would be burdensome beyond
just a handful of links, but this is why JATO provides other mechanisms for
doing what I'll call here "polymorphic HREFs".
Assuming this menu page scenario, the easiest thing to do is to simply use
one HREF child on the page, and add a value to it each time it is rendered
that distinguishes it from the other instances on the page. In your event
handler for the HREF, you simply check this value and use it to decide which
page to forward to. You can add a value to an HREF or Button by using the
"addExtraValue()" method. Or, if you are using JATO 1.2, you can add extra
query string NVPs right in the JSP document using the "queryParams"
attribute of the <jato:href> tag. Thus, your one HREFchild and event
handler become "polymorphic" because what they do depends on the context in
which they are invoked.
Now, I still don't have confirmation that this is what you were trying to
do, so until I do, let me explain the exception you're seeing. JATO assumes
that when a request comes in for a page that includes the pageAttributes
NVP, it is a request coming from a previously generated JATO page. Because
of the way JATO works, this means that the request dispatching code should
send the request back to the originally rendered page. For example, if Page
A renders an HREF, which the user then activates, JATO sends the request
back to Page A for handling. All of the HREFs and forms generated during
rendering of Page A actually refer back to Page A, regardless of where those
links or buttons actually pass the request in their event handlers/Command
objects.
So, what's happening when you include the pageAttributes in your HREFs is
that JATO is assuming that a request is being sent to the target page, with
the assumption that the target page has a mechanism in place to handle the
request. This assumption relies on the specification of the "originator" of
the request being specified in the request. For links/HREFs, the name and
value of the HREF is sent along with the request. For forms, the name and
value of the button that was pressed are sent in the request. JATO uses the
presence of these name/value pairs to decide which event handler, or which
Command object, to invoke to handle the request.
The exception you are receiving is saying that there was no object on the
target page that indicated it could handle the request. This is to be
expected, since you have not specified a query parameter that indicates
which CommandField child is responsible the request. However, this is where
I see the disconnect, because that is not what I believe you were trying to
do (as explained above).
So now, given all the information above, can you tell me what you're trying
to accomplish, and whether or not the info I've given you has helped you to
design a mechanism more in line with a JATO approach? If not, given that I
understand what you're trying to do, I can offer a more concrete solution.
Todd
----- Original Message -----
From: <Mark_Dubinsky@p...>
Sent: Monday, November 05, 2001 2:54 PM
Subject: [iPlanet-JATO] Re: session timeout when not submitting to a handler
This is the exception we get:
(And BTW, leaving a blank value for the pageAttributes doesn't help)
[05/Nov/2001 17:49:18:4] error: <portalServlet.processRequest>
javax.servlet.ServletException: The request was not be handled by the
specified handler
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at
javax.servlet.ServletException.<init>(ServletException.java:107)
at
com.putnaminvestments.common.jato.ApplicationServletBase.dispatchRequ
est(Compiled Code)
at
com.putnaminvestments.common.jato.ApplicationServletBase.processReque
st(Compiled Code)
at
com.putnaminvestments.bp.portal.portalServlet.processRequest(Compiled
Code)
at
com.putnaminvestments.common.jato.ApplicationServletBase.doPost(Compi
led Code)
at
com.putnaminvestments.common.jato.ApplicationServletBase.doGet(Compil
ed Code)
at javax.servlet.http.HttpServlet.service(Compiled Code)
at com.putnaminvestments.bp.bpServletBase.service(Compiled
Code)
at javax.servlet.http.HttpServlet.service(Compiled Code)
at
com.netscape.server.servlet.servletrunner.ServletInfo.service(Compile
d Code)
at
com.netscape.server.servlet.servletrunner.ServletRunner.execute(Compi
led Code)
at com.kivasoft.applogic.AppLogic.execute(Compiled Code)
at com.kivasoft.applogic.AppLogic.execute(Compiled Code)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at com.kivasoft.thread.ThreadBasic.run(Compiled Code)
at java.lang.Thread.run(Compiled Code)
--- In iPlanet-JATO@y..., "Todd Fast" <Todd.Fast@S...> wrote:
Mark--
Initially we tried to add the pageAttributes NVP as well, but that
was
causing an exception, so we stopped doing that.That's odd--what was the exception?
Our problem now is that when the SessionTimes out it does not go
to
onSessionTimeout method as in processRequestMethod of the
ApplicationServletBase it looks for pageAttributes. If it is notnull
then only onSessionTimeOut method is called.This is sadly the only technique for determining if a session hastimed out
and a new one been created, versus the initial creation of thesession.
Is there any work around for this? Maybe you can suggest how topass
the pageAttributes without causing the initial exception?Definitely--let me know what the exception was and I'll be able tosuggest
something. However, it shouldn't really be any harder thanappending a
"jato.pageAttributes=" empty NVP on the HREF.
Todd
Todd Fast
Senior Engineer
Sun/Netscape Alliance
todd.fast@s...
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp

OK, here's what I'm trying to do: We have, like you said, a menu
page. The pages that it goes to and the number of links are all
variable and read from the database. In NetD we were able to create
URLs in the form
pgXYZ?SPIDERSESSION=abcd
so this is what I'm trying to replicate here. So the URL that works
is
pgContactUs?GXHC_GX_jst=fc7b7e61662d6164&GXHC_gx_session_id_=cc9c6dfa5
601afa7
which I interpreted to be the equivalent of the old Netd way. Our
javascript also loads other frames of the page in the same manner.
And I believe the URL-rewritten frame sources of a frameset look like
this too.
This all worked except for the timeout problem. In theory we could
rewrite all URLs to go to a handler, but that would be...
inconvenient.

Session Timeout Thoughts

I saw a post from awhile ago that you can't change the session timeout in iTunes U. Is this still true?
Our users are having timeout issues and we have an unfortunately lengthy login process to get back into iTunes U so I had some thoughts on the Site Login URL.
We use a portal to authenticate our users who then click an SSO link to take them to a jump page that assembles their credentials and generates an SSO link into iTunes U. I'd really like to avoid having to go back through the portal to get users back into iTunes.
What if, instead of passing just the destination back to the site login URL, iTunes U passed a full SSO link. This way, I can just point my site login URL to the jump page. The jump page can then parse the SSO link to verify the user's credentials and just create a new SSO link right back into iTunes U, almost transparently to the users.
Are there any better options to solve this problem? I know this would require some modification on the iTunes U side, but it seems like it'd solve some problems.
Thanks
Jason

Hi Jason,
I don't think I did a good job at explaining what I'm trying to get at. Sorry, let me try another way.
The problem is not one of security necessarily. If you get a signature back from Apple, sure, your jump site can verify that Apple sent you warnings about sessions that are about to timeout. The problem is that Apple cannot distinguish our local users from the identity and credentials we send. It might seem that way in specific instances (because some sites have an elaborate identity/credentialling scheme), but it is not true in the general case. It is entirely possible that scores of people can share exactly the same identity/credential info ... that is totally legal in the iTunes U world (and why I urge people not to think of "users" and "accounts" whenever they think iTunes U). For example, lessay I have a site that has a very simple credentialling scheme, say ...
Administrator@urn:mace:itunesu.com:sites:uic.edu
Instructor@urn:mace:itunesu.com:sites:uic.edu
Student@urn:mace:itunesu.com:sites:uic.edu
Authenticated@urn:mace:itunesu.com:sites:uic.edu
Unauthenticated@urn:mace:itunesu.com:sites:uic.edu
All@urn:mace:itunesu.com:sites:uic.edu
Further, let's say that I "anonymize" my users by sending no identity info to Apple. So if Apple sends my jump site the following:
credentials=Student@urn:mace:itunesu.com:sites:uic.edu
identity=
time=123456789
signature=stringwith_bunch_ofhex
which one of my local users does that belong to? ... whose session should I recredential? Sure, you can make a complex credentialling scheme that narrows usage down to the specific person ... but I would urge you to think of credentials as a kind of "hall pass" ... a token that lets you into a specific place within iTunes U ... and not as a way to identify someone. Remember that Apple has to use a system that applies in the general case and what I have above is totally legal. If I want, I can obfuscate my users to be certain that only -I- know who's accessing iTunes U.
Recall, too, the way that iTunes U is setup. Your transfer CGI sends a URL to Apple and Apple sends you back loads of HTML/JavaScript/CSS in return. Your transfer CGI passes all of it back to the end user. The heart of the HTML Apple sends is this itmss: redirect:
itmss://deimos.apple.com/WebObjects/Core.woa/BrowsePrivately/uic.edu?
credentialKey=1474615910&identity=2253747564656e7422203c5374756
4656e74407569632e6564753e202853747564656e7429205b305d&time=
1203747692&signature=32d169daa7a282f8c7efa7d4f7f7fb0dceaac507c26
f205123473f09d6b9ef50&x=true&ignore.mscache=8974210
That is how Apple talks to your end users. The session is private ... between Apple and your end users. The only way for you to know which session belongs to which local user is for Apple to send you that itmss link and say, in effect, "the session associated with this link is about to time out". Your jump site would have to maintain a connection between itmss links, your local users, and the credentials associated with both. But if your site is -already- caching local user/credential info, there is no need for Apple to send your creds/identity back to you.
As ever, if my understanding is itself cloudy, I bow to Duncan. He knows all and I am happy to be corrected. Like you guys, I am here to learn.

Session Timeout - Process as a webservice

Hi ,
I am using ALBPM v5.7.
In this we are exposing our process as webservice.
We are Invoking these webservice methods from portal deployed in BEA Weblogic Server,
The procedure we are following is , starting the session and then invoking our methods -- method1 and method2.
But , After invoking method1, In the portal, we are waiting for five minutes and then trying to invoke method2 of BPM using the same session,
When we do this, It is throwing an exception,
Invalid Session.
We observed that if we invoke method2 before five minutes then it is working fine.
So do we have any session timeout for the BPM Process, when we expose our process as a webservice.
If so , could you please help me in resolving this issue?
Thanks & Regards,
Krishnaveni.

Just input paramters inside the Begin Activity...
Right Click on the Process and open Process Web-Service and add a Web-Service to it..
Then start the engine in Studio..
And then click on Launch Deployed WebServices Webapp..
And you would get the endpoint..

How can i redirect a page to Login screen when sessionis timeout???

I have a problem in my portal development.
I set the "<b>Session timeout= 01</b>" parameter in the<b> Visual Administrator</b>
server_0 > services > Web Container
        Runtime > sap.com/irj > irj    (view button)
However, when the session is timeout then the page become to be "red"!!! That is, there is an Exception. I'd like to redirect the page to the "Login screen", but I don't know how. <b>Does anybody know how can I do it</b>?
Thanks in advance.

Hi,
    the http session invalidation must be checked at application level do it DYNPAGE only .you can call the following method.
public void expireSession(IPortalComponentRequest request)
          long lastAccessedTime=request.getServletRequest().getSession().getLastAccessedTime();
          Date currentDate = new Date();
          Calendar currentDateCal = new GregorianCalendar();
          currentDateCal.setTime(currentDate);
          long systemTime = currentDateCal.getTimeInMillis();
          long sessionExpiryTime = systemTime - lastAccessedTime;
          long sessionExpiryTimeProp = 600000; //dont hard code.get from property file
          if(sessionExpiryTime >= sessionExpiryTimeProp)
               try
                   IPortalComponentResponse response=(IPortalComponentResponse)this.getResponse();
                    String sessionExpiryPage ="/irj/servlet/prt/portal/prtroot/com.sap.portal.masthead.LogOutComponent?logout_submit=true";
                    response.write ("<script language="javascript">");
                    response.write("parent.window.location.replace('"+sessionExpiryPage+"','','toolbar:No,status: No,location: N0');");
                    response.write("</script>");
               }catch(Exception e)

Portal Session Timeout - ICM/Webdynpro/POWL

Similar Messages

Maybe you are looking for