Exploded (hot) deployment on a Weblogic cluster

AFAIK, exploded hot deployment on a Weblogic cluster is not supported through OEPE.
When deploying an application on a cluster, each change, no matter how small, forces you to republish these changes, ultimately causing the application to be redeployed by OEPE. Turnaround time for this (depending on the app) can take some time.
Is there a workaround available for this ?
I'm looking for a way to minimize the turnaround time between developing code, and actual seeing the code changes on the screen. The requirement however is that deployments should be possible on a managed instance / cluster (non AdminServer).
Does Oracle Weblogic support such "hot deployment" capabilities from an IDE like Eclipse ? Does anybody here have such a process in place ? (perhaps using ant / maven2 tooling)

Hi
I want to clarify that the application has to be deployed to a cluster of two managed servers, amandad_Server_1 (On Windows server hosting console) and amandad_Server_2 which is running in other Windows server.
I deployed the application following your recdommendations and the resulta is as follows:
Windows server (running the console)
1 EAR file was copied to ... \user_projects\domains\amanda_domain\servers\amandad_Server_1\stage
2. The application files extractected from the EAR files were copied to   \user_projects\domains\amanda_domain\servers\amandad_Server_1\tmp
Windows Server not runn ing the console
No files were copied to neither
... \user_projects\domains\amanda_domain\servers\amandad_Server_2\stage
     \user_projects\domains\amanda_domain\servers\amandad_Server_2\tmp
Questions
1 Windows server not running the console the files were not copied....What might cause this behaviour....? how to fixi it...?
2. Do I have to manaully copy the files to folders
...\user_projects\domains\amanda_domain\servers\amandad_Server_2\stage
   ... \user_projects\domains\amanda_domain\servers\amandad_Server_2\tmp

Similar Messages

Hot deployment problems with weblogic 7.0 sp2

Hi Guys
I am trying out hot deplyment of a j2ee application on WebLogic Server 7.0 SP2
Approach 1
The application is deployed in exploded ear format from the folder
d:/work/testbed/ear. The appropriate entry in config.xml looks like this.
<Application Deployed="true" Name="Testbed"
Path="D:\tools\bea702\projects\testbed\applications\testbed"
StagedTargets="" TwoPhase="false">
<EJBComponent Name="SessionBeans" Targets="myserver" URI="SessionBeans.jar"/>
</Application>
Creating or touching the REDEPLOY file in META-INF folder doesnt cause hot
deployment to occur
Approach 2
Copied the ear file to the applications folder. Creating or touching the
REDEPLOY file in META-INF file caused the application to be redeployed.
However the weblogic console is constantly spitting out this message.
Undeploying EJB Component SessionBeans
<Sep 29, 2003 9:53:46 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
<Sep 29, 2003 9:53:46 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
Undeploying EJB Component SessionBeans
<Sep 29, 2003 9:53:51 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
<Sep 29, 2003 9:53:52 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
Undeploying EJB Component SessionBeans
<Sep 29, 2003 9:53:57 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
<Sep 29, 2003 9:53:57 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
It seems that the application is getting undeployed and reactivated every 5
seconds.
Questions
1) Any reasons why approach 1 didnt work
2) What could be causing this constant undeployment and reactivation
Thanks for your time
anand

