POST
|
Thanks again Nikhil, this is exactly what I was looking for. As a tip to others experiencing this same issue, it should also be noted that using this method you must stick with port 6180. Trying to configure it to something else will not work by just changing this setting. Matthew Jones is also correct that an external endpoint must be opened (which I had done already through the Azure portal in this case). -Steve
... View more
04-09-2015
11:19 AM
|
0
|
0
|
725
|
POST
|
I've grown to appreciate the ArcGis Online MapViewer a great deal as a quick and easy tool for pulling together various layers from our ArcGIS development server into a single map. Recently in development we have been experimenting with the Stream Service layers created through the GeoProcessor Extension. Although the layers can be consumed as layers in MapViewer, some of the normal options that you get with a static layer are not available. There are two important features available to static layers that seem to be disabled for Stream Services. First is the ability to create a label for features. Here are the options for a Stream Service Layer As opposed to a static feature layer which has the "Create Labels" option. I cannot think of a reason that this should not be supported for Stream Services, so perhaps it was an oversight as I know the Stream Services are fairly new. Another great feature available to static layers that is not available to Stream Service Layers are the various ways to encode your data into the feature icons, such as using heat maps or a color scale. This can be seen in the difference between the "Change Style" screens of a static layer vs. a Stream Service. Stream Service: Static Layer: I understand the options here also depend on the type of Geometry being displayed, but even so the Stream Services are lacking in options. Now we could of course spin up some custom ArcGis API development to achieve our goals but it would be nice if this were doable via the MapViewer in the future. Thanks, -Steve
... View more
04-09-2015
10:54 AM
|
0
|
0
|
3537
|
POST
|
Matt, Thanks so much for your response, this seems to be exactly what I've been looking for. However, I cannot find system > properties in the admin site. On the "Services" tab where you land upon signing into the Arcgis Server manager (at http://localhost:6080/arcgis/manager/) there is a System button: But when I click that I do not see any properties option. Just what's pictured below. I also checked out the Site tab up top but have the following screen: Which has the System directory listed but I'm not sure this is what you were referring to. I guess part of my confusion is this was my first time setting up ArcGIS server in general so I'm not as familiar with the configuration layout. Any help in finding this WebSocket property would be much appreciated. Thanks again, Steve
... View more
04-09-2015
10:39 AM
|
0
|
2
|
725
|
POST
|
It's been a long couple of days trying to set up an ArcGis for Server development environment up in Azure. I've been able to get most things to work, however the primary nagging issue I'm still unable to resolve is that of the quirky FQDN resolution of Azure VMs (and ArcGis' dependence on them). A prior thread here Invalid redirect when logging in to Portal for ArcGIS 10.3 detailed the issue in the context of the Portal WebAdaptor. In this case, there was a work a round, as you can go in and edit the Web Adaptor setting manually to use the correct externally facing VM. The issue stems from the fact that Azure uses local FQDN's within each Cloud Service network, which all have the format of machinename.xx.internal.cloudapp.net. The real external FQDN is machinename.cloudapp.net - however this is hidden from the perspective of the local machine and is taken care of at some higher level in the network architecture (I am not a network expert unfortunately). After two attempts of trying to solve this issue with my own manual deployments - I decided to try the ArcGIS Server for Azure Technical Preview Unfortunately the issue remains. Below is a screenshow for the rest API call located at http://d-arcgis.cloudapp.net/arcgis/rest/services/TestStream/StreamServer (which is available over the net) but the websocket addresses at the bottom are still using the local DNS naming. If you were to click on ArcGis Javascript and look at the Javascript Console in Chrome, you would see my suspicions confirmed: Any insights on workarounds or other options for hosting a stream service in Azure? Thanks, Steve Kehoe
... View more
03-17-2015
02:48 PM
|
0
|
5
|
5277
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:25 AM
|