WSO2 API 管理器集群配置 [英] WSO2 API Manager Clustering configuration

问题描述

我正在尝试为 WSO2 API 管理器安装和配置高可用性设置.我一直在阅读此文档:http://docs.wso2.org/wiki/display/Cluster/Clustering+API+Manager 并在那里解释了将应用程序的 4 个组件分解为单独的文件夹，并且这 4 个组件可以在单个服务器上运行.我不确定为什么需要这样做.我真正想要做的就是在两台服务器上安装完整的应用程序(不要将应用程序分成 4 个不同的部分)，然后将它们聚集在两台服务器之间，并在它们前面放置一个弹性负载均衡器.如果它们都用完单个安装，那么在同一台服务器上拆分多个组件的目的是什么?如果一台服务器出现故障，我正在寻找最简单的方法来为该应用程序提供故障转移功能.如果您对他们的方法有任何见解，我们将不胜感激.

I'm trying to install and configure a highly availability setup for the WSO2 API Manager. I've been reading through this document: http://docs.wso2.org/wiki/display/Cluster/Clustering+API+Manager and in there it explains to break up the 4 components of the application into separate folders and that these 4 components can run on a single server. I'm not sure why this is needed. All I really want to do is take 2 servers, install the full application on both of them (without breaking the application up into 4 different pieces) and cluster them together between two servers with an Elastic Load Balancer in front of them. What is the purpose of splitting up the multiple components on the same server if they all run out of a single installation? I'm looking for the simplest way to provide fail over capability to this application if one server goes down. Any insight into their methodology would be greatly appreciated.

谢谢.

推荐答案

My 2cts:

备注中提到的文档解释了 WSO2 如何看待集群世界.在不同的 JVM 上传播不同的功能.从架构的角度来看，这听起来很合乎逻辑.一个缺点是不同的应用程序也需要由操作来管理.这使得技术架构相当复杂.

The documentation mentioned in the remarks, explains how WSO2 sees the world of clustering. Spread the different functionality over different JVM's. This sounds logical from architectural point of view. A dis-advantages is that the diffent applications need to me administrated as well by operations. This makes the technical architecture rather complex.

在我们的情况下，我们定义了 2 个具有额外 CPU 和内存的不同服务器，在这些服务器上我们安装了完整的 WSO2 API 管理器并定义了集群配置.通过 Puppet 提供的所有内容.

In our situation, we defined 2 different servers with extra CPU and memory, on these servers we have installed the full WSO2 API Manager and defined the cluster configuration. Everything provisioned via Puppet.

只需简单的安装，所有数据源都指向 Oracle 数据库中的一个模式.

Just a straightforward install, all data-source pointing to one schema in an Oracle database.

而且……它正在工作；我们的开发人员很高兴，运营很高兴，架构师部门很高兴

And...it is working; Our Developers happy, Operations happy, Architect department happy

这篇关于WSO2 API 管理器集群配置的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！