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

Similar Messages

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

Don't redeploy the whole portal application each time we change a portlet

Hi folks,
I have around 50 struts portlets in my weblogic portal, following the struts portlet architecture in the documentation, so we have now one ear which ends up that whenever we change any portlet we will have to redeploy the whole portal :( !!!
I have read about federated portal, but it seems that its great advantage is when your portal wants to consume remote portlets deployed in remote producers, but this is not my case, since all my portlets are local ones, so I think there might be a simpler solution (*like in websphere where we have separate war for each portlet*)
any suggestions ? would be great if you can provide any resources or links document steps needed to accomplish this
Thanks a lot :)

Hi Kevin,
I made sure through the monitor servlet that it's WSRP V2
---- localLogin.portlet------
<?xml version="1.0" encoding="UTF-8"?>
<portal:root xmlns:netuix="http://www.bea.com/servers/netuix/xsd/controls/netuix/1.0.0"
xmlns:portal="http://www.bea.com/servers/netuix/xsd/portal/support/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/servers/netuix/xsd/portal/support/1.0.0 portal-support-1_0_0.xsd">
<netuix:portlet definitionLabel="mainLogin" title="Mainlogin">
<netuix:sharedParameter paramId="UserIdentifier" qname="UserIdentifier"/>
<netuix:content>
<netuix:jspContent contentUri="/pages/mainLogin.jsp"/>
</netuix:content>
</netuix:portlet>
</portal:root>
---remotePortlet.portlet----
<?xml version="1.0" encoding="UTF-8"?>
<portal:root xmlns:html="http://www.w3.org/1999/xhtml-netuix-modified/1.0.0"
xmlns:netuix="http://www.bea.com/servers/netuix/xsd/controls/netuix/1.0.0"
xmlns:portal="http://www.bea.com/servers/netuix/xsd/portal/support/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/servers/netuix/xsd/portal/support/1.0.0 portal-support-1_0_0.xsd">
<netuix:portlet backingFile="com.backing.LoginBackingFile"
definitionLabel="DAdmin" title="Struts">
<netuix:sharedParameter paramId="UserIdentifier" qname="UserIdentifier"/>
<netuix:content>
<netuix:strutsContent action="Log" module="/Log" refreshAction="Log"/>
</netuix:content>
</netuix:portlet>
</portal:root>
and this is the .portlet of another local portlet where i was able to get the shared parameter on.
----LocalPortlet.portlet-----
<?xml version="1.0" encoding="UTF-8"?>
<portal:root xmlns:html="http://www.w3.org/1999/xhtml-netuix-modified/1.0.0"
xmlns:netuix="http://www.bea.com/servers/netuix/xsd/controls/netuix/1.0.0"
xmlns:portal="http://www.bea.com/servers/netuix/xsd/portal/support/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/servers/netuix/xsd/portal/support/1.0.0 portal-support-1_0_0.xsd">
<netuix:portlet definitionLabel="CommCh" title="CommCh">
<netuix:sharedParameter paramId="UserIdentifier" qname="UserIdentifier"/>
<netuix:content>
<netuix:strutsContent action="List" module="/Comm" refreshAction="List"/>
</netuix:content>
</netuix:portlet>
</portal:root>
Thanks :)

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

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?

Apache Bounce Must for Application Message Changes???

Hi Friends,
Is it necessary to bounce apache and oc4j whenever we need to change the text of an application message that is being used on an OAF page?
Thanks,
Amit

Thanks Ashish.
What I got from that post is that it is mandatory to bounce apache for application message changes to get reflected.
What we are doing is -> String strObligStmt = pageContext.getMessage("APPL_SHORT_NAME", "XX_XX_NAME_OF_MSG", msgToken);
OAFormattedTextBean obligStmtBS = (OAFormattedTextBean)webBean.findIndexedChildRecursive("ObligMsg");
obligStmtBS.setText(strObligStmt);
Another thing I got from that post is that we can read the message text directly from FND_MESSAGES and hence get the latest text at all times. But in that case, we will have to substitute the message tokens manually right?
Actually the whole purpose of application messages is getting defeated here. If we have to bounce apache, it is as tedious as sending a code deployment and the flexibility of having application messages is being compromised.
THIS QUESTION IS STILL OPEN.
Thanks,
Amit

How to Define MQ message expire time in OSB Business service.

Hi,
Please let me know the option in OSB business service to set the expiration time for MQ messages. Is it possible?
Thanks,
karthik.

http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/mqtransport/transport.html
transport header "Expiry"
i hope it works :o)

TS1702 I'm getting an " application" cannot be downloaded at this time message. With any app I try to download/update. Why is this happening and what can I do about it ?

I'm getting an " application" cannot be downloaded at this time message. With any app I try to download/update. Why is this happening and what can I do about it ?

I am fighting the same error. I gifted an album to mydaughter and she got that when she tried to cash it in. iTunes support was quick to respond saying the would refund in 5 to 7 days. That was 13 days ago and they will not respond now. Try to contact support to see if they can help. Also be sure you do not have restrictions enabled in settings. If your parental controls are set to block certian content ratings this will give you an error as well.
You could also try to purchacs through the iTunes program on Mac or PC. Check your restrictions there too. If your device is company owned your employers may have restrictions enabled preventing certian apps from being installed. Hope that helps.
E

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

