Redeployment of an Application

Assume that in Dev I have an application and then deploy it to Production following the APEX Deploy instructions. If the application in Dev is subsequently altered, how do we redeploy the application to production? Do we first have to delete the existing application in Production or is there a way to overlay the Production Version with the new version from Dev?

Vee's suggestion is correct.
This method also preserves an saved Interactive Report definitions your users may have saved. So we always make sure to re-use the original application ID.
In an development environment bigger that a couple people, you'll probably want to assign blocks of application IDs to each development team, so they can be assured that the application ID they created in development is available in the production environment. That is, it hasn't been assigned to another application already. Application IDs can be ridiculously big, so we assigned IDs in blocks of 1000, not that any programmer team will ever create more than 100 Apex apps (before the product goes EOL). But good to be safe, eh?
Best of luck,
Stew

Similar Messages

Partial redeploy of an application ear fails intermittently

Hi,
I am trying to redeploy my application ear using deployment API provided by weblogic. The list of files which i try to redeploy are couple of jars and couple of wars one at a time. The problem is most of the times the deployment paritally goes through informing me that weblogic has transitioned application status from activated at last. But in some cases i see "<b>javax.management.InstanceAlreadyExistsException"</b> though the application is already present. Why does this happen where in the handle to ApplicationMBean tries to register the application as though it was new which is not the case. Check the exception below.
javax.management.InstanceAlreadyExistsException: vgndomain:Location=VgnVCMServer,Name=VgnVCMServer_VgnContentSvcs,ServerRuntime=VgnVCMServer,Type=ApplicationRuntime
     at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
     at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:2371)
     at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:876)
     at weblogic.management.internal.RemoteMBeanServerImpl.private_registerMBean(RemoteMBeanServerImpl.java:582)
     at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanServerImpl.java:524)
     at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:166)
     at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:122)
     at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:85)
     at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:62)
     at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:74)
     at weblogic.j2ee.J2EEApplicationRuntimeMBeanImpl.<init>(J2EEApplicationRuntimeMBeanImpl.java:42)
     at weblogic.j2ee.J2EEApplicationContainer.initRuntimeMBean(J2EEApplicationContainer.java:781)
     at weblogic.j2ee.J2EEApplicationContainer.<init>(J2EEApplicationContainer.java:448)
     at weblogic.j2ee.J2EEApplicationContainerFactory.createApplicationContainer(J2EEApplicationContainerFactory.java:131)
     at weblogic.j2ee.J2EEApplicationContainerFactory.getOrCreateApplicationContainer(J2EEApplicationContainerFactory.java:113)
     at weblogic.management.deploy.slave.SlaveDeployer$Application.getContainer(SlaveDeployer.java:3011)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2550)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Any help on this would be appreciated.
Thanks,
Sandeep

The info for the 149080 error is included below:
Basically, you can only do a partial redeploy if you are using an exploded directory app.
Error: A partial update of an archived application is not allowed. Application app cannot be redeployed.
Description
     There was an attempt to partially redeploy an archived application. Partial redeployment of an archived application is not allowed.
Cause
     There was an attempt to partially redeploy an archived application
Action
     Try deploying entire application
Refer to the deployment documentation for more info.
http://download.oracle.com/docs/cd/E11035_01/wls100/deployment/redeploy.html#wp1031505
8.1.2.2 Partial Redeployment of J2EE Modules
Partial redeployment also enables you to redeploy a single module or subset of
modules in a deployed Enterprise Application. Again, partial deployment is
supported only for applications that are deployed using an exploded archive directory.

Dynamic redeployment of exploded application

Hi
I am trying to configure weblogic (6.0sp1) for dynamic deployment of my
application.
For convenience of source management, i got my web-apps + ejbs in different
directory other than "/config/domain_name/applications".
Now weblogic document says, application should be in
"/domain_name/application" folder, for dynamic redeployment.
Is it possible to redeploy dynamically if my EJBs class files are different
directory.
I am using exploded form of deployment.
ps. I hope it's not a issue with 6.0sp1?
Thanks
Ashish Jain

Hi,
Here We have called javascript function('setFlashHeight') from Flex, and pass the param to the javascript function like: index, height
Flex:
Index: embed swf name
height: set value of swf height
javascript:
divid: id of the div containing the flash movie.
Flex Code:
ExternalInterface.call("setFlashHeight","index",height);
JavaScript Code:
function setFlashHeight(divid, newH){
$(divid).style.height = newH+"px";

NoClassDefFoundErrors after Redeployment of an Application

Hi all,
in our current project we encounter the following problem:
We deploy our application via the wldeploy ant task and the deployment finishes successfully. But at runtime when an MDB is instantiated by the container we get a NoClassDefFoundError. What is weird about that is that a) this does not happen after every redeployment, b) it does not occur every time an MDB gets invoked, sometimes a few messages can be retrieved and then it suddenly fails, c) after the error occurs it sometimes vanishes again, that means that sometimes a redelivered message gets delivered after several attempts without that error and d) after a restart of the application server (WLS 9.2 MP1) the error does not occur until the next (or a following) redeployment.
This behavior puzzles me immensely, the class in question is located in the jaxb-api.jar that we bundle with our application. Other classes from this jar, like the JAXBContext get loaded without problems which i can see from the stacktrace, so the jar seems to be available to the classloader. None of the other libs in the classpath/application contain any jaxb classes so it does not look like a class conflict.
Any pointers on this will be greatly appreciated.
Thanks, Chris

