Latest Contributions by JYI

‎01-20-2023

This is the final solution - after gone through a lot of pains, and gains of course. 1. In ArcGIS Pro 2.9, create a Script tool, to publish .geojson file to a standalone ArcGIS Server, or Portal. Lessons learned: a. Cannot use ArcGIS Pro 3.0. The versions between ArcGIS Pro and enterprise Portal much match. Thanks to ESRI Tech support for this point. Reference. b. Must have a standalone ArcGIS Server deployed in the enterprise Portal platform. Reference. c. Must use .zip files as input files, as .geojson file, .ags file, .lyrx, .aprx files are not recognized when running the web tool published to Portal. However, if you publish a Geoprocessing Service to the standalone server, then this is unnecessary, after you add MIME type to the web.config. d. Be careful with the env. settings. The script runs inside ArcGIS Pro, does not guarantee that it runs in the Portal web tool too. Usually the error is caused by the file path that inaccessible. Reference. e. For the map service symbology settings, the final solution is here, a workaround solution, due to Bug-000117445, f. The parameter Data types used is "File" for the zipped files, from the Script -> Tool Properties in ArcGIS Pro. 2. Once the Geoprocessing service is successfully published to Portal, or to standalone server, call the services from Databricks, or a regular Python env. outside of ArcGIS env. Lessons learned: a. File upload procedure is not included in the Geoprocessing service. This, however is not stated anywhere. When using arcgis.geoprocessing.DataFile, it always complains that the required DataFile parameter "does not exist or is not supported". Thanks to ESRI Support, that this is because the required files are not on the standalone server yet. b. Do not want to call the "uploads ArcGIS REST API" to upload the 60MB files, before running the Geoprocessing service, as there will be performance issue. Use self hosted Integration Runtime to hoop up the data lake data with the Portal web server VM, such that user can access the data through a url. References: 1, and 2. c. Calling the Geoprocessing service is straight forward. References: 1 and 2. d. This Creating and Using Web Tools and Geoprocessing Services video is very helpful.

‎12-15-2022

I would publish a geoprocessing service with the tool https://pro.arcgis.com/en/pro-app/latest/help/sharing/overview/publish-a-map-image-layer-from-a-hosted-feature-layer.htm#GUID-F8D58FC1-EE75-445D-A3A2-3E3EB202F728 Then in Databricks, call the rest service to publish the hosted feature layer as an image layer. Update: it turns out that there is no this arcpy function available for this tool at this moment.

‎12-15-2022

Hi, I am looking for the ArcGIS Python API to publish a hosted map image layer from a web feature layer, https://pro.arcgis.com/en/pro-app/latest/help/sharing/overview/publish-a-map-image-layer-from-a-hosted-feature-layer.htm#GUID-F8D58FC1-EE75-445D-A3A2-3E3EB202F728 The reason is that the client found the hosted line feature layers have serious performance issues with huge number of polylines, in their dashboards. The hosted feature layers are published from Databricks using ArcGIS Python API. They are looking for a way to publish the features to a hosted image layer instead, using ArcGIS API for Python. The data is located in data lake, i.e., there is no way to use relational database like PostgreSQL. If a direct way exists, that is ideal. Otherwise, a workaround would work. Thanks. Update: the final solution is publishing a map service to a standalone ArcGIS Server, instead of the hosted map service in Portal. Code.

‎11-16-2022

