设置并配置基本的高可用性环境的主服务器和备份服务器。
| 缩写 | 术语 |
|---|---|
| URI | 统一资源标识 |
| JTS | Jazz Team Server V4 |
| CCM | “变更和配置管理”应用程序 V4 |
| QM | “质量管理”应用程序 V4 |
| RM | “需求管理”应用程序 V4 |
| CLM | Collaborative Lifecycle Management(JTS、CCM、QM 和 RM) |
| LPA | 生命周期项目管理 |
通常,jts.war 应用程序在将单一应用程序服务器作为目标的情况下进行安装。由于引入了 Web 服务器,所以必须将应用程序容器配置修改为允许通过 Web 服务器进行路由。
com.ibm.team.fulltext.indexLocation=I\:/sharedIndexFolder/workitemindex
com.ibm.team.fulltext.indexLocation=/net/LinuxHost/sharedIndex/workitemindex
com.ibm.team.repository.scheduler.migration.mode.enabled=true
每次将 WebSphere Application Server 配置为通过 Web 服务器将请求路由到应用程序服务器时,Web 服务器的 plugin.xml 文件都将根据该应用程序服务器的连接信息进行更新。此时,您对 plugin-cfg.xml 文件进行了部分配置。在 Web 服务器上,请替换并接着编辑 plugin-cfg.xml 的下一节以完成配置。这个 plugin-cfg.xml 文件位于 Web 服务器的 plugin\config\webserver1 文件夹中,其中 webserver1 是您在上一节(安装并配置 IBM HTTP Server 和 Web 服务器插件)对该 Web 服务器指定的名称。
URI 组
根据高可用性环境设置不同,以及根据您是打算对每个应用程序分别使用一个 WebSphere Application Server 实例还是对所有应用程序使用一个应用程序服务器,您必须相应地进行规划。URI 组是集群提供的 URI 的逻辑分组。例如,如果对每个应用程序分别使用一个 WebSphere Application Server 实例,请为每个应用程序声明一个集群。这将对单一集群应用一个 URI 组。URI 分组可能与以下示例类似:
<!-- JTS URI Group -->
<UriGroup Name="default_host_JTS_basicHA_Cluster_URIs">
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/admin/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/jts/*"/>
</UriGroup>
<!-- CCM URI Group -->
<UriGroup Name="default_host_CCM_basicHA_Cluster_URIs">
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ccm/*"/>
</UriGroup>
<!-- QM URI Group -->
<UriGroup Name="default_host_QM_basicHA_Cluster_URIs">
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/qm/*"/>
</UriGroup>
<!-- RM URI Group -->
<UriGroup Name="default_host_RM_basicHA_Cluster_URIs">
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/rm/*"/>
</UriGroup>
服务器集群
如果对每个应用程序设置一个 WebSphere Application Server 实例,那么必须将服务器集群设置为包括所有提供了一个应用程序 URI 的服务器。CLM 应用程序的服务器集群可能与以下示例类似:
<!-- JTS Server Cluster -->
<ServerCluster CloneSeparatorChange="false" GetDWLMTable="false" IgnoreAffinityRequests="true" LoadBalance="Round Robin" Name="server1_jts_Cluster" PostBufferSize="64" PostSizeLimit="-1" RemoveSpecialHeaders="true" RetryInterval="60">
<Server LoadBalanceWeight="0" ConnectTimeout="0" ExtendedHandshake="false" MaxConnections="-1" Name="jts1Node01_server1" ServerIOTimeout="0" WaitForContinue="false">
<Transport Hostname="jts1.example.com" Port="9080" Protocol="http"/>
<Transport Hostname="jts1.example.com" Port="9443" Protocol="https">
<Property Name="keyring" Value="/root/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.kdb"/>
<Property Name="stashfile" Value="/root/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.sth"/>
</Transport>
</Server>
<Server LoadBalanceWeight="1" ConnectTimeout="0" ExtendedHandshake="false" MaxConnections="-1" Name="jts2Node01_server1" ServerIOTimeout="0" WaitForContinue="false">
<Transport Hostname="jts2.example.com" Port="9080" Protocol="http"/>
<Transport Hostname="jts2.example.com" Port="9443" Protocol="https">
<Property Name="keyring" Value="/root/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.kdb"/>
<Property Name="stashfile" Value="/root/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.sth"/>
</Transport>>
</Server>
</ServerCluster>
<!-- End JTS Server Cluster -->
<!-- CCM Server Cluster -->
<ServerCluster CloneSeparatorChange="false" GetDWLMTable="false" IgnoreAffinityRequests="true" LoadBalance="Round Robin" Name="server1_ccm_Cluster" PostBufferSize="64" PostSizeLimit="-1" RemoveSpecialHeaders="true" RetryInterval="60">
<Server LoadBalanceWeight="0" ConnectTimeout="0" ExtendedHandshake="false" MaxConnections="-1" Name="ccm1Node01_server1" ServerIOTimeout="0" WaitForContinue="false">
<Transport Hostname="ccm5.example.com" Port="9080" Protocol="http"/>
<Transport Hostname="ccm5.example.com" Port="9443" Protocol="https">
<Property Name="keyring" Value="/root/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.kdb"/>
<Property Name="stashfile" Value="/root/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.sth"/>
</Transport>
</Server>
<Server LoadBalanceWeight="1" ConnectTimeout="0" ExtendedHandshake="false" MaxConnections="-1" Name="ccm2Node01_server1" ServerIOTimeout="0" WaitForContinue="false">
<Transport Hostname="ccm6.example.com" Port="9080" Protocol="http"/>
<Transport Hostname="ccm6.example.com" Port="9443" Protocol="https">
<Property Name="keyring" Value="/root/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.kdb"/>
<Property Name="stashfile" Value="/root/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.sth"/>
</Transport>
</Server>
</ServerCluster>
<!-- End CCM Cluster -->
<!-- QM Server Cluster -->
<ServerCluster CloneSeparatorChange="false" GetDWLMTable="false" IgnoreAffinityRequests="true" LoadBalance="Round Robin" Name="server1_qm_Cluster" PostBufferSize="64" PostSizeLimit="-1" RemoveSpecialHeaders="true" RetryInterval="60">
<Server LoadBalanceWeight="0" ConnectTimeout="0" ExtendedHandshake="false" MaxConnections="-1" Name="qm1Node01_server1" ServerIOTimeout="0" WaitForContinue="false">
<Transport Hostname="qm7.example.com" Port="9080" Protocol="http"/>
<Transport Hostname="qm7.example.com" Port="9443" Protocol="https">
<Property Name="keyring" Value="/root/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.kdb"/>
<Property Name="stashfile" Value="/root/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.sth"/>
</Transport>
</Server>
<Server LoadBalanceWeight="1" ConnectTimeout="0" ExtendedHandshake="false" MaxConnections="-1" Name="qm2Node01_server1" ServerIOTimeout="0" WaitForContinue="false">
<Transport Hostname="qm8.example.com" Port="9080" Protocol="http"/>
<Transport Hostname="qm8.example.com" Port="9443" Protocol="https">
<Property Name="keyring" Value="/root/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.kdb"/>
<Property Name="stashfile" Value="/root/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.sth"/>
</Transport>
</Server>
</ServerCluster>
<!-- End QM Cluster -->
<!-- RM Server Cluster -->
<ServerCluster CloneSeparatorChange="false" GetDWLMTable="false" IgnoreAffinityRequests="true" LoadBalance="Round Robin" Name="server1_rm_Cluster" PostBufferSize="64" PostSizeLimit="-1" RemoveSpecialHeaders="true" RetryInterval="60">
<Server LoadBalanceWeight="0" ConnectTimeout="0" ExtendedHandshake="false" MaxConnections="-1" Name="rm1Node01_server1" ServerIOTimeout="0" WaitForContinue="false">
<Transport Hostname="rm3.example.com" Port="9080" Protocol="http"/>
<Transport Hostname="rm3.example.com" Port="9443" Protocol="https">
<Property Name="keyring" Value="/root/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.kdb"/>
<Property Name="stashfile" Value="/root/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.sth"/>
</Transport>
</Server>
<Server LoadBalanceWeight="1" ConnectTimeout="0" ExtendedHandshake="false" MaxConnections="-1" Name="rm2Node01_server1" ServerIOTimeout="0" WaitForContinue="false">
<Transport Hostname="rm4.example.com" Port="9080" Protocol="http"/>
<Transport Hostname="rm4.example.com" Port="9443" Protocol="https">
<Property Name="keyring" Value="/root/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.kdb"/>
<Property Name="stashfile" Value="/root/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.sth"/>
</Transport>
</Server>
</ServerCluster>
<!-- End RM Cluster -->
路由
Route 元素是 URI 组与服务器集群的绑定位置。Route 元素将“哪些 URI 由哪个集群提供”这一情况告知插件。以上一个示例为基础,Route 元素示例将应用程序 URI 与其相应的集群绑定,如下所示:
<Route ServerCluster="server1_jts_Cluster" UriGroup="default_host_JTS_basicHA_Cluster_URIs" VirtualHostGroup="default_host"/>
<Route ServerCluster="server1_ccm_Cluster" UriGroup="default_host_CCM_basicHA_Cluster_URIs" VirtualHostGroup="default_host"/>
<Route ServerCluster="server1_qm_Cluster" UriGroup="default_host_QM_basicHA_Cluster_URIs" VirtualHostGroup="default_host"/>
<Route ServerCluster="server1_rm_Cluster" UriGroup="default_host_RM_basicHA_Cluster_URIs" VirtualHostGroup="default_host"/>
定制服务器属性不会自动地在主服务器与备份服务器之间进行同步。为了确保备份服务器具有一致的配置属性,必须在备份服务器激活之前将所有定制设置传播到备份服务器。从主服务器定期备份这些文件并将其复原到备份服务器即可确保可定制的服务器属性保持同步。
为了实现高可用性,您必须在主服务器关闭时了解到此情况。了解此情况对于这种基本的高可用性解决方案而言至关重要(此解决方案不支持进行自动故障转移以便从主服务器切换到备份服务器)。
检测故障服务器的过程是一项必须及时完成的紧急任务。服务器故障可以由多个因素体现,例如网络问题、配置问题、应用程序超负荷或用户错误。无论您选择哪种解决方案来检测服务器故障,都必须确保尽可能及时地发出警报。