Working with my WebLogic guy....apparently in the deploy there is an option of 'staging' which makes a copy of the deploy dir and that's where Mid-Tier runs from. There is an option of 'no staging' which tells it to run from the place you put it....that stopped it overwriting our config changes for us.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Grooms, Frederick W Sent: Friday, June 04, 2010 1:49 PM To: arslist@ARSLIST.ORG Subject: Re: WAR deployment If I remember the last time I deployed using the .war method I did the following. Dropped in the .war file and let the web server process it. Stopped the web server. Deleted the .war file This eliminated the redeploy issue. Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of John Baker Sent: Friday, June 04, 2010 1:49 PM To: arslist@ARSLIST.ORG Subject: WAR deployment I remember the issue now - Midtier writes the configuration locally, to the WEB-INF directory, and WL redeploys the WL at every given opportunity, so any configuration is lost as soon as WL restarts. What BMC really need to do is allow the config file to be located on the classpath - it's a two minute change to the MT source code. -- John Baker, Java System Solutions. http://www.javasystemsolutions.com/jss/ssoplugin ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