I think I figured out what is causing the application to be redployed every 5
seconds. It seems that if the application is deployed in the weblogic domains
applications folder you should NOT create a <Application element. Weblogic
automatically recognizes all applications in this folder and deploys them.
Removing the application entry (as shown in Approach 1) from the config.xml
and hot deploying by touching the REDEPLOY file did the trick.
One question still remains. Is hot deployment only possible when I copy the
exploded ear to the domain "applications" folder
Thanks for your time
anand
ps : The idea of trying it without the <Application element came from trying
out hot deployment in Weblogic 8. WLS8 first deploys the application in the
applications folder, followed by the application configured in the
<Application element. Since both the applications were essentially the same it
gave me a JNDIException saying that some entity is already bound with the same
name. Weblogic 7 however doesnt complain at this point.
- anand
In article <[email protected]>, Anand Raman wrote:
Hi Guys
I am trying out hot deplyment of a j2ee application on WebLogic Server 7.0 SP2
Approach 1
The application is deployed in exploded ear format from the folder
d:/work/testbed/ear. The appropriate entry in config.xml looks like this.
<Application Deployed="true" Name="Testbed"
Path="D:\tools\bea702\projects\testbed\applications\testbed"
StagedTargets="" TwoPhase="false">
<EJBComponent Name="SessionBeans" Targets="myserver" URI="SessionBeans.jar"/>
</Application>
Creating or touching the REDEPLOY file in META-INF folder doesnt cause hot
deployment to occur
Approach 2
Copied the ear file to the applications folder. Creating or touching the
REDEPLOY file in META-INF file caused the application to be redeployed.
However the weblogic console is constantly spitting out this message.
Undeploying EJB Component SessionBeans
<Sep 29, 2003 9:53:46 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
<Sep 29, 2003 9:53:46 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
Undeploying EJB Component SessionBeans
<Sep 29, 2003 9:53:51 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
<Sep 29, 2003 9:53:52 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
Undeploying EJB Component SessionBeans
<Sep 29, 2003 9:53:57 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
<Sep 29, 2003 9:53:57 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
It seems that the application is getting undeployed and reactivated every 5
seconds.
Questions
1) Any reasons why approach 1 didnt work
2) What could be causing this constant undeployment and reactivation
Thanks for your time
anand

How to hot deploy EJB in Weblogic?

Hi all,
We use Weblogic 10.3 and EJB3.
EJB has been build as ear and deployed in the server. And other deployed modules in server calls that.
But the modification of EJB need to be rebuilt and restart the server.
Does Weblogic support hot deploy for EJB? Do we need plugin or something else for this feature?
Thanks a lot.

Hi,
The production redeployment strategy/hot deployment is supported for:
a. Standalone Web Application (WAR) modules and Enterprise applications (EARs) whose clients access the application via a Web application (HTTP).
b. Enterprise applications that are accessed by inbound JMS messages from a global JMS destination, or from inbound JCA requests.
c. All types of Web Services, including conversational and reliable Web Services, but not 8.x Web Services.
Production redeployment is not supported for:
a. Standalone EJB or RAR modules. If you attempt to use production redeployment with such modules, WebLogic Server rejects the redeployment request. To redeploy such modules, remove their version identifiers and explicitly redeploy the modules.
b. Applications that use JTS drivers. For more information on JDBC application module limitations, see JDBC Application Module Limitations in Configuring and Managing JDBC for Oracle WebLogic Server.
c. Applications that obtain JDBC data sources via the DriverManager API; in order to use production redeployment, an application must instead use JNDI to look up data sources.
d. Applications that include EJB 1.1 container-managed persistence (CMP) EJBs. To use production redeployment with applications that include CMP EJBs, use EJB 2.x CMP instead of EJB 1.1 CMP.
Please check the below Doc
http://docs.oracle.com/cd/E14571_01/web.1111/e13702/redeploy.htm#
Hope this answers your question!!
Thanks,
Vijaya

HowTo:Publish Msg to JMS queue deployed in a Weblogic Cluster from a client

Hello All-
I am new to Weblogic and need help from this forum. Forgive me for my ignorance. I am learning.
Below is a brief about the context and the issues that we are facing:
Background
=======
1. We have Oracle Service Bus (OSB) installed on top of Oracle Weblogic Server (ver 10.3). In OSB we have developed a proxy service that listens to a JMS queue for an incoming message
2. The Weblogic environment is a cluster having 2 managed servers listening to different ports and it is front-ended by a Apache Load Balancer.
3. Our requirement is to post an XML message from a Java client to the JMS queue which will then initiate the proxy service deployed. We are using t3 protocol to post the message from the client to the JMS queue
Issue
====
1. To post an XML message from the client, how do we give the address of the JMS queue in the clustered environment to enable failover/loadbalancing if one managed server goes down. I understand from your earlier posts in this forum that directly hitting the JMS queue on a particular managed server will not enable failover/loadbalancing in case one of them goes down
2. Do we need to modify any config file in the Apache Proxy Plugin?
3. Do we need to provide the address of the Apache proxy in the client to send the message?
Kindly clarify and let me know me know if you need any additional information.
Greatly appreciate your help!!!
Regards,
Dibya