Hi,
thanks for your answer.
I already did a search in my local WLS directory to find any jaxb related classes but could not find any. So it seems there are no jaxb classes bundled with WLS.
We do a complete undeploy first and the deploy the application fresh, so everything should be cleaned up (at least i would assume that) and there should not be any difference to a deployment at startup.
What i forgot to mention in my first post: We use Spring to create the MDBs, so maybe there is a problem with Spring vs WLS in class loading.
We are not running in a clustered environment but on a single instance.
Cheers, Chris

Redeploy parent application with Enterprise Manager

If I attempt to redeploy a parent application using Enterprise Manager I get the following error:
"Only a single application can be redeployed at a time. Only childless applications can be Redeployed"
I don't understand why I am being prevented from doing something seemingly trivial. Why do I need to go through the process of undeploying all child applications and then deploying them again?

Luis,
If all of the files uploaded piecemeal worked fine, then I believe your problem to be with your deployment descriptor(s). Also, note that the .war file lives in a different directory:
C:\oc4j\j2ee\home\applications\Application-Name
Perhaps if you have time you could post all of the associated deployment descriptor files. Log files from the C:\oc4j\j2ee\home\log\oc4j directory would also help to troubleshoot your deployment issues. You can turn up the logging level to "FINEST" for maximum output to your log file.
-Michael

Unable to redeploy Planning application

Hi,
I am trying to redeploy a planning application and I get the following error:
App Creation failed with Exception: com.hyperion.planning.HspRuntimeException: You cannot delete the required Planning dimensions after deploying. To redeploy single-currency applications, you must include these required Planning dimensions: Scenario, Version, Entity, Account, Period, and Year.
at com.hyperion.planning.appdeploy.HspAppDefinition.validateNonModifiablePropsOnRedeploy(Unknown Source)
at com.hyperion.planning.appdeploy.HspAppDefinition.deployAppFromXML(Unknown Source)
at com.hyperion.planning.appdeploy.HspAppDefinition.access$000(Unknown Source)
at com.hyperion.planning.appdeploy.HspAppDefinition$1.run(Unknown Source)
The Application contains the mentioned dimensions. I must mention here that this Application has been deployed since the last two months. I have redeployed it multiple times when additional members were added. The most recent change is an addition of one member in the Account dimension.
Thanks in advance for your help
Shehzad

Hi John,
Everything was working fine when I had the following patches applied:
7227802
7272558
7305465
I then rolled back the last two patches and applied the other 3 patches that were released before them. So the new set of applied patches (in the order specified) was:
7227802
7110941
7161248
7209507
7272558
7305465
I found that rolling back patch number 7161248 caused the deployment to go ahead without any errors. I can't really explain why this particular patch is causing problems. Do you know if this patch causes any known problems? Should I be doing something else when applying this patch?
Thanks in advance
Shehzad

HOT Redeployment of EAR fails with Classloader error

App Server: WLS 10.3
OS: Solaris 9
I have installed WLS installed with a domain, admin and a managed server. Everything is working fine.
I have WAR and EAR deployed successfully on the Managed Server.
HOT deployment of WAR files works perfectly fine.
There is this EAR "IIA.ear" with @ 8 WAR files and 1 jar "Manager.jar". The EAR has been deployed in the "nostage" mode.
I do not have any separate "Deployment" plan.
In order to "redeploy" the EAR I go to the Admin console >> Deployments >> Select the EAR >> update >> Source Path remains the same >> Finish
I get the following error :
+#####################+
weblogic.application.CannotRedeployException: Module 'Manager.jar' has the same ClassLoader as the Application 'IIA'. Consider redeploying the entire application.
Update operation failed - no deployments changed.
+#####################+
The log files shows below error
+#####################+
+<Sep 15, 2009 9:18:52 AM MEST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with+
ID '1252999132033' for task '8'. Error is: 'weblogic.application.CannotRedeployException: Module 'Manager.jar' has the
same ClassLoader as the Application 'IIA'. Consider redeploying the entire application.'
weblogic.application.CannotRedeployException: Module 'Manager.jar' has the same ClassLoader as the Application 'IIA'. Consider redeploying the entire application.
at weblogic.application.internal.AppClassLoaderManagerImpl.updatePartialDeploySet(AppClassLoaderManagerImpl.java:299)
at weblogic.application.internal.flow.TailModuleRedeployFlow.validateClassLoaderStructure(TailModuleRedeployFlow.java
+:135)+
at weblogic.application.internal.flow.TailModuleRedeployFlow.validateRedeploy(TailModuleRedeployFlow.java:97)
at weblogic.application.internal.BaseDeployment$ValidateRedeployStateChange.next(BaseDeployment.java:801)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
Truncated. see log file for complete stacktrace
+>+
+#####################+
does WLS 10 supports HOT deployment of EAR files? Is it any issue with "Class Loading"? Anything to be changed to make this HOT redeployment successful?

