on 06-26-2012 5:23 PM
Hi All,
We have a requirement for a long timeout for a single WebDynpro application.
The application will be a custom Clock In/Out WD ABAP application. We will run the application in some instances outside of the portal and SSO context. I'm I'm OK with using the PROCTIMEOUT param as usual. As a central Clock In/Out kiosk however it is desired to not have to re-authenticate for the execution of the WD component.
So...
1.) Supervisor or some other person launches the application and authenticates using seperate set of credentials to execute component.
2.) Multiple Users clock in/out typing PERNR or swiping badge.
3.) Component itself remains running for x hours without reauthentication. (x=many)
Long timeout is for this application only. All others run using existing timeouts.
Any ideas on how to pull this off?
Thanks,
Doug
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can set ICF service specific timeouts.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Doug,
Were you able to solve this puzzle ?
Chris Thomas
Duke University
email address removed by moderator
Message was edited by: Marilyn Pratt
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 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
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.