POST
|
I've created a custom geoprocessing tool from a Python script that uses feature layers hosted on our Portal as inputs. The tool runs without issue when the local version is used, but when I publish the tool to Portal and try to use the hosted version in Pro or Portal it says it can't access the feature layer. The feature layer is shared with our organization and the tool is currently private, but the account I'm using in Pro and Portal owns both. The layers and Portal both use HTTPS. Has anyone ever come across this issue before? I'm at a loss on where to begin to troubleshoot it. I don't think the issue is with the script itself because it runs fine with the exact same inputs before the tool is published. Thank you!
... View more
09-17-2020
09:50 AM
|
0
|
2
|
668
|
POST
|
Hello, I've been experimenting with publishing our layers from Pro (Version 2.2.1), and I noticed that the layers don't appear in the thumbnails when I publish. Only the basemap is visible. This is true whether I try to add a thumbnail image to the the metadata, or just let the layer publish without setting a thumbnail first. They all look like this: Has anyone else had this issue?
... View more
10-09-2018
05:05 PM
|
0
|
1
|
734
|
POST
|
Unfortunately, no. From the document you linked, in the syntax table: "Tiling scheme from an existing vector tile service will be used. Only tiling schemes with scales that double in progression through levels and have 512-by-512 tile size are supported." Regardless of whether you use an index or flat tile generation, it wants the scales to double.
... View more
04-10-2018
07:54 AM
|
0
|
0
|
517
|
POST
|
My organization has developed a custom tiling scheme, because our layers cover a fairly small area and our users complained there weren't enough scale levels in the areas they wanted to see. Since the custom scheme increments by less than double the previous value, we can't use it for vector tile layers. Why do the levels need to double for vector tile layers, but not raster based caches? Is it for technical reasons, or optimization? Is there any way to override this?
... View more
04-09-2018
04:42 PM
|
0
|
3
|
848
|
POST
|
I've installed several web adaptors now, and I keep running into this paradox: 1) When you install the web adaptor, the help documentation states "By default, administration of the site through ArcGIS Web Adaptor is disabled. This is the recommended option." I am assuming that's because of some sort of security risk, like the one described here? 2) However, if you want to make your services publishable through the web adaptor, as far as I know the only way to do that is to enable administration of the site through the web adaptor. In fact there's a help document that recommends you disable access through port 6080 and only use the web adaptor URL: Disabling administrative access to ArcGIS Server on port 6080—ArcGIS Server Administration (Windows) | ArcGIS Enterprise So my question is, what actually is the best practice for server administration through web adaptor? Does anyone have any insights on this? Does it depend on your server setup? If both methods have security risks, which is the least problematic? In our case, we have services that need to be kept inside the network, and services that need to be fully accessible for the public.
... View more
08-03-2017
05:18 PM
|
1
|
3
|
5279
|
Title | Kudos | Posted |
---|---|---|
1 | 08-03-2017 05:18 PM |
Online Status |
Offline
|
Date Last Visited |
11-24-2021
06:45 PM
|