App Server: WLS 10.3
OS: Solaris 9
I have installed WLS installed with a domain, admin and a managed server. Everything is working fine.
I have WAR and EAR deployed successfully on the Managed Server.
HOT deployment of WAR files works perfectly fine.
There is this EAR "IIA.ear" with @ 8 WAR files and 1 jar "Manager.jar". The EAR has been deployed in the "nostage" mode.
I do not have any separate "Deployment" plan.
In order to "redeploy" the EAR I go to the Admin console >> Deployments >> Select the EAR >> update >> Source Path remains the same >> Finish
I get the following error :
+#####################+
weblogic.application.CannotRedeployException: Module 'Manager.jar' has the same ClassLoader as the Application 'IIA'. Consider redeploying the entire application.
Update operation failed - no deployments changed.
+#####################+
The log files shows below error
+#####################+
+<Sep 15, 2009 9:18:52 AM MEST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with+
ID '1252999132033' for task '8'. Error is: 'weblogic.application.CannotRedeployException: Module 'Manager.jar' has the
same ClassLoader as the Application 'IIA'. Consider redeploying the entire application.'
weblogic.application.CannotRedeployException: Module 'Manager.jar' has the same ClassLoader as the Application 'IIA'. Consider redeploying the entire application.
at weblogic.application.internal.AppClassLoaderManagerImpl.updatePartialDeploySet(AppClassLoaderManagerImpl.java:299)
at weblogic.application.internal.flow.TailModuleRedeployFlow.validateClassLoaderStructure(TailModuleRedeployFlow.java
+:135)+
at weblogic.application.internal.flow.TailModuleRedeployFlow.validateRedeploy(TailModuleRedeployFlow.java:97)
at weblogic.application.internal.BaseDeployment$ValidateRedeployStateChange.next(BaseDeployment.java:801)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
Truncated. see log file for complete stacktrace
+>+
+#####################+
does WLS 10 supports HOT deployment of EAR files? Is it any issue with "Class Loading"? Anything to be changed to make this HOT redeployment successful?

How do I develop J2EE application in envirenment of WebLogic 8.1 and JB9?

Now I have 3 questions:
1. I can not use the EJB's local interface, although I have define local interface in config file and query code in the programe perfectly. What additional work has I not done;
2. I have to compile my program into a .jar, .ear or .war file(s) to debug, that is a unhandy way, even I change only one line of one page, I have to redeploy the whole application package once more. Is there any way else to deal with the work? Not a .jar, .war or .ear file(s) in the design time, just one page or class file, and I need not deploy and compile the whole application;
3. If I use the JBuilder9's Run command boot the WebLogic Server, the application deploied anteriorly becomes unavailable. But when the WebLogic Server is boot from console, everything is O.K.. Any advice?
Thanks in advance for any help you offer!

JB has online help describing how to build web applications and J2EE components. It even has wizards to assist you in setting up your projects.
WebLogic (at least 7.x) allows you to deploy your web apps in exploded directory format so you don't need to build an ear/war file everytime you change something. Again, RTFM.

Can't deploy a SINGLE bean in weblogic 6.1 SP2 w/o application reload

Anyone know how to update a single bean in an application without
redeploying the entire application?
We have a project containing 101 beans (session and entity) and 372
jsps which we are deploying on weblogic 6.1, SP2 as a single
application. The project is deployed in an exploded directory format
as follows:
trader/
META-INF/application.xml
lib/
third-party.jar
third-party.jar (etc.)
SessionBean.jar
EntityBean.jar (etc.)
trader/
WEB-INF/web.xml
META-INF/MANIFEST.MF (contains Class-Path: entry to lib dir)
jsp/html/gif's reside below this point.
Each bean jar has a META-INF/MANIFEST.MF to resolve third-party
library dependencies through the use of the Class-Path entry.
When we we try to update a single bean's implementation, the
entire application reloads, which can take between 10 - 30 minutes.
We have tried using the weblogic.deploy tool as well as undeploying
and redeploying the bean from the console. In both cases, the
entire application reloads.
When we use weblogic.deploy, we've tried the following:
weblogic.deploy
-url T3://localhost:7001
update weblogicpwd trader ~/trader/build/SessionBean.jar
and
weblogic.deploy
-url T3://localhost:7001
-component SessionBean:srvr1
update weblogicpwd trader ~/trader/build/SessionBean.jar

