Highly-Available Geocortex Web
-
Commentaire officiel
This post has been updated, to add additional information and reflect our new product branding. Check out:
https://support.vertigis.com/hc/en-us/community/posts/19322043845650-Highly-Available-HA-VertiGIS-Studio-Web -
We have started using GXW in our production environment where we have to address high availability and redundancy across all of the components of the platform.
While we have an HA ArcGIS Enterprise on all tiers, I could not find any information about the recommended HA setup for on-premise Geocortex Web.
Please advise
0 -
Hi Ahmed,
Thanks for your feedback. We are currently looking at adding documentation for this setup. It is currently possible to deploy Web side-by-side on the servers, but I've added your name to the list of stakeholders to add this section.
Thanks, Stefan
0 -
It is worth adding that as Geocortex Web is served out as 100% static content via a web server, any existing high-availability pattern for webservers serving static content would work fine.
0 -
I am interested in this as well
0 -
You can install Geocortex Web on two web servers behind a load balancer, and get it both configured with the same Portal and use the LB domain name for the redirect URL. Once you completed this, you should access the designer and apps through the LB.
0 -
So, basically the same way we have Essentials. I wonder why they dont follow the File Share approach like we get for Portal, Server, Reporting, and Printing.
0 -
The big difference between Geocortex Web / Designer and Geocortex Essentials and some of the other products like Portal / Server / Reporting / Printing is that there is no 'server side' component to Geocortex Web. It is 100% static content that is brought down to the client, and then runs 100% in the client context (no requests to server for any kind of storage or processing).
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
8 commentaires