I want to use Aris 9.8 Connectserver on a 2 node Windows environment, not for high availability purposes, but for horizontal scale out. We prefer some smaller servers instead of 1 big server. Some questions:
Will an Aris 9.x multi node environment working fine and not complex to manage?
Why is an Aris9.x multi node environment installation not part of the installation manual and a training will be necessary?
0
22.5k
8
by Runé Becker
Posted on Mon, 09/07/2015 - 19:31
Dear Nico,
ARIS' cloud architecture opens up several dimensions to scale up with the customer's needs, e.g., larger number of users, broader product adoption, higher performance, added failover or high availability etc.
These various adoptions can't be delivered by standardized setups, which are meant to support a fixed installation scenario. Our server setups are meant for single node installations and can update only such.
A multi node installation requires manual software deployment/provisioning as well as updating such installations manually.
As you probably know, instead of acquire all that knowledge, the alternative is hiring Software AG Global Consulting Service or its implementation partners.
Yes, you are right. The higher complexity is the price you pay for the advantage to scale an ARIS installation across several computers, e.g., each with a low or medium hardware sizing, instead of having ARIS installed only one computer with lots of hardware for delivering the same performance.
Not to mention that fail-over or high availability isn't of course out of scope when there is only one computer. E.g. if the Business Server runs on 3 nodes/computers, one could simply fail without data loss or an interruption at the client side.
1) Yes, I heard about projects where HW based load balancing was used. Please contact your Software AG sales representative to request for implementation services.
2) ARIS uses inside TomEE for serveral apps/services, but HA is realized between ARIS apps by redundancy and sharing the work load.
Its possible to split all runnables to each node, but the ARIS will not behave like a multi node high availability enviromnet . But its helpful if you have limited HW resources. (also works with ARIS9)
Node n1 - 4 installed runnables. ID State Version Type abs1 STARTED 10.0.17.XX com.aris.modeling.components.y-server-run-prod cs1 STARTED 10.0.17.XX com.aris.cip.y-cloudsearch-run-prod oct1 STARTED 10.0.17.XX com.aris.octopus.y-octopus_server-run-prod sim1 STARTED 10.0.17.XX com.aris.modeling.components.simulationserver.y-simuserver-run-prod
Node n2 - 9 installed runnables. ID State Version Type apg1 STARTED 10.0.17.XX com.aris.age.age-run-prod cop1 STARTED 10.0.17.XX com.aris.copernicus.copernicus-portal-server-run-prod es1 STARTED 10.0.17.XX com.aris.runnables.elasticsearch-run-prod ads1 STARTED 10.0.17.XX com.aris.adsadmin.y-adsadmin-run-prod umc1 STARTED 10.0.17.XX com.aris.umcadmin.y-umcadmin-run-prod ecp1 STARTED 10.0.17.XX com.aris.runnables.ecp-run-prod lb1 STARTED 10.0.17.XX com.aris.runnables.httpd.httpd-run-prod zoo0 STARTED 10.0.17.XX com.aris.runnables.zookeeper-run-prod das1 STARTED 10.0.17.XX com.aris.dashboarding.dashboarding-run-prod
In case of multinode installation you will need replicate of all runnables and to do addional configuration of zookeeprs and elasticsearchs. So you will need at least 3 nodes/computers.
