Hot deploy Pre Requisites – Easiest way to hotdeploy your code – Hot switch your java classes

-
Pre Requisites

This can be possible if  the version of JVM is V1.4 or higher.In Eclipse Set up your remote debugging options.

please visit the link to see how can you setup this,
Set up Remote Debug

Also From the Eclipse Project menu,check 'Build Automatically' Option.Set  break points to the class you need to modify(will make sense if you keep the debug point before the line you want to modify),after that Launch the debugger.

Hot Deploy Java Application


Generally you compile the code with the options ‘Run  as a Java Application’ or through some ant script which will do a clean, build and deploy your whole code.which is time consuming.


Hot Deploy,Modify your code straight away unless it's a change in method signature,save your changes,Relaunch the  debugger with the same class(in case any issues with automatic build )and you will notice your changes are reflected without compilation.

Also verify how to Hot Swap classes in ATG Applications running in Weblogic Server

Comments

Post a Comment

Popular posts from this blog

BCC site status inaccessible Agent Production in error state

-
Image
The Error Message showing in BCC T he error logs is showing the below message /atg/epub/DeploymentServer Failed to connect to agent 'Production'. This agent not allowed to be absent for  a deployment. The server will continue attempts to  intialize the connection. Set loggingDebug to true for  continued exception and stacktrace logging. Analysis This happens when the target/Production instance is down for some  reason or the RMI configuration which points to the target/Production instance may not be correct one. Fix If this is happening  due to target/Production instance down  then we can restart the target/Production Server,Other wise  correct the RMI configuration from the BCC agent configuration page and reinitialise. Verify the RMI Port in Configuration.properties file.Usually this file will be located in the path C:\ATG\ATG10.2\home\servers\ATGProduction\localconfig\atg\dynamo\Configuration...
Read more

Weblogic Issues during EAR Deployment Exception in AppMerge flows progression

-
Unable to access the selected application Exception in AppMerge flows progression Bean already exists "weblogic.j2ee.descriptor.ModuleBeanImpl@..../Modules[weblogic.descriptor.internal.Descriptor.Beankey@....] This issue can happen in many scenarios, may be you need to check your deployment descriptors based on Application Servers used, this generally happens due to issue in XML files related to deployment. I got this issue when i mistakenly added the modules twice in the Manifest file, the module 'Store.Storefront' is added more than once in  'ATG-Required'  of my Manifest.MF file,due to this i am seeing the module 'storedocroot.war' is added twice in my application.xml which is located in the  path ATGProd.ear\META-INF\application.xml.Due to this i am not able to deploy my EAR file. I have removed the duplicate entry and deployed the application and everything working fine. ....... <module>         <web>  ...
Read more

Add a shopping cart button to the product page

-
Make sure you have ATG running with your Application  module. We are adding a jsp page fragment called addcart.jsp . This fragment will use two parameters passed from other jsp, skuInfo.jsp - skuId and productId . Add the form and inputs required to add an item to the order,  as shown in the sample code below: <dsp:input type="hidden" bean="CartModifierFormHandler.catalogRefIds" paramvalue="skuId"/> <dsp:input type="hidden" bean="CartModifierFormHandler.productId" paramvalue="productId"/> <dsp:input type="text" size="5" bean="CartModifierFormHandler.quantity" value="1"/> <dsp:input type="hidden" bean="CartModifierFormHandler.addItemToOrderSuccessURL" value="cart.jsp"/> <dsp:input type="submit" bean="CartModifierFormHandler.addItemToOrder" value="Add to Cart"/> Don't forget to import the /at...
Read more