红帽全球峰会第 6 章 其他修改
6.1. 修改 JBoss EAP Natives 和 Apache HTTP 服务器的提供方式
这个版本里 JBoss EAP 7 Natives 的提供与之前不同，其中一些现在附带新的 Red Hat JBoss Core Services 产品，这是许多 Red Hat JBoss 中间件产品常用的一套补充软件。新产品提供了更快的更新分发和更一致的更新体验。JBoss Core Services 产品可以在 Red Hat 客户门户网站的不同位置来下载。
下表列出了不同 JBoss EAP 版本的提供方式间不同之处。
软件包 JBoss EAP 6 JBoss EAP 7 用于消息处理的 AIO Natives
和单独的 "Native Utilities" 下载里的产品一起提供
包含在 JBoss EAP 里，不需要额外的下载。
Apache HTTP 服务器
和单独的 "Apache HTTP Server" 下载里的产品一起提供
和新的 "JBoss Core Services" 产品一起提供
mod_cluster、mod_jk、isapi 和 nsapi 连接器
和单独的 "Webserver Connector Natives" 下载里的产品一起提供
和新的 "JBoss Core Services" 产品一起提供
JSVC
和单独的 "Native Utilities" 下载里的产品一起提供
和新的 "JBoss Core Services" 产品一起提供
OpenSSL
和单独的 "Native Utilities" 下载里的产品一起提供
JBoss EAP 7 已舍弃它
tcnatives
和单独的 "Native Components" 下载里的产品一起提供
JBoss EAP 7 已舍弃它
您应该注意到下列变化：
已停止对和 RHEL RPM 频道的 Apache HTTP 服务器一起使用的 mod_cluster 和 mod_jk 连接器的支持。如果您从 RHEL PRM 频道运行 Apache HTTP 服务器并需要平衡 JBoss EAP 7 服务器的负载，您可以使用下列方法之一：
- 使用 JBoss Core Services 提供的 Apache HTTP 服务器。
- You can configure JBoss EAP 7 to act as a front-end load balancer. For more information, see Configuring JBoss EAP as a Front-end Load Balancer in the JBoss EAP Configuration Guide.
- You can deploy Apache HTTP Server on a machine that is supported and certified and then run the load balancer on that machine. For the list of supported configurations, see Overview of HTTP Connectors in the JBoss EAP 7 Configuration Guide.
已停止对和 HP-UX Web Server Suites 的 Apache HTTP 服务器一起使用的 mod_cluster 和 mod_jk 连接器的支持。如果您从 HP-UX Web Server Suites 运行 Apache HTTP 服务器并需要平衡 JBoss EAP 7 服务器的负载，您可以使用下列方法之一：
- You can configure JBoss EAP 7 to act as a front-end load balancer. For more information, see Configuring JBoss EAP as a Front-end Load Balancer in the JBoss EAP Configuration Guide.
- You can deploy Apache HTTP Server on a machine that is supported and certified and then run the load balancer on that machine. For the list of supported configurations, see Overview of HTTP Connectors in the JBoss EAP Configuration Guide.
- You can find more information about JBoss Core Services in the Apache HTTP Server Installation Guide.
6.2. 在 Amazon EC2 上部署的修改
A number of changes have been made to the Amazon Machine Images (AMI) in JBoss EAP 7. This section briefly summarizes some of those changes.
- 在 Amazon EC2 里启动非群集和群集的 JBoss EAP 实例和域已进行重大修改。
-
JBoss EAP 6 将
User Data:字段用于 JBoss EAP 配置。JBoss EAP 7 已删除解析User Data:字段配置及在实例启动时自动启动服务器的 AMI 脚本。 - 以前的 JBoss EAP 版本安装了 Red Hat JBoss Operations Network 代理，而在 JBoss EAP 7 里，您需要单独安装它。
For details on deploying JBoss EAP 7 on Amazon EC2, see Deploying Red Hat JBoss Enterprise Application Platform on Amazon EC2.
6.3. Changes to JBoss EAP Scripts
The add-user script behavior has changed in JBoss EAP 7 due to a change in password policy. JBoss EAP 6 had a strict password policy. As a result, the add-user script rejected weak passwords that did not satisfy the minimum requirements. In JBoss EAP 7, weak passwords are accepted and a warning is issued. For more information, see Setting Add-User Utility Password Restrictions in the JBoss EAP Configuration Guide.
6.4. Removal of OSGi Support
When JBoss EAP 6.0 GA was first released, JBoss OSGi, an implementation of the OSGi specification, was included as a Technology Preview feature. With the release of JBoss EAP 6.1.0, JBoss OSGi was demoted from Technology Preview to Unsupported.
In JBoss EAP 6.1.0, the configadmin and osgi extension modules and subsystem configuration for a standalone server were moved to a separate EAP_HOME/standalone/configuration/standalone-osgi.xml configuration file. Because you should not migrate this unsupported configuration file, the removal of JBoss OSGi support should not impact the migration of a standalone server configuration. If you modified any of the other standalone configuration files to configure osgi or configadmin, those configurations must be removed.
For a managed domain, the osgi extension and subsystem configuration were removed from the EAP_HOME/domain/configuration/domain.xml file in the JBoss EAP 6.1.0 release. However, the configadmin module extension and subsystem configuration remain in the EAP_HOME/domain/configuration/domain.xml file. This configuration is no longer supported in JBoss EAP 7 and must be removed.
