Help a newbie decide how to set up Server

[AdrianWelsh]

I have never been on the back end of setting up a server for the first time and now I find myself working for a small company that is just getting its feet wet with GIS. The issue is, I am not sure where to start and not sure if I should consult the GeoNet or my local Esri rep.

There seems to be so many options out there and I want to make sure I get things setup right initially. We do not have a real dedicated server machine in our building so we are looking at options on this (like do we outsource and use something like Amazon web services, do we dedicate a local machine in-house, etc.). My company has a standard ArcGIS Server Workgroup license (with two cores, whatever that means). We will be wanting to host data on our ArcGIS Online site and will want to be able to update that data regularly. We will also want some secure services and things like that (and we are in the US).

We do not have a back-end relational database but I believe we are working towards getting one on PostgreSQL, from what I understand. Our website has a MySQL component that could work, I suppose, but then again, I am unfamiliar with configuring these types of relational databases (though, I would love to learn).

Ok GeoNet, the question is, where is the best place for me to start? How should I best approach this to get the most value and functionality? Are options like ArcGIS for Portal or an SDE likely possibilities for me?

Thanks!

[AdrianWelsh]

Brian,

I appreciate and and all comments/suggestions/advice. So we may not know all the directions we are going but we do know some things that would help us where we are right now and that's where we suspect Server is the right approach (at least, I think that's the correct path).

We will be wanting to post a lot of data to AGOL and we will want to be able to update that data on a somewhat regular basis. It would be ideal if the updates could come from desktop ArcGIS or from AGOL (and therefore update each other, if that makes sense). I presume that is one advantage of having Server. I am not too concerned about the credits for the moment (and we do have the regular beginning allotment of credits).

As for the secure services, maybe this is not the best approach. Maybe I need to just think about having named users in my organization that are allowed access to a 'group' of maps in my content that only the group can see (and these would not be public groups, per se).

What my users would like to do is, update web maps and have those updates reflected on the desktop/server end (and vice versa). I do not like the wasted efficiency in having to make updates in both places since there is a high chance of error.

In any case, I really appreciate the advice as this is getting me further along in the decision-making process (though things are still cloudy!).

Thanks,

Adrian

EDITED to add: yes, the labels... Labels have 'improved' in AGOL but are still virtually useless unless you have something super simple and no one cares about style. In this world, no one wants super simple anymore...

[MarkYerington]

Adrian

I think you are on the right track as far as what you are thinking.  If you want to be able to edit through desktop you will edit the database directly through a database connection and ArcGIS online the best solution for you would be hosting your own service and re-direct this out through ArcGIS online as a feature service in some sort of web map that you want to create for editing.   This way all of the data is stored locally and updates automatically show up at all points.  The other option would be to publish everything to AGO turning on feature access and Map Tile for the service this way you will have a map service and feature service.  The only problem with this is your Desktop edits will be downloading from AGO and then you will push back out which is not as dynamic as the locally hosted server.  Remember to shut off cache automatically!!!!!!!

One thing to think about is if your internal server will be exposed to the web, if not you will have to make sure that anyone that wants to see your service through ArcGIS online or Desktop for ArcGIS is connected to your domain "Local Network".  The only way around this is if your organization has some sort of VPN client that allows external networks entrance into your domain if they are an authenticated user.

When you publish a service you will activate capabilities for Mapping and Feature Access. This will create a rest endpoint for both a Map Service and a Feature Service.  If the feature service does not support the symbology and labels that you like publish 2 services pointing back to the same data source one for feature access and one as just a map service.  The feature service will be what you will use in ArcGIS online to do your edits, but you could add both the feature and the map service to the same web map so the symbology/ labels show correct, and the feature service I would make 100% transparent.  This way it looks like you want, but your web interaction is actually with a feature service layer sitting on top of your map service.  These services are added to an arcgis online or any application through the rest endpoint that is created when the server is installed.

http://machinename/arcgis/rest/services/FolderName(if one exists on your server/servicename/MapServer

http://machinename/arcgis/rest/services/FolderName(if one exists on your server/servicename/FeatureServer

In ArcGIS online you will add them through "Add Item" "From Web"  The urls above will be what you add if you want to add your services to a web map.

You can control security on your server through built in stores or use your windows logins.

I would suggest standing this up on your local machine with (sql express that is free and shipped with your workgroup license) for you to test and mess around with.  If you are going to be the one managing the site there is no reason to not make use of your license just to get an idea of how things work.  There are a lot of moving parts in an enterprise system so the more hands on you are the more comfortable you will feel in the long run.  No sense in waiting around for the justification of a server if the software is just sitting around collecting dust.  The only way you will justify is if you can model workflows and the power of the system in a small scale deployment.

The first thing I would try and justify is a course through esri on Server.  If not hopefully some of my commentary above will get you going.

Good Luck!!