Web. Logic Split Deployment with Maven. Recipe. Maven 2. 2. Web. Logic 1. 0. 3. Eclipse q. b. How does Split Deployment work. Running and Deploying Applications on Oracle WebLogic Server. This chapter provides a basic overview of the Oracle WebLogic Server environment and information. I wanted to deploy WAR file on weblogic 11g Weblogic Server 10. Normally, in a web application one will have web. In order to make Weblogic pick up the. InformationWeek. com News, analysis and research for business technology professionals, plus peertopeer knowledge sharing. Engage with our community. Managed Coherence Servers provides tight integration between WebLogic Server and Coherence. This integration allows for a simplified. The purpose of the split deployment is to allow the deploy of only altered components in an enterprise application, skipping the steps of packaging and complete application restart. Unfortunately this good idea is not supported by a good implementation. Oracle has in fact decided to impose its own quirky layout and its tools some Ant tasks, without any possibility of customization. Fortunately Web. Logic Server instead provides a very intelligent system to map the virtual layout to the real, phisical, layout. A file called . beabuild. EAR that we want to deploy which permits the mapping between virtual filefolderpackage to absolute locations on the file system. Ill try to give an example of it C progettixxxparentwebsrcmainwebapp web. Oracle Sql Update Statement Time Stamps. C progettixxxparentwebtargetclasses web. WEB INFclasses. C progettixxxparentejbtargetclasses ejb. C Userszzzzzz. APP INFlibcommons logging. C progettixxxparentwebsrcmainwebapp. Note that instead of the Windowss we use, apart from the first after the drive letter. The EJB instead consists only of classes and XML configuration, and in this case were going to take them all from the folder ejbtargetclassesHere instead we map a library jar the Apaches commons logging to the standard enterprise application library folder. Steps To Deploy Ear File In Weblogic' title='Steps To Deploy Ear File In Weblogic' />Obviously are also possible other interesting configurations, for instance you could map a web. Web. Apps war eg if we prototype with Google Web. Toolkit, its shell does not usually use the same web. C progettixxxTest. Splitsrcmainwebappweb. WEB INFweb. xml. Once prepared the file that reflects our folder structure we try to deploy the application, setting the CLASSPATH set. WLSEnv. cmdand then running the deployer java weblogic. Rockss July 7th, 2010 on 1024 pm. Hi Joy, could you please help, i need to use this hot deploy feature in weblogic cluster, i have one cluster with 2 MS. What if after performing this step when i deploy to EAR file. It still would pick another Jar File E. Antlr and Apache Poi jar files. I even tried setting them at. Y07Jx1XqU/VIwxJFyS-rI/AAAAAAAAMlo/TzquVn4N8lM/s1600/8.png' alt='Steps To Deploy Ear File In Weblogic' title='Steps To Deploy Ear File In Weblogic' />Deployer adminurl t. This will be the command that well will launch from out Maven project, using the maven antrun plugin. A bit of foreplay Creating a Maven Test Project. I organized my test enterprise project with this structure We can easily do that creating a parent pom project that include the three modules lt UTF 8 lt project xmlnshttp maven. POM4. 0. 0 xmlns xsihttp www. XMLSchema instance      xsi schema. Locationhttp maven. POM4. 0. 0 http maven. Version 4. 0. Version      lt group. Id net. lucamasini. Id      lt artifact. Id parentlt artifact. Id      lt packaging pomlt packaging      lt version 0. SNAPSHOTlt version      lt modules            lt module earlt module            lt module ejblt module            lt module weblt module      lt modules lt project then inside the poms folder we can create the three archetyes mvn archetype generate Dgroup. Idnet. lucamasini. Dartifact. Idear Darchetype. Artifact. Idear jee. Darchetype. Group. Idorg. codehaus. Dinteractive. Modefalse Darchetype. Version1. 0. 1 Dpackagenet. Dgroup. Idnet. lucamasini. Dartifact. Idwar Darchetype. Artifact. Idwebapp jee. Darchetype. Group. Idorg. codehaus. Dinteractive. Modefalse Darchetype. Version1. 0. 1 Dpackagenet. Dgroup. Idnet. lucamasini. Dartifact. Idejb Darchetype. Artifact. Idejb jee. Darchetype. Group. Idorg. codehaus. Once created we must include the dependencies of the war and ejb into the ears pom lt dependency    lt group. Id test splitlt group. Id      lt artifact. Id ejblt artifact. Id      lt version 0. SNAPSHOTlt version      lt type ejblt type      lt scope compilelt scope lt dependency lt dependency      lt group. Id test splitlt group. Id      lt artifact. Id weblt artifact. Id      lt version 0. SNAPSHOTlt version      lt type warlt type      lt scope compilelt scope lt dependency Now we can try if everything works doing a mvn install and checking if the created ear is correct we auto deploy it in Web. Logic for a quick and dirty check. Configuring deployment into Maven project. Oracle also provides an ANT version of its deploy command, that we can quite easily run from within Maven only adding to the dependencies of the maven antrun plugin plugin Weblogic jars usually added to the classpath from the set. WLSEnv. cmd command lt plugin    lt group. Id org. apache. Id      lt artifact. Id maven antrun pluginlt artifact. Crack In Plastic Shower Tray'>Crack In Plastic Shower Tray. Id      lt version 1. WLDeploy classpathrefmaven. Test. Split sourcesrcmainapplication               userweblogic passwordweblog. Admin. Server        lt tasks                                                             lt configuration      lt dependencies          lt dependency              lt group. Id com. sunlt group. Id              lt artifact. Id toolslt artifact. Id              lt version java. Path java. home. libtools. Path           lt dependency           lt dependency               lt group. Id weblogiclt group. Id               lt artifact. Id weblogiclt artifact. Id               lt version weblogic. Path weblogic. Path            lt dependency            lt dependency                lt group. Id weblogiclt group. Id                lt artifact. Id webserviceslt artifact. Id                lt version weblogic. Path weblogic. Path             lt dependency    lt dependencies                   lt plugin To start the deployment just run the following goal mvn antrun runfrom the ears pom folder, for this to works is necessary to put the. This is a clean solution because this is a source folder for Maven, and as such its readonly during the build goals its never written, but only read to create packages. Its important to notice that against Java EE 5 specifications a correctly configured application. Generating. beabuild. Generate that file is a trivial task, but can be really annoying. For this exist an experimental plugin, the maven beabuild plugin that can generate this for us with few configurations for the most commons enterprise application layout. If indeed that doesnt apply to our environment we can use the maven dependency plugin that can generate for us the most tedious section of the file, which is the paths to the artifacts in the Maven repository that are Enterprise Libraries    lt plugin            lt group. Id org. apache. Id            lt artifact. Id maven dependency pluginlt artifact. Id            lt version 2. File project. File                lt exclude. Scope providedlt exclude. Windows 7 Loader 32 Bit For here. Scope                lt exclude. Types ejb,warlt exclude. Types                lt output. Absolute. Artifact. Filename truelt output. Absolute. Artifact. Filename                lt silent truelt silent        lt configuration    lt plugin This would generate under our target folder a file containing the list of dependencies with their absolute path, which then can be cut and pasted inside.