Latest Contributions by AngusHooper1

‎08-04-2021

Unfortunately the locks cannot be easily cleared as the python tool errors out due to the scale of locks. It does clear some, but not all.

‎07-11-2021

What is the system locale time for the various VMs that support Portal, hosting server etc?

‎06-22-2021

We have an enterprise geodatabase (AWS Aurora, postgres) that has a significant number of sessions and locks (10,000+). These sessions and locks date back to 8+ months ago. These tables and feature classes are only accessed by cached map services from a multi-machine ArcGIS Server site. All of these map services have been set to use "shared services" in the pooling. Theoretically if everything maxed out we would expect to see 200 concurrent connections to the database via these services. We have tested these services in our dev environment using dedicated pooling and cannot replicate these persistent lock issues. Has anyone else noticed that shared services from a multi-machine ArcGIS Server site not dropping the connection to the database? Our assumption is that when the service is recycled it never truly drops the connection. This is somewhat justified by Aurora never showing 0 connections to the database as there is always the minimum threshold as indicated by our shared service pooling size. update We have been able to replicate the schema locks persisting after the service has been stopped in our dev environment. Only changing the number of shared instances for the ArcGIS Server site cleared the locks.

‎06-15-2021

That looks correct. Keep in mind that the rollback is quite easy, just change it back to machine name. Also, this only applies for Portal for ArcGIS. ArcGIS Server does not allow you to /edit the web adaptor endpoint. In order to achieve the same end result you'll need to reinstall the WA and ensure you access the configuration endpoint via the DNS alias from the local machine when configuring it. This may not be relevant for the recent releases though as the web adaptor config process has been tweaked by the looks of it.

‎06-01-2021

Sorry, yes it should be ALB. When we set the health check to use the web adaptor we generally have no issues and as you have suggested it should be a great way to ensure that both the web adaptor and the site are operational. Since we are using chef to deploy and configure the web adaptor we have certain instances where the web adaptor either doesn't configure at all or it takes a few attempts to configure. During this configuration time or when it doesn't configure at all, any requests that go to https://server.domain.com/webadaptorname/ * will receive an ArcGIS error page indicating that no server machines have been configured with the web adaptor. When viewing this page as a user through a browser it is obvious that it is an error message, however the web adaptor simply sees a 200 response from the ArcGIS error page and marks the instance as healthy. This has resulted in users seeing the above error page as the instance is then put into production. If we just hit the 6443/rest/info/healthcheck we have the same problem of the instance being marked as healthy before the web adaptor has configured. While we have not yet seen a web adaptor fail in our cloud deployment we could envisage a situation where the web adaptor drops its configuration and starts to show the no server associated with this web adaptor but still being marked as healthy as the Esri error page returns a 200 error.

‎05-31-2021

What is the most appropriate health check configuration for ArcGIS Server when using an application load balancer in AWS? The default guidance from Esri (e.g. cfn scripts) is to use the 6443:/arcgis/rest/info/healthCheck endpoint. However this does not take into consideration the web adaptor or issues within the web adaptor / web server tier. Another option would be to use the same endpoint but from :443/webadaptorName/rest/info/healthCheck. However, even if the healthCheck endpoint returns a broken response it is still code 200 and healthy. What would be the best option? I was thinking an export request against sampleWorldCities.

‎03-25-2021

https://support.esri.com/en/technical-article/000012876

‎03-24-2021

Is there a whitepaper or set of documents on the built-in authorisation model of ArcGIS Enterprise? The various help sites and documents that outline authentication methods and how they work are more than sufficient but the authorisation component is a tad light. I am trying to document (in as much detail as possible) the various components and interactions that occur when a user accesses a secured ArcGIS Server service (federated, gis item shared to group). I could patch something together myself that outlines the various components, e.g. redirects, generateToken requests and esri_auth cookies. However, I would much rather use an authoritative reference directly from Esri.

‎03-23-2021

