alternative to timedtrigger

[former_member186444]

we have a Web dynpro application that takes over 2 minutes to run. The portal session, however, times out after 2 minutes. I have looked at the timedtrigger UI element (to force a round trip) but it seems this any action associated with this only kicks in when there is no server side activity. So, the action does not happen until after the code is executed. Certainly, this is what my testing seems to show me. Is my understanding correct?

If so, is there any alternative method I can use to stop the session timing out?

[guillaume-hrc]

Hi,

I feel forced to ask: "Why a timeout so short"?

2 minutes is a long time in dialog processing for the user to simply wait!

Maybe you could embed the processing within a notification service so as to:

1) feed him/her with some progress in the processing

2) let the users go on with their lives in your WDA application

But, I'm not an expert on this precise feature.

http://scn.sap.com/docs/DOC-2274

http://enterprisegeeks.com/2009/06/03/abap-freak-show-june-3rd-web-dynpro-abap-notification-service/

Best regards,

Guillaume

[former_member186444]

thanks for the info, I'll take a look at that. I was just trying out something I noticed Thomas Jung suggest to someone else - calling a function using 'STARTING NEW TASK' but unfortunately that doesn't seem to work for me either.

I've spoken to our Basis guys about the 2 minutes before and they tell me they are following SAP guidelines in setting it 2 minutes. It does seem very short to me. What would you suggest and do you have any information that backs up making it longer (so I can show them the proof!).

thanks again.

[former_member186444]

which parameter is this we're talking about? Is it one of these?

icm/conn_timeout

icm/keep_alive_timeout

[guillaume-hrc]

Hi,

If not mistaken, we are talking about the processing timeout (a.k.a. PROCTIMEOUT within icm/server_port_<n>)

Check this: http://help.sap.com/saphelp_nw70ehp2/helpdata/en/7b/72092aaa1342c5a3af7ce0b9a11ff9/content.htm

If this page does indicate 60 seconds as recommended value for PROCTIMEOUT, it also says that it can be tuned per service as needed (up to a recommended 10 minutes value)

In systems where the standard timeout setting of 60 seconds for the keep-alive and processing timeouts is not sufficient due to long-running applications, SAP recommends that both the TIMEOUT and PROCTIMEOUTparameters are set for the services concerned so that they can be configured independently of each other. TheTIMEOUT value should not be set unnecessarily high.
We recommend you set this parameter as follows:
icm/server_port_0 = PROT=HTTP,PORT=1080,TIMEOUT=60,PROCTIMEOUT=600
in order to allow a maximum processing time of 10 minutes.

Also check this OSS Note: https://service.sap.com/sap/support/notes/824554

Best regards,
Guillaume

[former_member186444]

funnily enough, ours is set to the standard 60 seconds for that parameter so it must be something else that's causing me to time out after exactly 2 minutes.