什么是一个EAR文件和＆QUOT之间的差异;增强的WebSphere EAR＆QUOT;？ [英] What is the difference between an EAR file and a "WebSphere Enhanced EAR"?

问题描述

假如我有一个标准的EAR文件（以及被用来生成它的源文件，）需要什么额外的处理工作要做，以将其转换为IBM WebSphere中的增强型EAR？

要问这个问题的另一种方法是问：什么是增强型EAR和标准EAR的区别吗？

我非常清楚，有工具在Rational开发工具（RAD和RSA）。但是，对于这个问题的目的，我需要通过Ant或者Maven来完成在自动构建（相同的任务。 ）

解决方案

  

要问这个问题的另一种方法是问：什么是增强型EAR和标准EAR的区别吗？

这是增强EAR是添加到META-INF目录中的一些XML文件的EAR在应用，服务器或单元级别配置特定的资源（请参见IBM红皮书的WebSphere应用服务器V7：为部署打包应用程序了解这方面的更多详细信息）。

J2EE包装，增强耳朵和应用服务器工具包表23-1（ PDF）列出了这些文件：

该文件正在位于META-INF目录下，从Ant或Maven标准EAR嵌入他们应该是pretty直线前进，只是把他们在META-INF包装之前。

如果你不得不从头开始生成这些文件（这个就没有意义恕我直言），那么它真的另一个故事，我不知道这些文件的结构是公开的。

说真的，如果你想使用该功能，找到一个方法来生成从WebSphere增强EAR编辑器中的文件。也许得到RAD的试用版，以评估这一功能> :)或与IBM，我敢肯定，他们会很乐意<击>帮助卖你的东西，甚至一个许可证。

更新： IBM提供<一个href=\"http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.wsps.602.javadoc.doc/doc/com/ibm/websphere/ant/tasks/package-summary.html\">Ant 的任务为WebSphere，你可以从Maven的使用antrun插件也使用（这似乎是preferred方式），但我不认为<一href=\"http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/topic/com.ibm.wsps.602.javadoc.doc/doc/com/ibm/websphere/ant/tasks/DefaultBindings.html\"><$c$c>wsDefaultBindings正是你要寻找的，默认的IBM WebSphere绑定不提供比增强EAR相同的特性 - 但他们可能是有益的，虽然不够。为了以防万一，如果你决定使用<$c$c>wsadmin任务，而不是增强EAR，这里是一个<一个href=\"http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rxml_taskoptions.html\">list的选项。

Supposing that I have a standard EAR file (and the source files that were used to generated it,) what additional processing needs to be done to convert it to an IBM WebSphere "Enhanced EAR"?

Another way to ask this question would be to ask, "What is the difference between an Enhanced EAR and a standard EAR?"

I'm very aware that there is tooling in the Rational development tools (RAD and RSA.) But, for the purpose of this question, I need to accomplish the same task in an automated build (via either Ant or Maven.)

解决方案

Another way to ask this question would be to ask, "What is the difference between an Enhanced EAR and a standard EAR?"

An enhanced EAR is an EAR with some XML files added to the META-INF directory to configure specific resources at the application, server or cell level (see the IBM Redbook WebSphere Application Server V7: Packaging Applications for Deployment for more details on this).

Table 23-1 of J2EE Packaging, Enhanced EARs, and the Application Server Toolkit (pdf) lists these files:

The files being located under the META-INF directory, embedding them in a standard EAR from Ant or Maven should be pretty straight forward, just put them in the META-INF before packaging.

If you have to generate these files from scratch (this wouldn't make sense IMHO), then it's really another story and I'm not sure that the structure of these files is publicly available.

Seriously, if you want to use that feature, find a way to generate the files from the WebSphere Enhanced EAR editor. Maybe get a trial version of RAD to evaluate this feature >:) Or contact IBM, I'm sure they will be happy to helpsell you something, even a single license.

UPDATE: IBM provides Ant Tasks for WebSphere that you could also use from Maven using the antrun plugin (this seems to be the preferred way) but I don't think that wsDefaultBindings is exactly what you're looking for, default IBM WebSphere Bindings don't offer the same features than Enhanced EAR - but they might be useful and enough though. Just in case, if you ever decide to use the wsadmin task instead of Enhanced EAR, here is a list of options.

这篇关于什么是一个EAR文件和＆QUOT之间的差异;增强的WebSphere EAR＆QUOT;？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！