Your GIS architecture looks fine. However, we hope to disable the REST API web interface and Service Admin API if accessed externally. Is this achievable with the above setup? If you want this accessible internally but not externally then you will need to handle this via your external load balancer. Also, if removing the dedicated web adaptor tier and installing the 3 x web adaptor on the Portal Server as you would normally do, I can see the benefit of resource-saving. Is there any other benefit from doing that? Installing 3 x web adaptors onto the Portal VM is not normal. Typical deployments have the web adaptor installed on each components VM. In your architecture you would have the WA installed on the portal server, hosting and general server. The only consideration I would throw into the mix here is defining DNS alias' now. It's quite frustrating to remediate legacy data services that use old fully qualified domain names and not a more agile alias.

‎03-21-2021

1. It primarily depends on data and what privileges users have to publish data. For example, if you are expecting users to host imagery (raster) on the hosting server then you will need cater for that. Vector data is quite small and you can probably ignore handling this at scale. The tile cache data store can become quite big if you have significant 3D data holdings as well. If you deploy at 10.8.1 you can leverage a NAS or S3 for this though. 2. It is generally recommended to leave C drive for the OS. Install all software to the D drive. All locally hosted data should be on the E drive. This logical separation means that a windows patch (download, install, delete installer) doesn't cause the C drive to max out and then crash the GIS if they're installed to the same disk. Same for user data. My recommendation: C drive 100 GB D drive 150 GB E drive 250 GB. Depending on your internal business processes, extending the drives to meet user demand is trivial. You'll need some good monitoring thrown into the mix for this though.

‎03-02-2021

Use the python API. https://developers.arcgis.com/python/api-reference/arcgis.gis.server.html#service Specifically an edit operation against the GIS admin service object. You would parse back the exact same JSON properties with your edits to minInstancePerNode and maxInstancePerNode. https://developers.arcgis.com/python/guide/managing-your-gis-servers/#Administering-services Here is the section of the guide that introduces the object.

‎03-01-2021

Double check the LM when you run this script. You may be borrowing a license per multiprocess thread and hitting a cap.

‎02-28-2021

Are you using a single use license, pulling from a concurrent use license manager or via ArcGIS Online?

‎02-28-2021

Paraphrasing the FAQ: Open the ArcGIS Portal Directory and sign in with an administrator account. The URL is formatted https://webadaptorhost.domain.com/webadaptor/portaladmin. Click System - Indexer - Index Status. Refresh the page to obtain the latest status. Depending on the result of the index status: Navigate to System - Indexer - Reindex. Click the Mode drop-down list, and select Full. Leave all other settings to default. Click Reindex.

‎02-15-2021

I have been able to move a single-machine ArcGIS Enterprise deployment from one virtual machine to another using webgisDR. The SOP was pretty straight forward and the local hosts file change needed to be made before any software was installed on the new VM. To make your life easier, ensure your existing enterprise GIS is using a DNS alias across all configuration items that require a URL (where possible). Therefore any routing issues based on FQDN url (e.g. federated AGS service url) are mitigated. You should have a thorough look at the portal and server admin settings (federation values, web adaptor settings, etc) and change FQDN to the DNS alias or to the new FQDN. You can easily test your changes by removing the entry from the hosts file and accessing the system from a separate client.

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by AngusHooper1

Re: Shared services and persisting database locks

Re: Time Zone is incorrect when overwriting existing Feature Services

Shared services and persisting database locks

Re: Changing ArcGIS portal DNS alias post installation -

Re: ArcGIS Server - AWS NLB health check

ArcGIS Server - AWS NLB health check

Re: What causes the following Server Log: Unable to process request. java.io.IOException: Connection reset by peer

Enterprise built-in authorisation whitepaper or detailed breakdown?

Re: Best Practice for ArcGIS Enterprise Multi-Machine Deployment

Re: Best Practice for ArcGIS Enterprise Multi-Machine Deployment

Re: Does anyone have a batch script to change the pooling paramaters of all services in a AGS Enterprise folder?

Re: Arcpy Runtime Error The Product License has not been initialized

Re: Arcpy Runtime Error The Product License has not been initialized

Re: Portal members not displayed under Organization > Members

Re: Using webgis DR to recover Enterprise installation in the same machine with new machine name

Re: ten million rows of data in one service layer-...

Support non-web mercator projections for tours

Re: Publishing Tables to Portal - Best Practices Q...

Re: Query regarding planning Enterprise maintenanc...

Active-Active across sites