Hi Dibya,
Please refer to : http://weblogic-wonders.com/weblogic/2010/05/13/apache-proxy-as-static-content-repository/#comment-1379
Thanks
Jay SenSharma

Issue Undeploying and Deployment Application in Weblogic Cluster

We have a production environment wich has one cluster with 40 servers in it. The problems lies when we select one application to undeploy. Weblogic response in administration console says that the undeploy is finished, but when I try to deploy another version of the application it only affect one of the 40 servers of the cluster, the other 39 servers are still with the old version of the application in memory.
If I restart all the servers it works and all the 40 server get the new version of the application.
Now we want to do continuous deployment and scripting all the deploy process and we don't want to restart all the 40 servers every deploy.
Is there any limit of servers in a cluster? I'm saying this because it didin't occur in the stage environment with one cluster with 5 managed servers.
Do I need any specific node manager configuration to undeploy this 40 managed servers?
I look in the internet and didin't find any issues related to this.

Sharmela,
Looks like the undeploy command did not clean up the stage directories of the managed server properly.
There is no limit on the number of managed servers in a cluster or in a domain. But again you need to plan the number based on the hardware and memory settings.
We have two hexalogics, the problem here is not hardware.
Do I need any specific node manager configuration to undeploy this 40 managed servers?
What exactly you mean by undeploying managed server ? You want to remove them or bring them down ?
Sorry about that, I want to know what should I do to undeploy the application properly in the 40 managed servers(not bringing them down). I've heard something about staging mode but i've already tried to put ---nostage paramenter and the result was the same.
Do you have any clue why weblogic is not cleaning the stage directories? Is there any way to force it without restarting all the servers?
Thank you very much,
Gustavo

HOT deployment problem with WebLogic 5.1sp11

Hello!
We trying to deploy our EJB (jar contains 5 EJB's) with WebLogic EJB DeployerTool.
When we registered our jar in the weblogic.properties file - everything is OK.
This ejb cotains correct EJB's which are made in EJB 1.1 standard.
In the WebLogic EJB DeployerTool I attach proper WeaWeblogic application server
(it works on another computer, but tool found our server confidently. Then I opened
my jar file. Tool parsed file and found all beans.
After all I'm trying to run Tools/Deploy and I have the error message showed below.
If somebody knows how to manage with this problem, help!
weblogic.ejb.common.DeploymentException: Problem creating deployment ftp://172.16.2.108:21C:/tmp2/StaffShell.jar
from ftp://172.16.2.108:21C:/tmp2/StaffShell.jar; nested exception is:
     java.lang.NullPointerException:
Start server side stack trace:
java.lang.NullPointerException
     at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
     at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.java:108)
     at java.net.URL.openStream(URL.java:798)
     at weblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.java:322)
     at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
     at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
     at weblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
     at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
     at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
     at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
     at weblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
     at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
     at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
End server side stack trace
java.lang.NullPointerException:
Start server side stack trace:
java.lang.NullPointerException
     at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
     at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.java:108)
     at java.net.URL.openStream(URL.java:798)
     at weblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.java:322)
     at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
     at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
     at weblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
     at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
     at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
     at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
     at weblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
     at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
     at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
End server side stack trace
Deployment failed.

