- This topic has 1 reply, 2 voices, and was last updated 15 years ago by
.
-
Posts
-
When deploying an application EAR to WebSphere, it looks like the scripts set an argument
-noprocessEmbeddedConfig
which may not be allowing the deployment of an Enhanced EAR (an EAR with configuration information contained within – under the {EAR Name}/META-INF/ibmconfg folder.
Is there a way to change or override this?
We have an application that needs to have the WAR classloader policy set to ‘Single’, and when deploying via MyEclipseBlue the result of the deploy sets the option back to the default (‘Multiple’). We have other applications deployed to the same app server that do NOT need this option set, so setting it at the application server level would not be an option.
I’m looking for an effective way to be able to deploy without having to go into the app server to re-establish the settings manually.
Thanks for any help you can provide.
Tom