Thanks @DanWade. 1) If looking at the WFS getFeature url from a browser directly, the result is at the format of GeoJson. So we used "Poll an External Website for GeoJSON" as the input connector. 2) I contacted the WFS service owner, and no explanation so far. 3) Without "&count=20000", or with the count value bigger than 20000, the GeoEvent Server shows an error in the log saying "the data gets lost, due to unable to process that big workload", something like that. After almost 3 days' digging, yes, I believe that the paging function is removed by the WFS service provider, and that caused the original settings suddenly stopped working. The final workaround is that I divided the original one Input and one GeoEvent service to 10 Inputs and GeoEvent Services, respectively, by using the paramters like "...&count=20000&startIndex=0&sortBy=received_date_time+D", "...&count=20000&startIndex=20000&sortBy=received_date_time+D", "...&count=20000&startIndex=40000&sortBy=received_date_time+D", ...... "...&count=20000&startIndex=180000&sortBy=received_date_time+D". The polling rate is now changed to 4-5 minutes, instead of 15 seconds before. It works well.

‎11-15-2022

Hi @DanWade I am using GeoEvent Server and having a question with a WFS service which say has 200k records . I have to attach the count parameter in the WFS service url, like ...&count=20000&... However, in the past, this works well, I poll the data every 15 seconds from the WFS service, and I can get almost all the data and put them in a spatial temporal big data store. The GeoEvent Input connector is "Poll an External Website for GeoJSON", and the output is "Update a Feature in a Spatiotemporal Big Data Store". Now I found in every poll (every 15 seconds), I only get the same set of records, I.e., it is always those 20000 records... Is it possible that I fix this from the GeoEvent server side? Thanks.

‎06-18-2022

Same post: We just found that in our PROD enterprise Portal 10.9.1, which is deployed on Azure, with Windows 2022 VMs, we have serious WebGL issues with our dashboard, where, the error is like "Too many active WebGL contexts. Oldest context will be lost." Our dashboard has 26 web maps, which are all changed to use the Topographic raster basemap. I attached one screenshot with browser MS Edge, from one of the enterprise Portal Azure VMs. The web maps are loaded randomly when navigating the tabs, e.g., one web map does not load 2 seconds ago now gets loaded this time. The same dashboard works well in our 10.7.1 enterprise Portal on Azure though. Do you have any suggestion how to resolve the issue? Thanks.

‎06-18-2022

Hi @MikeMinami We just found that in our PROD enterprise Portal 10.9.1, which is deployed on Azure, with Windows 2022 VMs, we have serious WebGL issues with our dashboard, where, the error is like "Too many active WebGL contexts. Oldest context will be lost." Our dashboard has 26 web maps, which are all changed to use the Topographic raster basemap. I attached one screenshot with browser MS Edge, from one of the enterprise Portal Azure VMs. The web maps are loaded randomly when navigating the tabs, e.g., one web map does not load 2 seconds ago now gets loaded this time. The same dashboard works well in our 10.7.1 enterprise Portal on Azure though. Do you have any suggestion how to resolve the issue? Thanks.

‎02-25-2022

Solution is in the comments part of this link

‎02-25-2022

I am on 10.9.1 GeoEvent Server, and we are experiencing similar issue with TCP socket. That is the only blank page we got. Any solutions? Thanks.

‎12-14-2021

It is being said "Jan 11th, 2022 ". Fingers crossed.

‎12-14-2021

ESRI support just sent me the document which is available in December only, entitled "ArcGIS Enterprise Web Application Filter Rules". It says "This is required reading if you are implementing a WAF." To us, "OWASP Core Ruleset Guidance" is the most important part that we have been waiting for, although Azure team is not happy with so many rules that need to be disabled. 🙂 It also says "do not distribute or post publicly" so ask ESRI support for it.

‎12-14-2021

Our final solution is, change the admin url in the federated server to the external arcgis server url, not using the web adaptor url anymore. The change was safe to do, see here. Adding subject alternative DNS name of the web adaptor domain to the wild card certificate was turned down by IT for the security reason.

‎12-13-2021