Is SP11 jars in the client classpath or not, before launching DeployerTool.
If yes, then it looks like a bug. You might want to report this problem to
[email protected]
Kumar
"Anton Nazarov" <[email protected]> wrote in message
news:[email protected]...
>
Hello!
We trying to deploy our EJB (jar contains 5 EJB's) with WebLogic EJBDeployerTool.
When we registered our jar in the weblogic.properties file - everything isOK.
This ejb cotains correct EJB's which are made in EJB 1.1 standard.
In the WebLogic EJB DeployerTool I attach proper WeaWeblogic applicationserver
(it works on another computer, but tool found our server confidently. ThenI opened
my jar file. Tool parsed file and found all beans.
After all I'm trying to run Tools/Deploy and I have the error messageshowed below.
>
If somebody knows how to manage with this problem, help!
weblogic.ejb.common.DeploymentException: Problem creating deploymentftp://172.16.2.108:21C:/tmp2/StaffShell.jar
from ftp://172.16.2.108:21C:/tmp2/StaffShell.jar; nested exception is:
java.lang.NullPointerException:
Start server side stack trace:
java.lang.NullPointerException
at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
atsun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.ja
va:108)
>
at java.net.URL.openStream(URL.java:798)
atweblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.ja
va:322)
>
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
atweblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
>
atweblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
>
at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
atweblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
>
atweblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
pter.java:347)
>
atweblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
r.java:96)
>
atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
5)
>
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
End server side stack trace
java.lang.NullPointerException:
Start server side stack trace:
java.lang.NullPointerException
at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
atsun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.ja
va:108)
>
at java.net.URL.openStream(URL.java:798)
atweblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.ja
va:322)
>
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
atweblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
>
atweblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
>
at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
atweblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
>
atweblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
pter.java:347)
>
atweblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
r.java:96)
>
atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
5)
>
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
End server side stack trace
Deployment failed.

Hot Deploy Memory leak

It appears that when using the hot deploy functionality on Weblogic
6.2 to redeploy an EJB application .ear that all previously loaded
classes are untouched - creating a huge memory leak. The weblogic
generated stub classes are never touched, even though new copies are
loaded into memory. After numerous hot deploys, I eventually get an
out of memory error. Is there some way to force the unloading of
these classes? Is this fixed on WL 7 maybe ?

I will contact bea support as well, but any ideas if this fix is
resolved in base WL 7.0, or is there a SP for 7.0 that includes this
fix too?
Thanks,
Terry
==========
Rajesh Mirchandani <[email protected]> wrote in message news:<[email protected]>...
This is fixed over SP3 and is in SP4. Pls contact [email protected]
Jared Rodriguez wrote:
It appears that when using the hot deploy functionality on Weblogic
6.2 to redeploy an EJB application .ear that all previously loaded
classes are untouched - creating a huge memory leak. The weblogic
generated stub classes are never touched, even though new copies are
loaded into memory. After numerous hot deploys, I eventually get an
out of memory error. Is there some way to force the unloading of
these classes? Is this fixed on WL 7 maybe ?

Hot deploy in weblogic 10.0 not working

Hi,
I am trying to do hot deploy in an exploded war deployment. If I deploy the same exploded war in weblogic 9.2, I can update the class files without restarting the sever. However, in weblogic 10.0 system throws “java.lang.ClassCastException: com.xxx.xxx.xxxxx” when it tries to reload the app after the old class file has been updated with a new one. If the server is restarted then the new class file is picked without any errors. Are there different settings in weblogic 10.0 to enable hot deploy? Please let me know.
Thanks a lot.

Please don't cross-post.
Cameron Purdy
Tangosol Inc.
Tangosol Coherence: Clustered Coherent Cache for J2EE
Information at http://www.tangosol.com/
"vinayvangala" <[email protected]> wrote in message
news:[email protected]..
Hi,
Did anybody get hot deploy in an expanded directory format to work
in weblogic 6.0 sp2. I have tried to follow the documentation but
couldn't get it to work.
Thanks
Vinay