Anyone know how to update a single bean in an application without
redeploying the entire application?
We have a project containing 101 beans (session and entity) and 372
jsps which we are deploying on weblogic 6.1, SP2 as a single
application. The project is deployed in an exploded directory format
as follows:
trader/
META-INF/application.xml
lib/
third-party.jar
third-party.jar (etc.)
SessionBean.jar
EntityBean.jar (etc.)
trader/
WEB-INF/web.xml
META-INF/MANIFEST.MF (contains Class-Path: entry to lib dir)
jsp/html/gif's reside below this point.
Each bean jar has a META-INF/MANIFEST.MF to resolve third-party
library dependencies through the use of the Class-Path entry.
When we we try to update a single bean's implementation, the
entire application reloads, which can take between 10 - 30 minutes.
We have tried using the weblogic.deploy tool as well as undeploying
and redeploying the bean from the console. In both cases, the
entire application reloads.
When we use weblogic.deploy, we've tried the following:
weblogic.deploy
-url T3://localhost:7001
update weblogicpwd trader ~/trader/build/SessionBean.jar
and
weblogic.deploy
-url T3://localhost:7001
-component SessionBean:srvr1
update weblogicpwd trader ~/trader/build/SessionBean.jar

Failed to deploy a simple application on weblogic 10.3.3.0

