on 09-09-2014 6:54 PM
Hi Hareesh,
Hope you are doing good.
You can this in configtool.
Open Offline Configuration Editor:
/usr/sap/<SID>/<Instance>/j2ee/configtool/offlinecfgeditor[.bat .sh]
(this assumes a running database)Open the node Configurations -> deploy -> <hierarchicalApplicationName>.
Also for particular services:
. open the configtool
. open the services tree and click on the service
What is the reason you want to make this change?
Thank you!
_____________
Kind Regards,
Hemanth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Hemanth. we'll give a try..
>>> What is the reason you want to make this change?
Couple of reasons.
So we just want to analyze the behavior by changing it a core service.
Hi Hareesh,
Hope you are doing good.
Thats great.
The application startup mode is set to decrease the initial load on the J2EE Engine and to minimize its startup time at each restart. The default value is "lazy" and you should use the most appropriate startup modes for your applications. This is because all WD applications are designed started lazily and they should be all stopped and get only started when they are triggered for the first time (i.e. by first invoke of the given WD application). The decision was taken that way because SAP wanted to prevent start-up time problems when Web Dynpro applications were started right with the server. This is why they always start upon first request.
So you can change the "StartUp" for the application you deem fit. 1 equals to manual, 2 equals to lazy and 3 equals to always (using configtool as mentioned earlier).
Specifying the Application Startup Mode
http://help.sap.com/saphelp_nw73/helpdata/en/25/0c08f3981343609d4045f8acaa0a76/frameset.htm
Thank you!
_____________
Kind Regards,
Hemanth
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.