Issues with ArcGIS Enterprise 11.0 Portal Stability After URL Rewrite Setup

[CanDAGDELEN1]

Hello everyone,

I recently followed the steps outlined in this post to configure URL Rewrite and Application Request Routing (ARR) on IIS, aiming to simplify the URL structure and mask internal ports for our ArcGIS Monitor 2024.0.1 setup.

While this setup works, I noticed that after enabling the URL Rewrite rule, the Experience Builder within our ArcGIS Enterprise portal started behaving inconsistently. Specifically, it fails to load necessary JavaScript files when opening applications, leading to unstable performance. Disabling URL Rewrite resolves the issue, but of course, that defeats the purpose of the setup.

I’d prefer not to use a subdomain for this configuration if possible. Is there an alternative approach to set up URL rewriting or proxying that could help avoid this stability issue with the Experience Builder? Or are there specific settings within IIS or ARR that could be adjusted to allow Experience Builder to load all required resources correctly?

Thanks in advance for any insights or recommendations!

[StevenB]

Did you enable the URL Rewrite and Application Request Routing (ARR) on your IIS web server hosting the Web Adaptors? If so this can cause issues with the internal "arcgis" instance name of your Portal for ArcGIS and ArcGIS Servers. 

If the above is true can you install IIS on your ArcGIS Monitor server to setup the URL Rewrite and Application Request Routing (ARR)?

[CanDAGDELEN1]

Thank you for your response.

In our setup, the Server, Portal, Monitor, and Web Adaptors are all hosted on a single machine. With the 11.4 update, the integration of ArcGIS Monitor with the Web Adaptor was introduced, so I’m attempting to configure the setup through the Web Adaptor. However, I’m encountering issues in providing a URL that aligns with the Web Adaptor’s expected format, particularly on the Fully Qualified Domain Name (FQDN) side, which results in errors.

Do you have any recommendations for addressing this within a single-machine deployment, or adjustments that can be made to ensure compatibility with the Web Adaptor’s URL requirements?

Thanks in advance for your insights.

[StevenB · Accepted solution]

I would not recommend to deploy ArcGIS Monitor on any machines that are hosting ArcGIS Enterprise components. Having an all in one deployment of ArcGIS Enterprise is fine if you are a smaller organization and don't anticipate to grow over a small handful of concurrent users. 

My recommendations for you are:
#1. Place ArcGIS Monitor and it's PostgreSQL DB onto its own dedicated host with a starting size of 4 vCPU and 16 GB RAM. Optionally with IIS and URL Rewrite and Application Request Routing (ARR) configured.

#2. I have not tested the 11.4 web adaptor configuration with ArcGIS Monitor yet but I know it will not require the URL Rewrite and Application Request Routing (ARR) to function as these were workarounds when the ArcGIS Web Adaptors didn't support ArcGIS Monitor, so uninstall or disable this functionality from your ArcGIS Enterprise machines.

[CanDAGDELEN1]

Thank you for your recommendations! Currently, I am proceeding with a single machine deployment. If possible, I will configure it with the Web Adaptor; if not, I’ll stick with the current setup for now.

Your input is greatly appreciated.