Skip to Content
Oct 18, 2021 at 08:42 AM

BO 4.2 server architecture for resilience



We are looking to migrate from windows server 2008 to windows server 2016 and have < 150 users and < 2000 reports.

Our current environment has 2 servers 24gb ram 8 cpu 1 running tomcat/ajs/2 webi proc servers, the other 2 webi proc server services, other aps services including dsl bridge.

Looking to have some more resilience in the new enviornment to cope with failover/load balancing etc.

If wished to have all components running on both servers (i..e tomcat,ahs, aps, webi proc. servers) such that if one failed no interruption to service users get how could we best achieve this? Assume the new servers we build woudl have to be 28gb 16 cpu to cope with having all services running on them.

How could we deal with situation whereby we give users a url and it point to one machine, if that server was down but other up we wouldn't to have to tell users to use the other url.

Would we need to have another server which directed traffic on automatic basis to one of the servers and ifs ay server1 was down, traffic would automatically route to server2 - how is this best achieved with regards business objects?

Any thoughts/best practices how we could build new system with full high availability/resilience in mind?