Latest Contributions by JessicaViera-Atwell

We have a similar architecture at my utility.   Once you've done the initial export, you will need to set up a routine (via model builder or python, etc.) that runs nightly to update the data in your export.  We currently have Milsoft's data exported to an Esri file geodatabase nightly.  Once this process ends, we have an extension GeoEXT Import that runs on our ArcServer machine to import the delta changes made within the last 24 hours.  Our end result is a copy of our Milsoft data that then resides within an enterprise geodatabase (SQL 2012).  All services are published using this data and any data that must be maintained outside the Milsoft environment is also edited within the enterprise geodatabase.   With respect to symbology, dependent upon the type of symbology you are using, you should be able to create layer files and/or styles that match whatever you are using with your current .mxd.   Feel free to contact me if you have any questions regarding our current workflow processes for getting our data out of Milsoft and into an Esri geodatabase that we can use for publishing web services. ... View more