Application Expiration time

Hi Experts,
My all WebdynPro Java applications are getting expired after 1-2 minutess. Even I have set parameter Expiration time = 1000 sec for all my application.
Please let me know if I am missing something.
Regards,
Rohit

Hi,
Check the expiration time of your WAS. Because, even if u increase the Expiration time of ur application if the WAS expiration time is less, then its of no use.
Regards,
Poojith MV

Similar Messages

Application Expiration time message change

Hi,
I would like to disply our own custom message when Web Dynpro application expires the time instead of displaying standard message "The Web Dynpro application 'MyWDApp' has expired. Please restart the application. Use the Refresh entry in the iView tray or use the browser Refresh button to restart the iView. ".
Please let me know where to change this message.
Thanks

No info

Webdynpro application expired

hi
i am getting this following error after runnig this
500 Internal Server Error
SAP J2EE Engine/7.00
The Web Dynpro Application 'CustomerApp' has expired. Restart the application using the Refresh button or via the following link CustomerApp.
Details: No details available
any suggestions ? its urgent ?

Hi,
U get that error whenevr ur application expiration times expires
or either some one is deploying any application on the same
server on which u r running ur application at the same time.
Regards
Surender Dahiya

Timeout Session - Expiration time of Webdynpro application

Hello,
I set the sap.expirationTime property of my application to 1 hour, know the expiration time of my application is one hour. After time out (one hour) I am getting default 500 internal server error page. But as per the requirement we need to display a custom message instead of 500 internal server Error.
i.e.need to Redirect to Custom page with custom message instead of 500 internal server error page.
i try to follow as per this link [Timeout of a WebDynpro session;
but found that in NW 7.0 the parameter sap.sessionExpiredURL is not available anymore. How can archive this?
Conclusion: If there is a timeout session, instead of 500 internal error page how to display a custom messages?
Thanks & Regards
Maha
Edited by: Maha Hussain on Feb 10, 2009 12:00 PM

Hi Maha,
With sap.expirationTime property, the application will certainly be expired.
If your requirement suits for the scenario just try out the following workaround.
If you want show a custom message only, you can use TimedTrigger UI Element instead of setting expirationTime just set dealy for this and in the action kust navigate to the view and displaye the custom message in that.
Regards,
Siva

Setting the session expiration time in ESS/MSS application

HI Experts,
how can we control the expiration time of a particular I view ? we have implemented ESS\MSS application on our portal . The session is getting expired after 5 minutes . We would like to increase this expiration time.
Thanks
Surender Dahiya

Surender,
Most of the ESS/MSS applications are webdynpro for java applications
check DefaultExpirationTime in the link
http://help.sap.com/saphelp_rc10/helpdata/en/43/8a1a8ece230c8ce10000000a11466f/content.htm
but you can set expiration time at individual application level using sapexpirationtime which will take the precedence
Thanks
Bala Duvvuri

Webdynpro Applications expire all the time

Hi,
I am facing a huge problem with my WebDynpro applications. I am running SAP EP 6.0 SP and a separate WebAS 6.4 SP 12.
I am not deploying my WebDynpro applications on the SAP Enterprise Portal WebAS Server.
The problem that I have regardless of integration in Enterprise portal is that my WebDynpro applications time out all the time.
Even though I click around in the IView, after a few minutes, I get a message,
<b>The WebDynpro application has expired. Please click on this link XXX to restart the application</b>
I have gone to the configuration adaptor and set the default expiration time to 3600. ..I increased it just to try..to 7000..
I have also additionally set the time in each WebDynpro applications to sapExpirationTime = 3600
I am using fully qualified domain names so that shouldn't be a problem.
Just to know...the Portal and the WAS used for deployed content run on the same machine on different port.
Has anyone faced this problem and found a solution?

Hi,
I am facing a huge problem with my WebDynpro applications. I am running SAP EP 6.0 SP and a separate WebAS 6.4 SP 12.
I am not deploying my WebDynpro applications on the SAP Enterprise Portal WebAS Server.
The problem that I have regardless of integration in Enterprise portal is that my WebDynpro applications time out all the time.
Even though I click around in the IView, after a few minutes, I get a message,
<b>The WebDynpro application has expired. Please click on this link XXX to restart the application</b>
I have gone to the configuration adaptor and set the default expiration time to 3600. ..I increased it just to try..to 7000..
I have also additionally set the time in each WebDynpro applications to sapExpirationTime = 3600
I am using fully qualified domain names so that shouldn't be a problem.
Just to know...the Portal and the WAS used for deployed content run on the same machine on different port.
Has anyone faced this problem and found a solution?

[Forum FAQ] Fixing scheduled task Next Run Time displaying as expired time plus days to delete

Symptom:
We used Task Scheduler to create a scheduled task. For example, we configured a daily task, starting from 3 AM 9/3/2014, recurring the task every 1 day, and set the expiration time as 3 AM 9/3/2015 (See Figure 1). Under
Settings tab, we checked If the task is not scheduled to run again, delete if after:
option, and set the value as 30 days (See Figure 2).
However, in the Task Scheduler Library snap-in, we saw that the Next Run Time of the task is 3AM 10/3/2015, which equals expiration date plus days to delete (See Figure 3), but the right value should be 3 AM 9/2/2014 because the task has never been run.
Figure 1
Figure 2
Figure 3
Cause:
This is a Task Scheduler interface displaying issue. Although the next run time that is displayed in the Task Schedule is incorrect, the trigger will be fired correctly.
Solution:
We can install the hotfix in the following KB article to fix the displaying issue, though the symptom in the article is different.
An incorrect value for Next Run Time is displayed when you specify multiple triggers to schedule a task in Windows Vista, Windows 7, Windows Server 2008 or Windows Server 2008 R2
http://support.microsoft.com/kb/2495489
After installing the hotfix, we need to restart computers to make it take effect.
In this example, after installing the hotfix and restarting the computer, we see that the next run time of the task is displayed correctly in Task Scheduler (Figure 4).
Figure 4

I am not running out of space, but I do have the same problem. Every so often TM does a backup which is about 60 GB bigger than expected.   The extra is always a new backup of /System /Applications /usr etc. - that is the 'system files'.
The key thing is, as you have noticed:
Examining the content of the latest backup, the one that did not fail, shows that some system directories, /Applications, /usr, and /bin are missing
As a consequence the next backup is, in my case, 60 GB bigger because it includes all the system files.
It is as if 'systemFilesExcluded' was turned on for the previous backup (the one that 'did not fail'). But I have looked in the .exclusions.plist for this backup and it is exactly the same as for other backups and does include:
        <key>systemFilesExcluded</key>
        <false/>
It seems that TM is treating this as if <true/>.
Like you, I have done a disk verify and it finds no errors.
I think this must be a bug. I have had this on four occassions since upgrading to Mountain Lion. And it is doing a large one right now - I have caught it in the act!

After application expired, navigate to last Web Dynrpo screen

Hi all,
When the application is not used for 30 minutes, the Web Dynpro application goes "time out". I get the following message:
500 Internal Server Error
The Web Dynrpo Application "<appname>" has expired. Restart the application using the Refresh button or via the following link <appname>.
Is it possible to return to the last screen when the user pushes the <appname> link?
Otherwise the user has to click and wait several seconds for each screen to go to the point where the application was before the timeout?
Is there any one who solved a similar problem?
Thanks in advance and kind regards,
Bart Elshout

Hi,
The problem which u have stated regarding the time-out not only depends on the webdynpro application, but also on the Web AS time out. You can set the expiration time in the application of webdynpro project (Right Click on ApplicationName --> Properties --> Expiration time) and set the time in seconds (ed:- 60000 for 10 min)
But if the time out on the server is set to 30 min, the application definitely displays the 500 Internal server message.
Regards,
Poojith MV

Expiration time

Hi,
What is the purpose of expiration time in web dynpro application ?
Thanks,
Ravi

Hi ravi,
At design time, you can declare several configuration properties for your Web Dynpro application. Examples of this are the specification of an expiration time for the application (ExpirationTime) or the definition of the HTML page to be used as the logoff page (LogoffURL). The configuration property Authentication, which describes the Boolean value for the use of the authentication, is also included in the configuration options.
You set the properties of the application configuration in the SAP NetWeaver Developer Studio. For some properties, the values of the Web Dynpro system configuration are adopted if you have not already set them explicitly in the application configuration. For example, the value of the DefaultExpirationTime parameter of the Web Dynpro system configuration is used if you have not assigned a value to the ExpirationTime property of the application configuration.
The configuration property ExpirationTime describes the lifetime in seconds of a Web Dynpro application on the server before the Web application is terminated by the server. The value that is assigned to the DefaultExpirationTime parameter in the system configuration is used as the default value.
ExpirationTime 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.
Regards,
Sunaina Reddy T
Edited by: Sunaina Thatipally on Apr 29, 2009 9:13 AM
Edited by: Sunaina Thatipally on Apr 29, 2009 9:18 AM

Webdynpro expiration time

Is it possible to set an expiration time for a particular Web dynpro application
guidance please

Hi,
Yes We can set in the application properties,
Please go thr below, i hope it will help you
http://help.sap.com/saphelp_nw04/helpdata/en/2c/7a0a00c8bb5d42b87e58419c09bf43/content.htm
Thanks,
Sreeni.

Application session time out

Hello
i have an application deployed on weblogic 11. after 30mins the application session times out.
1.how can increase this time.
2. can this be done in weblogic since on the application side there is no configuration for the time out.
please assist me
Thanks

Hello;
On middleware the default should be 3600 seconds.
To change :
Login to the WebLogic Administration Console
Under domain structure click Deployments
Click on the "em" Enterprise Application
Click on the Configuration Tab
Set "Session Timeout (in seconds):" to 7200 ( or whatever you want )
Hit the Save button to save your changes in the deployment plan
I would make sure an idle timeout in not set in the database profile as well.
Best Regards
mseberg
Also worth a look :
How to Troubleshoot Oracle Fusion Middleware 11g OPMN Issues? [ID 1303000.1]
Edited by: mseberg on Oct 28, 2011 12:41 PM

Re: Running the same (Forte) application multiple times -for different

Hi
We had the same problem - how to deploy a number of identical applications, using each their own db.
(for training).
The solution we used is to wrap the entire application into different applications by using a very small
module called KURSUS01, KURSUS02 etc, that did nothing but call the start procedure of the main app.
Then in the dbsession connect, we made a call appname to get the application name, and appended the
first 8 chars to the dbname. Thus our dbnames now points to logicals name: rdbdataKURSUS01, rdbdataKURSUS02 etc.
All this allows us to deploy the identical apps in the same env, or change one version, and run both the old
and new program on the same pc and server at the same time (eg. KURSUS01 and KURSUS02).
I also think this is a kludge - but it works nicely!
Jens Chr
KAD/Denmark
-----Original Message-----
From: Haben, Dirk <[email protected]>
To: 'Soapbox Forte Users' <[email protected]>
Date: 15. januar 1999 09:41
Subject: Running the same (Forte) application multiple times - for different business clients.
Hi All
We have a number of different business clients all willing to use our
application.
The (forte) application is to run on our machines etc for these (business)
clients.
All (business) clients will have their data kept in separate Oracle DBs
(instance).
The problem now is that the entire (forte) application is written using
DBSessions.
Now, depending on what business client needs to be serviced (so to speak) we
need to attach to the right DB - or use the "right" SO.
The two options we can think of are:
Option1:
Programatic change to somehow "know" what (business) client (DB) I'm talking
about and then use the right DB.
Pro:
Only one forte environment to maintain
Can run multiple (business) clients on same PC at the same time
Con:
Requires many program changes
bending O-O rules(?)
can't dynamically name SOs so can it be done at all? (ResourceMGRs maybe?)
Option2:
Use separate environments! One for each business client.
Pro:
More defined separation of app and data,
SLA-easy
Con:
Maintain "n" number of environments
Can only run the application for one environment (business client) at a time
on one PC - Big Negative here!
Not knowing any feasible solution to option 1 (without much code changes and
developer moaning) I would go for option two; as I have already worked on
multi-environment setups on VMS back at the Hydro (hi guys).
I would appreciate any comments from anyone who has solved this problem.
How, Why Pro Con etc.
TIA,
Dirk Haben
Perth, WA
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Hi
We had the same problem - how to deploy a number of identical applications, using each their own db.
(for training).
The solution we used is to wrap the entire application into different applications by using a very small
module called KURSUS01, KURSUS02 etc, that did nothing but call the start procedure of the main app.
Then in the dbsession connect, we made a call appname to get the application name, and appended the
first 8 chars to the dbname. Thus our dbnames now points to logicals name: rdbdataKURSUS01, rdbdataKURSUS02 etc.
All this allows us to deploy the identical apps in the same env, or change one version, and run both the old
and new program on the same pc and server at the same time (eg. KURSUS01 and KURSUS02).
I also think this is a kludge - but it works nicely!
Jens Chr
KAD/Denmark
-----Original Message-----
From: Haben, Dirk <[email protected]>
To: 'Soapbox Forte Users' <[email protected]>
Date: 15. januar 1999 09:41
Subject: Running the same (Forte) application multiple times - for different business clients.
Hi All
We have a number of different business clients all willing to use our
application.
The (forte) application is to run on our machines etc for these (business)
clients.
All (business) clients will have their data kept in separate Oracle DBs
(instance).
The problem now is that the entire (forte) application is written using
DBSessions.
Now, depending on what business client needs to be serviced (so to speak) we
need to attach to the right DB - or use the "right" SO.
The two options we can think of are:
Option1:
Programatic change to somehow "know" what (business) client (DB) I'm talking
about and then use the right DB.
Pro:
Only one forte environment to maintain
Can run multiple (business) clients on same PC at the same time
Con:
Requires many program changes
bending O-O rules(?)
can't dynamically name SOs so can it be done at all? (ResourceMGRs maybe?)
Option2:
Use separate environments! One for each business client.
Pro:
More defined separation of app and data,
SLA-easy
Con:
Maintain "n" number of environments
Can only run the application for one environment (business client) at a time
on one PC - Big Negative here!
Not knowing any feasible solution to option 1 (without much code changes and
developer moaning) I would go for option two; as I have already worked on
multi-environment setups on VMS back at the Hydro (hi guys).
I would appreciate any comments from anyone who has solved this problem.
How, Why Pro Con etc.
TIA,
Dirk Haben
Perth, WA
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Can't open iTunes, it said it has failed to start because MSVCR80.dll was not found, and I re-installed application many times and still problem persist, how do I solve this?

can't open iTunes, it said it has failed to start because MSVCR80.dll was not found, and I re-installed application many times and still problem persist, how do I solve this?

Try the following user tip:
Troubleshooting issues with iTunes for Windows updates

How to override the expiration time in SOA Workflow OIM?

Hello everyone,
I am working on SOA Workflows to develop the Approval Process in OIM 11g R2 PS1.
I have a requirement as follows:
The request should escalate after 3 days of the request submission to the approver's manager. This configuration i have done in 'Deadlines' , Escalate after and given the duration also.
But this request should not expire after escalation. So, right now its escalating after 3 days but again after 3 days it is getting expired(i.e. on 6th day).
I have to override this expiration with 'Never expire'. How can I achieve that? Any idea?
Regards,
Neha Gupta

Thank you, that was it!
I left the Time-to-Live Override to the default value -1. The new expiration time kicked in after I set it to the right value.
Thanks again.
Hong

Remove password expiration time limit for ocs users

Hello,
I want to know how to remove password expiration time limit for ocs (11gR2) users? In our system all user accounts are getting expired in 1 week. I have to remove expdate. (profile was changed)
Thx

SQL> select * from dba_profiles where RESOURCE_NAME LIKE 'PASSWORD_LIFE_TIME';
PROFILE RESOURCE_NAME RESOURCE     LIMIT
DEFAULT PASSWORD_LIFE_TIME PASSWORD     180
MONITORING_PROFILE PASSWORD_LIFE_TIME PASSWORD     DEFAULT
SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;
Profile altered.
SQL> select * from dba_profiles where RESOURCE_NAME LIKE 'PASSWORD_LIFE_TIME';
PROFILE RESOURCE_NAME RESOURCE     LIMIT
DEFAULT PASSWORD_LIFE_TIME PASSWORD     UNLIMITED
MONITORING_PROFILE PASSWORD_LIFE_TIME PASSWORD
To change the password for a user:
alter user username identified by new_password;
Edited by: hitgon on Apr 30, 2012 7:33 PM

Application Expiration time

Similar Messages

Maybe you are looking for