To XebiaLabs, we know each other in automatic deployment of applications Popular dance EE there. One of the most surprising things domiciles due to the fact that the suppliers of servers of application do not seem to be part of persons who maitrisent the best the deployment of applications .

In a previous article, we described what we consider to be the deployment of application total J2EE. And force is to note that:

• Display go really beyond of a simple deployment of EAR or of WAR.
• Most applications also need other art facts as for example static contents for the server web or else files of shape, used by code popular dance, in starting.
• It is also necessary to configurer of resources JEE as DATASOURCES JDBC or components JMS (Tails, Topics, Servers).
• To this is added, of course, the shape of the very middleware: creation and shape of clusters of servers of application or of virtual hosts of a server Apache.
• The death-warrant of tasks is important to reduce (or even to tell) the service cut of application during deployment and to augment by it the speed.

Then let us put us down question. What offer us the suppliers of servers of application in this domain?

Oracle WebLogic Server

Oracle WebLogic Server offers a concept of ' Deployment ': it is the thing which you create when you display EAR, WAR or EJB JAR. Sic! You can adapt him to environment by giving a plan of deployment. However, nothing is offered to regroup several ART FACTS JEE in the single deployment or to include the creation of resources JEE such as Datasource.

In WebLogic, there is the concept of ' SubDeployement ' but mysteriously it is not corr l in a deployment. It is a mechanism used to target parts of a module JMS towards servers JMS or servers WebLogic. The device offered by modules JMS seems intended only to regroup resources JMS. Undoubtedly that one day a developer initially called it Deployment without remembering that concept has existed already in WebLogic and he then reappointed it SubDeployement. Of course, all this is only calculation!

WebLogic offers a big number of IPA - INTERNATIONAL PHONETIC ALPHABET for deployment: WebLogic review. Online Deployer of order, task ANT and , WLST for the intimate, based on Python. This last is, I think, the most complete. Thanks to his representation in form of system of file of the hierarchy of MBEANS, he gives a very intuitive means to achieve information.

JBOSS APPLICATION SERVER

The deployment in JBOSS is managed by the Virtual Deployment Framework. It is a framework based on MBEANS that allows different art facts (EARS, WARs, EJB GANDER, RARs, SARS) and in different resources (sources of data, parametres JMS) to be displayed on JBOSS. All this is managed by their deployers.

However, most people do not invoke this deployers, nor even . They simply prefer depositing their art facts in the directory deploy/ of their server of application Jboss, then wait that Deployment Scanner discerns it. They prove then in the file of log that deployment is ended.

Worry with this method: deployment is not an atomic operation. When a deployment is automated, they want to start again the server web only after a successful deployment of the new WAR. But write an end of code which analyses the logs of the server in search of a key word am simply seedy. An alternative would be to position property ScanEnabled of DeploymentScanner in false to invoke manually deployer. Not only it complexifie encodes the, but it is also necessary to envisage the copy of files in the directory deploy of the server JBOSS.

So, it proves to be that with JBOSS APPLICATION SERVER, it is difficult to include deployments towards its servers into a scenario of more total deployment. RedHat must correct this problem as quickly as possible so that JBOSS is indeed ready for firms.

IBM WEBSPHERE APPLICATION SERVER

And for the big monster JEE from ' Big Blue '? He gives a polyvalent and transactional way to display applications and resources. On the whole, the language of script allows to control all aspects of WEBSPHERE. For example, you can synchronise knots expressly and the conjuration of method (by Jython or JACL) to display application will return the hand only when operation will be accomplished. The negative side is that it is much slower than the similar tool WLST offered by WebLogic (many copies of documents XML across SOAP have to be for something) and IPA - INTERNATIONAL PHONETIC ALPHABET there offered are rather complex to manipulate (who can give difference between one containment path, one configuration id and one object name?)

Although WAS does not offer mechanisms to regroup the art facts different and resources linked to the same deployment, the transactional nature allows to commiter the different changes of shape all at once. He can even manage the shape of the authorities of servers IBM HTTP SERVER or Apache HTTP Server.

In spite of a slow speed of deployment, nothing is worth the reliability of deployments of WEBSPHERE!

Conclusion

The servers of application give each a level of different support to take care of deployments of the applications of firm. Of course, they all give the basic deployment of ART FACTS POPULAR DANCE EE but none of them offers to regroup different art facts in the single deployment or to link resources Popular dance EE to this art facts. WebLogic SERVER is the only one who tries to regroup resources (JMS Modules and SubDeployment). But these abstractions cover only a baby left all expanse of deployment Popular dance EE.

Repetition and prediction are very important for a successful strategy of deployment, what can explain the previsibility of WEBSPHERE on the market. And finally, good one IPA - INTERNATIONAL PHONETIC ALPHABET is necessary to automate your process of deployment: WebLogic and WEBSPHERE give it, JBOSS has a serious lack in this domain (even with twiddle !)

The consultants of and all the developers to XebiaLabs all practically wrote in their past experiences of the tons of scripts to automate deployments and had to battle on these questions still and still. We developed Deployit to take care of this difference between servers of applications and because we think that the automation of deployments is the highest importance due to the number growing by deployments in firms.

Translation free from the ticket Do APPLICATION SERVER vendors really understand Deployment? published by Vincent Partington.