Message tells me it's time to change my 200 black ink cartridge.

So, I installed a new cartridge from the same two pack I have been using. Same message.
Bought another one, same message.
Looked at contacts, looked clean, but GENTLY cleaned them with rubbing alcohol.
Same message.
Any suggestions? I'm pretty sure this copier/scanner is a little over one year old.
As it was quite reasonably priced, if I take it somewhere, it'll probably cost more to fix than a new one.
Bugs me though. Shouldn't be a throw away item.
Thanks all.
Betty

Hi @bettyholt1949,
Welcome to the HP Forums!
I noticed that you are getting a message telling you it's time to change my 200 black ink cartridge. I am happy to look into this for you!
After searching for your product name, the only printer that is coming up for this, is an EPSON Expression Home XP-400. If this is your type of printer, I would suggest to contact Epson Support.
Otherwise, if you have an HP printer that you need help with, please respond with your printer's Product/Model Number. To find your printer's Product/Model Number follow instructions in this link. Finding Your HP Product Model Number, and I will be glad to help!
Hope to hear from you soon!
RnRMusicMan
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" to say “Thanks” for helping!

Itunes won't recognize my password and every time I change I get the same message

itunes won't recognize my password when ipod is connected and every time I change it I get the same message.

Have you restarted your computer? iTunes updated?

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/>

Expiration of messages in Queue + OSB

I am working on a prototype and I have the following scenario :
I have on ALSB (OSB) a JMS based Proxy Service that uses a queue in order to get the messages.
On the queue are put SOAP messages that are secured on message level.
There is a digest expiration on Domain Level that is set to 300 ms by default.
This means that the message once is created and reach the proxy it has to be in this 300 ms time frame.
==> Queue ==>Security Check on JMS Proxy Service ==> Message Flow
Problem nr 1)
In peak time i estimate that since on the queue to have maybe more then 1000 messages and 300 ms would not be enough.
If i modify this digest expiration on Domain Level i affect the other applications that are deployed also on ALSB (OSB) and i expose them to security breach.
Is there a way of solving this ? 300 ms is too small for such thing....
Problem nr 2)
The message pass the proxy (the security on message level) but in the message flow due to some exception (various reasons that are not important now) the transaction is rolled back and the message "is put back on the queue".
Now is the funny part: BEcause of the Digest Expiration Time which is very short the message for sure will expire until the redelivery (ususaly minutes) will be done.
So why a messages that already passed security is checked again on retry ? Can't this be avoided somehow ?
Thank you.

Problem nr 1)
In peak time i estimate that since on the queue to have maybe more then 1000 messages and 300 ms would not >be enough.
If i modify this digest expiration on Domain Level i affect the other applications that are deployed also on ALSB >(OSB) and i expose them to security breach.
Is there a way of solving this ? 300 ms is too small for such thing....I think message expiration can be setup on a proxy level by setting up a WS Security policy on the WSDL rather than at the domain level.
<wsp:Policy wsu:Id="MessageAge" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401->wss-wssecurity-utility-1.0.xsd" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">
><wssp:MessageAge Age="300" xmlns:wssp="http://www.bea.com/wls90/security/policy"/>
></wsp:Policy>
Problem nr 2)
The message pass the proxy (the security on message level) but in the message flow due to some exception >(various reasons that are not important now) the transaction is rolled back and the message "is put back on the >queue".
Now is the funny part: BEcause of the Digest Expiration Time which is very short the message for sure will >expire until the redelivery (ususaly minutes) will be doneSimple solution would be to configure the JMS Proxy where you have the WS-Security check to be a pass through and pass the message to another jms queue which can be listened to by JMS proxy which does validation and remaining processing.

Expiration of messages in Queue + OSB (part 2)

I am working on a prototype and I have the following scenario :
I have on ALSB (OSB) a JMS based Proxy Service that uses a queue in order to get the messages.
On the queue are put SOAP messages that are secured on message level.
There is a digest expiration on Domain Level that is set to 300 ms by default.
This means that the message once is created and reach the proxy it has to be in this 300 ms time frame.
==> Queue ==>Security Check on JMS Proxy Service ==> Message Flow
Problem nr 1)
In peak time i estimate that since on the queue to have maybe more then 1000 messages and 300 ms would not be enough.
If i modify this digest expiration on Domain Level i affect the other applications that are deployed also on ALSB (OSB) and i expose them to security breach.
Is there a way of solving this ? 300 ms is too small for such thing....
Problem nr 2)
The message pass the proxy (the security on message level) but in the message flow due to some exception (various reasons that are not important now) the transaction is rolled back and the message "is put back on the queue".
Now is the funny part: BEcause of the Digest Expiration Time which is very short the message for sure will expire until the redelivery (ususaly minutes) will be done.
So why a messages that already passed security is checked again on retry ? Can't this be avoided somehow ?
Thank you.

These question look like they are very specific to OSB, rather than basic JMS -- which has no concept of message level encryption -- I suggest reposting to the OSB newsgroup instead.

Application Expiration time message change

Similar Messages

Maybe you are looking for