dm Server 2.0 RC1 released

Engineering
Andy Wilkinson
December 18, 2009

Hot on the heels of Spring 3.0 and Spring DM 1.2.1, I’m delighted to announce that dm Server 2.0 RC1 is now available. RC1 is feature complete and, barring any major problems being found, will be the final 2.0 release early in the new year. So, please download the RC and give us your feedback: it’s your last chance to shape the 2.0 release!

If you’re interested in what’s changed since M6, please take a look at the release notes.

Thank you for all of the feedback that we’ve had during the development of 2.0. Please keep it coming as we move towards the final release.
Feature overview

There’s a lot of great stuff in the 2.0 release. Here’s a brief overview:

dm Shell - we've added a brand new shell in 2.0, that's available both in-process and remotely over ssh. It provides extensive support for managing a dm Server instance and its deployed artifacts.
Admin console - the admin console has been extensively overhauled in 2.0. It provides, among other things, support for managing and deploying artifacts, examining diagnostic dumps, and examining the bundle wiring both in the live system, and at the time of a resolution failure.
Plans - dm Server 2.0 introduces support for plans which are powerful alternative to 1.0's PARs for deploying modular applications. A plan can be used to reference all of the artifacts that comprise your application, optionally making the application atomic to tie the child artifact lifecycles together, and scoped to isolate the application from other applications deployed in the same dm Server instance.
Provisioning - dm Server's always had excellent provisioning support and in 2.0 it's got even better. In addition to the automatic provisioning of bundles based on the needs of the installed applications that was available in 1.0, dm Server 2.0 provides support for provisioning plans, PARs, and configuration from both local and remote repositories.
Web support - dm Server 2.0 builds upon 1.0's Web support and embeds the Tomcat-based reference implementation for the OSGi Web Container specification, allowing users to deploy vanilla WAR files with all their dependencies in WEB-INF/lib, and Web Application Bundles that import their dependencies via OSGi manifest metadata. The web container is configurable using the standard Tomcat server.xml.
User region - dm Server 2.0 introduces a user region which isolates the dm Kernel from user-installed applications. Among other things, this simplifies administration as it allows users to focus on user application artifacts and their dependencies without having to deal with those of the kernel as well.
Spring 3.0 - like many others, we've been tracking the Spring 3.0 milestones and release candidates, and dm Server 2.0 now packages Spring 3.0 final. If you'd prefer to use dm Server 2.0 with a different version of Spring, it can easily be configured to do so.
Hot deployment - in addition to support for deployment via the admin console, artifacts can also be deployed to dm Server by copying them into the pickup directory, either in archive or exploded form.
Running as a service - dm Server can now be run as a Windows service or as a Unix background process.
Logging - as in 1.0, dm Server's logging support is available via SLF4J. In 2.0, the backend has been replaced with LogBack, making it extensively configurable by modifying dm Server's config/serviceability.xml file with a rich set of appenders available out of the box.
Equinox 3.5 - dm Server 2.0 embeds Equinox 3.5, the reference implementation of OSGi 4.2.

comments powered by Disqus

translate：
翻译：

继Spring3.0和SpringDM1.2.1之后，我很高兴地宣布，DMServer2.0RC1已经上市。RC1的功能已经完成，除非发现任何重大问题，否则它将在新年的早些时候发布最终的2.0版本。所以，请下载RC并给我们你的反馈：这是你塑造2.0版本的最后机会！
如果您对M6以后的变化感兴趣，请查看发行说明。
感谢您在2.0开发期间提供的所有反馈。请继续它来，因为我们走向最后的释放。
功能概述
2.0版本中有很多很棒的东西。以下是简要概述：
dm Shell-我们在2.0中添加了一个全新的Shell，它可以通过ssh进行进程内和远程访问。它为管理dm服务器实例及其部署的构件提供了广泛的支持。
管理控制台-管理控制台已经在2.0中进行了广泛的检修。除其他外，它还支持管理和部署工件、检查诊断转储、检查实时系统中和解决失败时的捆绑包连接。
计划-DMServer2.0引入了对计划的支持，这是部署模块化应用程序的1.0的PAR的强大替代方案。可以使用一个计划来引用组成应用程序的所有工件，可以选择使应用程序原子化以将子工件生命周期绑定在一起，并设置作用域以将应用程序与部署在同一dm Server实例中的其他应用程序隔离。
资源调配-dm Server总是有很好的资源调配支持，在2.0中甚至更好。除了根据1.0中提供的已安装应用程序的需要自动提供捆绑包外，dm Server 2.0还支持本地和远程存储库中的配置计划、par和配置。
Web支持—DMServer2.0基于1.0的Web支持，嵌入了基于Tomcat的OSGi Web容器规范的引用实现，允许用户在Web-INF/lib中部署具有所有依赖项的vanilla WAR文件，以及通过OSGi清单元数据导入依赖项的Web应用程序包。web容器可以使用标准的Tomcat server.xml进行配置。
用户区域-dm Server 2.0引入了一个用户区域，它将dm内核与用户安装的应用程序隔离开来。除此之外，这简化了管理，因为它允许用户专注于用户应用程序工件及其依赖项，而无需处理内核工件。
Spring3.0和其他许多版本一样，我们一直在跟踪Spring3.0的里程碑和发布候选版本，而DMServer2.0现在已经打包了Spring3.0的最终版本。如果您希望在不同版本的Spring中使用dm Server 2.0，可以很容易地对其进行配置。
热部署-除了通过管理控制台支持部署之外，还可以通过将工件以存档或分解的形式复制到pickup目录来将其部署到dm Server。
作为服务运行-dm Server现在可以作为Windows服务或Unix后台进程运行。
日志记录-与1.0中一样，dm Server的日志记录支持可通过SLF4J获得。在2.0中，后端已被LogBack替换，通过修改dm Server的config/serviceability.xml文件以及一组现成的丰富附加程序，可以对其进行广泛的配置。
Equinox3.5-DMServer2.0嵌入了Equinox3.5，这是OSGi4.2的参考实现。