The problem gets fixed. Will update back with the final solution once the 10.9.1 gets deployed onto the new DEV/STG/PROD successfully. For the two issues: 1. So far, Azure team disabled a rule, "Remote Command Execution: Windows PowerShell Command Found", from WAF security policy OWASP 3.0. Once this is done, no 403 forbidden error anymore, and portal 10.9.1 is accessible from a company desktop browser which is outside of Azure network. This may not be the best way and a customized rule may be required to setup for enterprise 10.9.1 only. Update: there is a technical doc entitled "ArcGIS Enterprise Web Application Filter Rules", which you can get from ESRI tech support. This is required reading if you are implementing a WAF. 2. For the WebContextURL cannot be modified issue, where both WebContextURL value and privatePortalURL value are the web adaptor url and cannot be changed: the workaround is denying the write capability to ...\ArcGIS\Portal\framework\etc\portal-config.properties file, once the WebContextURL value (should be the external portal url) and privatePortalURL value (should be the internal portal url with 7443 port ) are properly setup, same as in the older version like 10.6.1-10.8.1. But the question is, is this still required with #1 fixed? Will update back once this is confirmed. Update: Yes, the #2 issue must be fixed. The final solution is shown here, the first step. Many thanks to ESRI Inc. DSC group.

‎12-09-2021

Thanks again, @BillFox . We did more testing: 1. Double checked that the current network settings for dev are exactly the same as the other two env. STG and PROD (10.7.1). It is only the private ip address of the web adaptor VM listed. There is no public IP address (or a separate IP, in your word). 2. I scraped 10.9.1 again, and deployed 10.9 enterprise onto the 4 VMs manually, 10.9 Portal worked well from an Azure VM browser, as well as from a local desktop browser outside of Azure env., as expected. 3. After upgrading from 10.9 to 10.9.1, again, from an Azure VM browser, everything works well. When accessing the Portal from the company desktop, the problems come back exactly the same as before - no matter how many times I change the WebContextURL from https://devgis.azurevm.ca/portal to https://gis.ca/portal, it will change back to the internal link. and a lot 403 forbidden errors. It appears that the new stuff in the version 10.9.1 has caused the weird behaviors. I attached a screenshot of some 403 forbidden errors: How will the Azure team handle those exceptions, not filter them out, I may not be using the correct words here, I think new WAF policy or profile may be required? How can we get that info? Thanks.

‎12-09-2021

Hi @BillFox . Thanks. Yes, "gis.ca" is the DNS alias of devgis.azurevm.ca. devgis.azurevm.ca is our web adaptor on Azure VM, and can only be accessed on Azure VMs. While gis.ca is the external url for all the company users to access Portal on their company desktops outside of Azure network. We do not have Reverse/Forward proxies.

Online Status	Offline
Date Last Visited	‎07-10-2023 04:04 PM

My Ideas

Latest Contributions by JYI

Re: How to publish features as a hosted image layer using ArcGIS API for Python

Re: How to publish features as a hosted image layer using ArcGIS API for Python

How to publish features as a hosted image layer using ArcGIS API for Python

Re: Working with XML Data Structures and Polling WFS Services in ArcGIS GeoEvent Server

Re: Working with XML Data Structures and Polling WFS Services in ArcGIS GeoEvent Server

Dashboards in enterprise 10.9.1: "Too many active WebGL contexts. Oldest context will be lost."

Re: WebGL Contexts Error

Re: GeoEvent input/output creation page is blank

Re: GeoEvent input/output creation page is blank

Re: When will Portal for ArcGIS Help Language Pack be available for 10.9.1

Re: Azure App Gateway WAF ruleset

Re: ArcGIS Portal Error: Unable to load URL status 500 white changing feature hosted layer settings

Re: Enterprise 10.9.1 deployment issues on Azure Cloud

Re: Enterprise 10.9.1 deployment issues on Azure Cloud

Re: Enterprise 10.9.1 deployment issues on Azure Cloud

Dashboards in enterprise 10.9.1: "Too many active ...

Re: Azure App Gateway WAF ruleset

Re: Azure App Gateway WAF ruleset

Re: Signout portal from web app builder app

Re: High availability Portal/Server in Azure with ...