Practical to modify app parameters for deployed app (using Builder, perhaps)?

Question

I see that it's very convenient to deploy a WAR file to WebLogic using WebLogic
Builder. It's also easy to edit the init parameters of a WAR file and redeploy
it.
I'm wondering, however, how practical it will be to dynamically edit application
parameters and redeploy in a production environment.
For instance, if I'm in my development environment, I will definitely have a WAR
(exploded or not) in my build environment that I can edit and deploy.
In production, however, we don't necessarily have the original WAR that was referenced
in the deployment, we have what was installed into WebLogic. Is it practical to
run WebLogic Builder on an already installed WAR file, edit it, and then redeploy
it? Would we instead have to store the WAR file to be deployed into a "staging"
environment before it is actually deployed? Any changes made to the WAR by the
administrator would be made to the staged WAR file and then redeployed. I guess
the "staging" filesystem would have to be reachable by the host where the administrator
runs WebLogic Builder.

Answer 1

"David M. Karr" <[email protected]> wrote in message
news:[email protected]...
>
"Sanjeev Chopra" <[email protected]> wrote:
"David M. Karr" <[email protected]> wrote in message
news:[email protected]...
I see that it's very convenient to deploy a WAR file to WebLogic usingWebLogic
Builder. It's also easy to edit the init parameters of a WAR file andredeploy
it.do you mean servlet init-param ?Both that and context init parameters.
I'm wondering, however, how practical it will be to dynamically editapplication
parameters and redeploy in a production environment.
For instance, if I'm in my development environment, I will definitelyhave
a WAR
(exploded or not) in my build environment that I can edit and deploy.
In production, however, we don't necessarily have the original WARthat
was referenced
in the deployment, we have what was installed into WebLogic. Is itpractical to
run WebLogic Builder on an already installed WAR file, edit it, andthen
redeploy
it?
Would we instead have to store the WAR file to be deployed into a
"staging"
environment before it is actually deployed?If the .war is deployed with staging mode as "stage", you should have
no
problem modifying the master copy and then doing a redeploy. The redeploy
operation will take care of copying the modified .war to the staging
areas
of all targets.Ok, but what I'm wondering is if this "master copy" that you refer to isin a
location that we set up outside of WebLogic, or whether that is where thedeployed
WAR gets stored. I'm trying to determine whether WARs that get deployedwill first
have to be stored outside of WebLogic in a directory that we control,which will
be on a filesystem that will be accessible by the administrator runningWebLogic
Builder (using Samba, perhaps).The 'master copy' is the path specified to the deployment tool (deployer,
admin console) when you deployed the app to WLS. So yes, if thats not
available to the user running builder, they have to keep a copy, modify it
and make it available to the admin.