WLS6sp2 Hot deployment in cluster does not work

          I have two WLS6sp2 servers in cluster in two different machines. There is an EJB
          deployed in the cluster that works fine. Now I go to the console and I undeploy
          it: the servers show a message of "ejb undeployed". Now I activate the "deploy"
          checkbox again: the following error appears:
          weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB; nested exception
          is:
          javax.naming.NameAlreadyBoundException: Can't rebind anything but a replica-aware
          stub to a name that is currently bound to a replica-aware stub; remaining name
          javax.naming.NameAlreadyBoundException: Can't rebind anything but a replica-aware
          stub to a name that is currently bound to a replica-aware stub; remaining name
          The object is obviously clusterable (it is a stateless EJB with "home-is-clusterable=true").
          It has been deployed to the cluster target. When is working it is load balanced
          between both servers. It deploys perfectly when starting up both servers, but
          hot deployment does not work.
          This works fine when only one server is up.
          ¿Is not possible to do hot deployment in cluster?


Hm, where are you seeing the javax.naming.NameAlreadyBoundException? In one of your managed
          servers, in all of your managed server, or in your admin server?
          If you see this in your admin server, then this means you got your admin joined in the cluster,
          which is not good. Remove it from the cluster if this is so.
          Gene
          "David Agudo" <[email protected]> wrote in message news:[email protected]...
          >
          > Yes, target="mycluster".
          >
          > "Gene Chuang" <[email protected]> wrote:
          > >Did you target the ejb to the cluster, or to each individual Node in
          > >your cluster? There is a
          > >difference...
          > >
          > >Gene
          > >
          > >"David Agudo" <[email protected]> wrote in message news:[email protected]...
          > >>
          > >> I have two WLS6sp2 servers in cluster in two different machines. There
          > >is an EJB
          > >> deployed in the cluster that works fine. Now I go to the console and
          > >I undeploy
          > >> it: the servers show a message of "ejb undeployed". Now I activate
          > >the "deploy"
          > >> checkbox again: the following error appears:
          > >>
          > >> weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB;
          > >nested exception
          > >> is:
          > >> javax.naming.NameAlreadyBoundException: Can't rebind anything but a
          > >replica-aware
          > >> stub to a name that is currently bound to a replica-aware stub; remaining
          > >name
          > >> ''
          > >> javax.naming.NameAlreadyBoundException: Can't rebind anything but a
          > >replica-aware
          > >> stub to a name that is currently bound to a replica-aware stub; remaining
          > >name
          > >> ''
          > >>
          > >> The object is obviously clusterable (it is a stateless EJB with "home-is-clusterable=true").
          > >> It has been deployed to the cluster target. When is working it is load
          > >balanced
          > >> between both servers. It deploys perfectly when starting up both servers,
          > >but
          > >> hot deployment does not work.
          > >>
          > >> This works fine when only one server is up.
          > >>
          > >> ¿Is not possible to do hot deployment in cluster?
          > >>
          > >
          > >
          >

Weblogic hot deployment

Hi all,
Does any body know how to redeploy a web application in weblogic without restarting the server?
I have my application in the exploded file format...
Thanks in anticipation,
Seshu