Hi All,
I'am unable to deploy a very simple War file application by ant task (weblogic ant task weblogic.ant.taskdefs.management.WLDeploy).
I find how to cause this problem,but I can't resolve it .
In my war file ,include one file with chinese file name "测试.jsp" .
the weblogic use the java.util.jar.JarFile to extract the war file.but is can't handle chinese file name corrently.
so it get a wrong file name "²âÊÔ.js" ,and cause this problem.
Thinks
Jason
exception:
deployOnServer1:
[echo] *********** Start deploying war file on SERVER1 ***********
[wldeploy] weblogic.Deployer -debug -remote -verbose -upload -noexit -name yuidemo -source y:\sources\yuidemo\dist\yuidemo.war -targets AdminServer -adminurl http://10.99.76.58:7001 -user weblogic -password ******** -redeploy
[wldeploy] weblogic.Deployer invoked with options: -debug -remote -verbose -upload -noexit -name yuidemo -source y:\sources\yuidemo\dist\yuidemo.war -targets AdminServer -adminurl http://10.99.76.58:7001 -user weblogic -redeploy
[wldeploy] [WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE version V1_4 deployments
[wldeploy] [WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at 10.99.76.58:7001, as user weblogic
[wldeploy] [ServerConnectionImpl.getEnvironment():288] : setting environment
[wldeploy] [ServerConnectionImpl.getEnvironment():291] : getting context using http://10.99.76.58:7001
[wldeploy] [ServerConnectionImpl.getMBeanServer():239] : Connecting to MBeanServer at service:jmx:http://10.99.76.58:7001/jndi/weblogic.management.mbeanservers.domainruntime
[wldeploy] [ServerConnectionImpl.getMBeanServer():239] : Connecting to MBeanServer at service:jmx:http://10.99.76.58:7001/jndi/weblogic.management.mbeanservers.runtime
[wldeploy] [DomainManager.resetDomain():36] : Getting new domain
[wldeploy] [DomainManager.resetDomain():39] : Using pending domain: false
[wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@1041876
[wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@1041876
[wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@34151f
[wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@34151f
[wldeploy] [ServerConnectionImpl.initialize():171] : Connected to WLS domain: base_domain
[wldeploy] [ServerConnectionImpl.setRemote():482] : Running in remote mode
[wldeploy] [ServerConnectionImpl.init():161] : Initializing ServerConnection : [email protected]a99
[wldeploy] [BasicOperation.dumpTmids():689] : Incoming tmids:
[wldeploy] [BasicOperation.dumpTmids():691] : {Target=AdminServer, WebLogicTargetType=server, Name=yuidemo}, targeted=true
[wldeploy] [RedeployOperation.setupPaths():86] : in place redeploy: false from moduleArchive: y:\sources\yuidemo\dist\yuidemo.war
[wldeploy] [RedeployOperation.setupPaths():95] : redeploy src path: Y:\sources\yuidemo\dist\yuidemo.war
[wldeploy] [BasicOperation.deriveAppName():140] : appname established as: yuidemo
[wldeploy] <2013-2-6 上午10时16分36秒 CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating redeploy operation for application, yuidemo [archive: y:\sources\yuidemo\dist\yuidemo.war], to AdminServer .>
[wldeploy] [ServerConnectionImpl.upload():658] : Uploaded app to D:\TOOLS\DEVELOP\bea\user_projects\domains\base_domain\.\servers\AdminServer\upload\yuidemo
[wldeploy] [BasicOperation.dumpTmids():689] : Incoming tmids:
[wldeploy] [BasicOperation.dumpTmids():691] : {Target=AdminServer, WebLogicTargetType=server, Name=yuidemo}, targeted=true
[wldeploy] [BasicOperation.loadGeneralOptions():606] : Delete Files:false
[wldeploy] Timeout :3600000
[wldeploy] Targets:
[wldeploy] AdminServer
[wldeploy] ModuleTargets={}
[wldeploy] SubModuleTargets={}
[wldeploy] }
[wldeploy] Files:
[wldeploy] null
[wldeploy] Deployment Plan: null
[wldeploy] App root: D:\TOOLS\DEVELOP\bea\user_projects\domains\base_domain\.\servers\AdminServer\upload\yuidemo
[wldeploy] App config: D:\TOOLS\DEVELOP\bea\user_projects\domains\base_domain\.\servers\AdminServer\upload\yuidemo\plan
[wldeploy] Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=null,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=yuidemo,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0deploymentPrincipalName=null}
[wldeploy]
[wldeploy] [BasicOperation.execute():423] : Initiating redeploy operation for app, yuidemo, on targets:
[wldeploy] [BasicOperation.execute():425] : AdminServer
[wldeploy] [RedeployOperation.initializeTask():55] : Starting task with path: D:\TOOLS\DEVELOP\bea\user_projects\domains\base_domain\.\servers\AdminServer\upload\yuidemo\app\yuidemo.war
[wldeploy] Task 3 initiated: [Deployer:149026]deploy application yuidemo on AdminServer.
[wldeploy] dumping Exception stack
[wldeploy] Task 3 failed: [Deployer:149026]deploy application yuidemo on AdminServer.
[wldeploy] Target state: redeploy failed on Server AdminServer
[wldeploy] java.lang.NullPointerException
[wldeploy]      at weblogic.utils.jars.JarFileUtils.extract(JarFileUtils.java:287)
[wldeploy]      at weblogic.application.io.ArchivedWar.expandWarFileIntoDirectory(ArchivedWar.java:131)
[wldeploy]      at weblogic.application.io.ArchivedWar.extractWarFile(ArchivedWar.java:100)
[wldeploy]      at weblogic.application.io.ArchivedWar.<init>(ArchivedWar.java:49)
[wldeploy]      at weblogic.servlet.internal.War.makeExplodedJar(War.java:1019)
[wldeploy]      at weblogic.servlet.internal.War.<init>(War.java:182)
[wldeploy]      at weblogic.servlet.internal.WebAppServletContext.processDocroot(WebAppServletContext.java:2658)
[wldeploy]      at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:2552)
[wldeploy]      at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:388)
[wldeploy]      at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456)
[wldeploy]      at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414)
[wldeploy]      at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910)
[wldeploy]      at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
[wldeploy]      at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
[wldeploy]      at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
[wldeploy]      at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
[wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
[wldeploy]      at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
[wldeploy]      at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
[wldeploy]      at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
[wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
[wldeploy]      at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
[wldeploy]      at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
[wldeploy]      at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
[wldeploy]      at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
[wldeploy]      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
[wldeploy]      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
[wldeploy]      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
[wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
[wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
[wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
[wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
[wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
[wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
[wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
[wldeploy]      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
[wldeploy]      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
[wldeploy]      at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
[wldeploy]
[wldeploy]
[wldeploy] weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application yuidemo on AdminServer.
[wldeploy] Target state: redeploy failed on Server AdminServer
[wldeploy] java.lang.NullPointerException
[wldeploy]      at weblogic.utils.jars.JarFileUtils.extract(JarFileUtils.java:287)
[wldeploy]      at weblogic.application.io.ArchivedWar.expandWarFileIntoDirectory(ArchivedWar.java:131)
[wldeploy]      at weblogic.application.io.ArchivedWar.extractWarFile(ArchivedWar.java:100)
[wldeploy]      at weblogic.application.io.ArchivedWar.<init>(ArchivedWar.java:49)
[wldeploy]      at weblogic.servlet.internal.War.makeExplodedJar(War.java:1019)
[wldeploy]      at weblogic.servlet.internal.War.<init>(War.java:182)
[wldeploy]      at weblogic.servlet.internal.WebAppServletContext.processDocroot(WebAppServletContext.java:2658)
[wldeploy]      at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:2552)
[wldeploy]      at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:388)
[wldeploy]      at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456)
[wldeploy]      at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414)
[wldeploy]      at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910)
[wldeploy]      at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
[wldeploy]      at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
[wldeploy]      at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
[wldeploy]      at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
[wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
[wldeploy]      at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
[wldeploy]      at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
[wldeploy]      at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
[wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
[wldeploy]      at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
[wldeploy]      at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
[wldeploy]      at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
[wldeploy]      at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
[wldeploy]      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
[wldeploy]      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
[wldeploy]      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
[wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
[wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
[wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
[wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
[wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
[wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
[wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
[wldeploy]      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
[wldeploy]      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
[wldeploy]      at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
[wldeploy]
[wldeploy]
[wldeploy]
[wldeploy]      at weblogic.deploy.api.tools.deployer.Jsr88Operation.report(Jsr88Operation.java:541)
[wldeploy]      at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:140)
[wldeploy]      at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
[wldeploy]      at weblogic.utils.compiler.Tool.run(Tool.java:158)
[wldeploy]      at weblogic.utils.compiler.Tool.run(Tool.java:115)
[wldeploy]      at weblogic.Deployer.run(Deployer.java:70)
[wldeploy]      at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
[wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[wldeploy]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[wldeploy]      at java.lang.reflect.Method.invoke(Method.java:597)
[wldeploy]      at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:419)
[wldeploy]      at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
[wldeploy]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
[wldeploy]      at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
[wldeploy]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[wldeploy]      at java.lang.reflect.Method.invoke(Method.java:597)
[wldeploy]      at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
[wldeploy]      at org.apache.tools.ant.Task.perform(Task.java:348)
[wldeploy]      at org.apache.tools.ant.Target.execute(Target.java:392)
[wldeploy]      at org.apache.tools.ant.Target.performTasks(Target.java:413)
[wldeploy]      at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
[wldeploy]      at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
[wldeploy]      at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[wldeploy]      at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
[wldeploy]      at org.apache.tools.ant.Main.runBuild(Main.java:811)
[wldeploy]      at org.apache.tools.ant.Main.startAnt(Main.java:217)
[wldeploy]      at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
[wldeploy]      at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
[wldeploy] [ServerConnectionImpl.close():334] : Closing DM connection
[wldeploy] [ServerConnectionImpl.close():354] : Unregistered all listeners
[wldeploy] [ServerConnectionImpl.closeJMX():374] : Closed JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():386] : Closed Runtime JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():398] : Closed Edit JMX connection

Hi Jason,
1. Log in to the WebLogic Administrative Console.
2. Click Preference at the top of the right pane.
3. Deselect Automatically acquire lock.
4. Click Save to save the changes.
5. On the left pane of Administrative Console, click Release Configuration.
6. Re-run the ant build
Regards,
Kal

Precompilation of JSPs for default web application

Hello,
Once in a while I need to redeploy my "Default" web application. I would like to have its all JSPs precompiled, so that it was immediatly available after redeployment.
However, if I try to redeploy my web application (.war file) under, let's say, "DefaultWebApp" root context, using the administration console, with the "Precompile JSPs" option enabled, it does compile all JSPs, but ONLY those deployed under the "DefaultWebApp" root context.
However, If I access a url like "http://somehost/SomeResource.jsp" (a file that belongs to that default web application"), I can see (due to a pause) that my JSPs have not been compiled under the root context.
Is there any way to precompile JSPs for my default web applications?
Sincerely,
Sergei Batiuk.

Hello,
Once in a while I need to redeploy my "Default" web application. I would like to have its all JSPs precompiled, so that it was immediatly available after redeployment.
However, if I try to redeploy my web application (.war file) under, let's say, "DefaultWebApp" root context, using the administration console, with the "Precompile JSPs" option enabled, it does compile all JSPs, but ONLY those deployed under the "DefaultWebApp" root context.
However, If I access a url like "http://somehost/SomeResource.jsp" (a file that belongs to that default web application"), I can see (due to a pause) that my JSPs have not been compiled under the root context.
Is there any way to precompile JSPs for my default web applications?
Sincerely,
Sergei Batiuk.

Trying unsuccessfully to redeploy an older ear on WLS9.2

Hi All,
I've spent a few days trying to get a redeploy of an ear working on WLS9.2 using the wldeploy ant task. It works where the ear file is newer that the one already deployed, but redeploy just doesn't take effect if the ear we want is older than the one that is already deployed. It doesn't give an error, the log says that it's redeployed, but the redeploy doesn't take effect. This wldeploy task worked fine with WLS8.1 no matter when the ear was built.
It seems to be the same issue as
http://forums.bea.com/bea/thread.jspa?forumID=2033&threadID=400002694&messageID=400007471#400007471
I'm out of ideas, so any help would be gratefully received!
The original deployment via the console was fine, specifying DDOnly. The ear was loaded from the location C:\EARS\app.ear on the machine "host1" We then specified that the location from which the ear would be available would be \\host1\ears\app.ear which is the same location simply specified as a network drive.
An Ant task, not the wldeploy task, copies the ear we want from any development machine to the networked host1 location. This step works fine.
Then we try to redeploy using the wldeploy task. This only seems to work if the ear file we're trying to deploy is newer than the one we already had running.
The task was as follows, with all options valid and one target server specified in targets:
          <wldeploy action="redeploy"
               source="${source}"
               name="${appname}"
               user="${user}"
               password="${pass}"
               verbose="true"
               adminurl="${adminurl}"
               debug="true"
               targets="${targets}">
          </wldeploy>
Source is specified as \\host1\ears\app.ear
Since then, we've been changing all kinds of options in wldeploy trying to get it to work for older ears, but it won't.
extract from one of many log files showing wldeploy logging for an older ear. In this case, we're trying to replace deployed version built at 10:30 with version built at 10:22. It shows successful but the version from 10:30 is still deployed on the managed server ManagedServer1 after the redeploy. The task is:
          <wldeploy action="redeploy"
               retiretimeout="1"
               source="${source}"
               name="${appname}"
               user="${user}"
               password="${pass}"
               verbose="true"
               adminurl="${adminurl}"
               debug="true"
               graceful="false"
               targets="${targets}">
          </wldeploy>
copy_ear:
[delete] Deleting 1 files from \\HOST1\EARS
[copy] Copying 1 file to \\HOST1\EARS
weblogic_redeploy:
[echo] message="ant wldeploy classpath is: /bea/weblogic92/server/lib/weblogic.jar"
[wldeploy] weblogic.Deployer -debug -verbose -noexit -name app1 -source \\host1\ears\app.ear -targets ManagedServer1 -adminurl t3://host1:5001 -user weblogic -password ******** -redeploy -retiretimeout 1
[wldeploy] weblogic.Deployer invoked with options: -debug -verbose -noexit -name app1 -source \\host1\ears\app.ear -targets ManagedServer1 -adminurl t3://host1:5001 -user weblogic -redeploy -retiretimeout 1
[wldeploy] [WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE version V1_4 deployments
[wldeploy] [WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at host1:5001, as user weblogic
[wldeploy] [ServerConnectionImpl.getEnvironment():288] : setting environment
[wldeploy] [ServerConnectionImpl.getEnvironment():291] : getting context using t3://host1:5001
[wldeploy] [ServerConnectionImpl.getMBeanServer():239] : Connecting to MBeanServer at service:jmx:t3://host1:5001/jndi/weblogic.management.mbeanservers.domainruntime
[wldeploy] [ServerConnectionImpl.getMBeanServer():239] : Connecting to MBeanServer at service:jmx:t3://host1:5001/jndi/weblogic.management.mbeanservers.runtime
[wldeploy] [DomainManager.resetDomain():36] : Getting new domain
[wldeploy] [DomainManager.resetDomain():39] : Using pending domain: false
[wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@40ece0
[wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@40ece0
[wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@1954f89
[wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@1954f89
[wldeploy] [ServerConnectionImpl.initialize():171] : Connected to WLS domain: OGPDomain
[wldeploy] [ServerConnectionImpl.init():161] : Initializing ServerConnection : [email protected]e9
[wldeploy] [BasicOperation.dumpTmids():690] : Incoming tmids:
[wldeploy] [BasicOperation.dumpTmids():692] : {Target=ManagedServer1, WebLogicTargetType=server, Name=app1}, targeted=true
[wldeploy] [RedeployOperation.setupPaths():86] : in place redeploy: false from moduleArchive: \\host1\ears\app.ear
[wldeploy] [RedeployOperation.setupPaths():95] : redeploy src path: \\host1\ears\app.ear
[wldeploy] [BasicOperation.deriveAppName():139] : appname established as: app1
[wldeploy] <08-Aug-2007 10:18:00 o'clock IST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating redeploy operation for application, app1 [archive: \\host1\ears\app.ear], to ManagedServer1 .>
[wldeploy] [BasicOperation.dumpTmids():690] : Incoming tmids:
[wldeploy] [BasicOperation.dumpTmids():692] : {Target=ManagedServer1, WebLogicTargetType=server, Name=app1}, targeted=true
[wldeploy] [BasicOperation.loadGeneralOptions():607] : Delete Files:false
[wldeploy] Timeout :3600000
[wldeploy] Targets:
[wldeploy] ManagedServer1
[wldeploy] ModuleTargets={}
[wldeploy] SubModuleTargets={}
[wldeploy] }
[wldeploy] Files:
[wldeploy] null
[wldeploy] Deployment Plan: null
[wldeploy] App root: C:\dev\RELEASE\config\deployments\conord\app1
[wldeploy] App config: C:\dev\RELEASE\config\deployments\conord\app1\plan
[wldeploy] Deployment Options: {isRetireGracefully=false,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=null,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=app1,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0}
[wldeploy] [BasicOperation.execute():424] : Initiating redeploy operation for app, app1, on targets:
[wldeploy] [BasicOperation.execute():426] : ManagedServer1
[wldeploy] [RedeployOperation.initializeTask():55] : Starting task with path: \\host1\ears\app.ear
[wldeploy] Task 69 initiated: [Deployer:149026]deploy application app1 on ManagedServer1.
[wldeploy] Task 69 completed: [Deployer:149026]deploy application app1 on ManagedServer1.
[wldeploy] Target state: redeploy completed on Server ManagedServer1
[wldeploy]
[wldeploy] [ServerConnectionImpl.close():334] : Closing DM connection
[wldeploy] [ServerConnectionImpl.close():354] : Unregistered all listeners
[wldeploy] [ServerConnectionImpl.closeJMX():374] : Closed JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():386] : Closed Runtime JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():398] : Closed Edit JMX connection
install_app:
install_app:
BUILD SUCCESSFUL
Total time: 21 seconds
Thanks for your time,
ConorD

Daniel Greeney wrote:
So I just purchased an internal drive (separate from my system drive) to use as a Time Machine drive, for both of my computers (only one partition). Since they will be backing up every day, I will retain much more recent material in case of drive failure.
Let Time Machine back up every hour, as it's designed. That will protect you best.
My question is this - if I have a drive failure on my current internal system drive, and the internal Time Machine is intact, is it possible for me to take my external bootable backup (say 3 weeks older than Time Machine in how recently it was backed up), make a cone of that on a new internal system drive, and then use Time Machine to restore that drive to what is most current on Time Machine?
Does this question make sense?
The question makes sense until you realize that Time Machine backups contain everything you need (unless you do something silly, like exclude your system files).
Once the new drive is installed and formatted, you can restore your entire system from the TM backups faster than you can copy the clone to the new internal HD. See #14 in the Frequently Asked Questions *User Tip,* also at the top of this forum. Note that you use the Snow Leopard Install disc only for the Installer on it; you don't install OSX from it.

Redeploy in cluster in production environment

There is a cluster consisting two node in a production environment. The purpose is to make it possible, to upgrade a deployed application to a new version, with the highest avaibility. Is it possible to do it faster than the standard Redeploy method? Couse it lasts an hour at least, and during that time the application cannot be accessed.
          Ideal would be that it could be done without service breakdown. /On one node the application keeps running, on the other at first it is redeployed, than the while the second is restarting the former stops and then that is redeployed too./
          Is it Possible? Or any other way to solve that?

Hello Mathers,
          Why does it take an hour to redoply your app, are you precompiling JSPs on startup or do you have a vast number of EJBs, lots of connection pools with connections that are all created on deployment etc?
          Can you explain your deployment process and are you using WLS staging?
          A redeployment of the application I am currently working on (three ear files approx 100 EJBs and 3 web apps) takes about 15 minutes on each managed server, so we have about 15 minutes of down time. But I think I can get this down to 5 minutes without too much trouble.
          cheers
          Hussein Badakhchani
          www.orbism.com

EPMA batch client with Essbase application - does not update aliases

Hello,
We are using EPMA 11.1.2.1 for managing outlines for Essbase applications.
Changing aliases in EPMA and launching manually redeploy from Workspace, with flag "Full Deploy" change correctly the aliases in Essbase..
Using the EPMA batch client to redeploy the Essbase application deletes all aliases in Essbase outline.
Someone knows how to solve this problem or what am I doing wrong in the EPMA script?
thanks...
this is the EPMA script:
SET bpmaserverurl=http://epma_server/hyperion-bpma-server;
SET workspaceurl=http://work_space_server/workspace;
login admin,password;
Execute reDeploy
Parameters(ApplicationName, InstanceName, waitforcompletion, deployOption)
Values('PNL', 'ESSBASE_STUDIO_SERVER:essbase_server_name', 'True', 'AppView');
Quit;
Edited by: AlexPavel on May 20, 2011 1:21 PM

Hi,
Thank you for posting in Windows Server Forum.
From your description it seems that you are facing issue only with windows 8\8.1. So firstly suggest you to check with application support team, whether they have whole support for application with newer version. Also check once with application support team
regarding this issue.
This issue occurs because the local taskbar does not receive the EVENT_OBJECT_NAMECHANGE event from the system due to a timing issue. The EVENT_OBJECT_NAMECHANGE is needed to update the taskbar title information.
More information (For reference).
The taskbar may not show the application name correctly when using a Terminal Server RemoteApp
Hope it helps!
Thanks.
Dharmesh Solanki

Can you reload web application from the Weblogic console?

          Good day, eh!
          Can you reload all your jsp/servlet classes of your
          web application from the Weblogic console?
          A one big button labeled 'Reload application' would be very
          good property in Weblogic
          Thanks for Your answers
          - hoser


Hi,
          I agree it is a much needed feature. Suppose I just change an init
          param of one application in the web.xml, I don't want to take down the
          15 other webapps running on my server just to be able to have that web
          app restart and re-read is configuration. Of course, I could program
          some servlet that allows changing application attributes and to enable
          restarting, but really this a)does not cover all the cases (i.e. addind
          an EBJ reference binding to web.xml) b) should be provided by the app
          server, not programmed by every little programmer again & again.
          Mathieu
          Jeff Nowakowski wrote:
          >
          > The URL you give refers to redeploying EJBs, not web applications. Being
          > able to redeploy a web application would be a very convenient feature.
          >
          > -Jeff
          >
          > Gene Chuang <[email protected]> wrote in message news:[email protected]...
          > > Button is already there!
          > >
          > > http://www.weblogic.com/docs51/techdeploy/hotdeploy.html#consoledeployejb
          > >
          > > Gene
          > >
          > > "hoser" <[email protected]> wrote in message
          > > news:[email protected]...
          > > >
          > > > Good day, eh!
          > > >
          > > > Can you reload all your jsp/servlet classes of your
          > > > web application from the Weblogic console?
          > > >
          > > > A one big button labeled 'Reload application' would be very
          > > > good property in Weblogic
          > > >
          > > > Thanks for Your answers
          > > >
          > > > - hoser
          > >
          > >

Redeployment of an Application

Similar Messages

Maybe you are looking for