HI,
Thank u for the prompt reply. I am using weblogic 8.1 and i want to know whether there is any Hot Deployment feature in 8.1.
I've gone thru the weblogic 7.0 documentation. It says that the server automatically reloads all the files every x secs. which we can specify in the console.
but doing so doesn;t reflect my changes......
is there any other way? (i've tried touching the REDEPLOY file too)..
Thanks,
Seshu

Hot deployment of Plugin on OIM cluster

Does someone know , how to deploy(re-register) the plugin(event Handler ,schedule Task etc.) on OIM cluster in real time.
I have observed that when i do re-register the plugin(after any code changes etc.) from one of the nodes of the cluster, the new code does not get reflected on all the nodes.
It works from one or two nodes but not from all nodes.
Even after doing Purge Cache from all nodes the behavior remains the same.(Restart of OIM will do the trick, but i need hot deployment)
Any ideas?
Thanks
Akshat

That's what I have observed that even though the documentation says that PurgeCache.sh will do the trick but it never works. You have to restart the OIM Servers.

Error when deploy to weblogic cluster

My cluster has 2 servers A, B. when I deploy an WebCenter Custom Portal application to weblogic cluster, application on server A work well and application on server B is failed. Log on failed server is “what do i do: seems an odd quirk of the EJB spec. The exception is:java.lang.NoClassDefFoundError: Oracle/jdeveloper/db/adapter/DatabaseProvider”
When I reconfig cluster and then deploy, application on server B work well but application on server A is failed.
Please advise what should I do in this situation?

Hi,
It seems your Application is running with non-seralizable objects where non-searlizable are not supported on cluster environment.
Please check server logs whether you have such warning messages are not.
Let me know if you need any further help on this issue.
Regards,
Kal

ADF Application error when deploy on WebLogic Cluster

Hello,
I setup a WebLogic 10.3.5 Cluster, but I have problems to deploy my ADF application (ADF 11.1.2).
I am getting the following java.lang.NoClassDefFoundError: oracle/adf/share/logging/ADFLogger
The problem does not occur if I deploy the same application only to the AdminServer.
In order to setup my WebLogic Cluster I followed the process described by Mark Nelson at http://redstack.wordpress.com/2010/12/20/using-weblogic-as-a-load-balancer/
Any idea?
Thanks,
Cristo A.

Have you installed the Oracle JRF template to the managed servers?
The error indicates that you didn't install the adf runtime (JRF template) for your jdev version onto the managed servers.
Timo

How to deploy WebLogic Cluster on a Blade?

Hi, I am looking for recommendations on how ( if it makes sense ) to deploy WebLogic
Cluster on the (Intel) Blade HW. The question is, actually, caused by the fact
that the Blade is totally redundant and load-balanced HW where the requests are
managed by a Big-IP module ( and redirected to the IPs on the internal Blade Cassettes
One of possible solutions, we discuss now, is "either-or", i.e. let's discard
the App.Server cluster and use the HW cluster. This might work for the request
load balance but we loose all other, out-of-the-box, cluster features like session,
EJB, JNDI and so on failover and balance features.
Any notes with this regard will be greatly appreciated.
Thanks, - Michael
P.S. I repeated the same question om "cluster" Newsgroup but have not seen any
responds so far.

It sounds like you're getting request routing and fail-over in front of
WLS with the Big-IP. Typically people would enable WLS clustering to
get replicated HTTP sessions in an environment like this.
-- Rob
Michael Poulin wrote:
Hi, I am looking for recommendations on how ( if it makes sense ) to deploy WebLogic
Cluster on the (Intel) Blade HW. The question is, actually, caused by the fact
that the Blade is totally redundant and load-balanced HW where the requests are
managed by a Big-IP module ( and redirected to the IPs on the internal Blade Cassettes
One of possible solutions, we discuss now, is "either-or", i.e. let's discard
the App.Server cluster and use the HW cluster. This might work for the request
load balance but we loose all other, out-of-the-box, cluster features like session,
EJB, JNDI and so on failover and balance features.
Any notes with this regard will be greatly appreciated.
Thanks, - Michael
P.S. I repeated the same question om "cluster" Newsgroup but have not seen any
responds so far.

Hot deployment in weblogic

Hi
I have some questions related to hot deployment.
1. Is Hot Deployment similar to auto-deploy option in development mode?
2. Using Auto-deploy is it possible to get the application deployed on managed server
( I found that it gets deployed on Admin server and it is not recommended to deploy on Managed.. but is there any way to deploy on managed server)
3. my application (ear) has dependencies... those are deployed as library.. is it possible to deploy library using auto-deploy
Thanks

1. no - hot deployment, deploy, redeploy, or undeploy an application while the server is running without affecting other applications or requiring a server restart
2. no - the admin server has a feature known as auto-deployment that is enabled when you create a domain using development mode. With this feature, the server watches the autodeploy directory for changes and automatically deploys new or changed applications that it finds there.
3. why would you want that - just deploy the libraries and refer to those libraries in your deployment overrides.
Better way to auto-deploy is using the wldeploy Ant task. (http://download.oracle.com/docs/cd/E11035_01/wls100/programming/wldeploy.html)

Exploded (hot) deployment on a Weblogic cluster

Similar Messages

Maybe you are looking for