nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Best web publishing database

KathleenWallis

I need advice from anyone who has set up a successful workflow for publishing to webapp builder from a publish only environment. Here is my issue.

Our utility department wants to publish a webmap that has many layers and I am trying to establish the best publishing environment for the best map performance. The map I am publishing is for viewing only and will not be edited.

1. I have successfully mastered publishing to ArcGIS online from my SDE server - however the data is in a database
that is in state plane, not web Mercator.
2. I have successfully mastered publishing to ArcGIS online from a file geodatabase that sits on the C drive on my
server.
3. Most layers are edited every couple of days, so a cached or tiled map is out of the question.

I have done all the scale dependencies and using only ArcGIS online or ESRI optimized symbol but want to take it
to the next step by

1. Setting up a database where all map layers are re- projected into web Mercator so that the web service does not have
to re-project on the fly. This database will consist of only my published map layers instead of my entire LGIM
database.
2. Have that geodatabase be a file geodatabase on my server's C drive so that I am not having to hit the SQL server
the is continually being asked for queries by the daily editors.

So my questions are as follows.
1. Is it possible to synchronize these map service layers down from SDE to the file gdb on a weekly basis to that the data in the webmap reflects data that is not too stale. I am assuming setting up data replication will work?

2. Will the map service published from the file geodatabase reflect regular changes (updated attributes and additional
points and lines, but not changes in schema) without my mapservice having to be refreshed or restarted.

3. Is there any other performance measure I can take that has not been mentioned?

Thanks in your patience in reading all this.

Katy

Encontre mais publicações marcadas com

Accepted answers

BelkiyaErcan2

Hello Neil,

Thanks your comment. It's partly true. As a rule, recommended that you use an enterprise geodatabase to maintain the source data for your services. When you use a file geodatabase as a data source, you should place an identical copy of the file geodatabase on each GIS server machine or you have to make network sharing from map's source to every GIS server. If you copied your map's data source to your GIS servers, that minimizes network communication traffic among the different ArcGIS Server components and reduces I/O contention when accessing the file geodatabases. Factors that influence potential disk I/O contention for a shared file geodatabase include the number of layers in the map service, the nature of the data in the file geodatabase, and the file storage device. But an enterprise geodatabase offers high-availability support, backup and recovery, concurrency, scalability, and a tendency to provide superior throughput.

Regards,

All comments

Anonymous User

Started...
Suggestions/Answers are updated soon...

BelkiyaErcan2

Hello,

Maybe these links helps for your performance considerations.

Map authoring considerations—Help | ArcGIS for Desktop

Tuning and configuring services—Documentation | ArcGIS for Server

In generally, if your map is slow in ArcMap, then your service will be work slow after it published. Check the drawing performance for your map in ArcMap. Before you are publishing, check the drawing performance for your service in the Preview window.

Optimizing map content for performance—Help | ArcGIS for Desktop

Previewing your map—Documentation | ArcGIS for Server

For best performance with geodatabases, use enterprise geodatabases. Because an enterprise geodatabase faster than a file geodatabase.

Data storage considerations for an ArcGIS Server site—Documentation (10.4) | ArcGIS for Server

I hope that, these links useful for you.

Regards,

JakeSkinner

Hi Katy,

1. Is it possible to synchronize these map service layers down from SDE to the file gdb on a weekly basis to that the data in the webmap reflects data that is not too stale. I am assuming setting up data replication will work?

Yes, you will want to create a 1-way replica from your SDE to File Geodatabase.

Creating a one-way or two-way replica—ArcGIS Help | ArcGIS for Desktop

2. Will the map service published from the file geodatabase reflect regular changes (updated attributes and additional
points and lines, but not changes in schema) without my mapservice having to be refreshed or restarted.

Yes, edits that are synchronized from your SDE geodatabase will show immediately in your map service without having to refresh/restart the service. Also, if interested, you can have the schema update without having to stop the map service:

Disabling schema locking on a map service—Documentation (10.4) | ArcGIS for Server

3. Is there any other performance measure I can take that has not been mentioned?

I noticed you stated that you are going to reproject all of your data to Web Mercator. This won't be necessary, you can simply set the Data Frame coordinate system to Web Mercator.

Designing a map to overlay ArcGIS Online, Google Maps, or Bing Maps—Documentation | ArcGIS for Server

NeilAyres

"Because an enterprise geodatabase faster than a file geodatabase."

I don't think that this statement is true. If you don't need feature access (editing), use a fgdb as you have outlined.

BelkiyaErcan2

Hello Neil,

Regards,

Anonymous User

I need advice from anyone who has set up a successful workflow for publishing to webapp builder from a publish only environment. Here is my issue.

I have successfully mastered publishing to ArcGIS online from my SDE server - however the data is in a database
that is in state plane, not web Mercator.:

Its related to your projection system and in ArcGIS online on the fly its converted to WGS84 projection.
2. I have successfully mastered publishing to ArcGIS online from a file geodatabase that sits on the C drive on my server.

Slow performance of map services and in future faces rendering issue also system resources uses goes high. Please use enterprise database.

Most layers are edited every couple of days, so a cached or tiled map is out of the question.

Its needs frequently to update or create tiles which takes time and reconditions for tile map services use static data.

I have done all the scale dependencies and using only ArcGIS online or ESRI optimized symbol but want to take it to the next step by

1. Setting up a database where all map layers are re- projected into web Mercator so that the web service does not have to re-project on the fly. This database will consist of only my published map layers instead of my entire LGIM database.

True & correct

Have that geodatabase be a file geodatabase on my server's C drive so that I am not having to hit the SQL server the is continually being asked for queries by the daily editors.

So my questions are as follows.
1. Is it possible to synchronize these map service layers down from SDE to the file gdb on a weekly basis to that the data in the webmap reflects data that is not too stale. I am assuming setting up data replication will work?

No you can use versioning concept and reconcile each week work best in this case and more efficient.

2. Will the map service published from the file geodatabase reflect regular changes (updated attributes and additional
points and lines, but not changes in schema) without my mapservice having to be refreshed or restarted.

Use above option it’s not require refresh of map services

3. Is there any other performance measure I can take that has not been mentioned?

Use system monitor to measure error and other stuff.

You can also use ArcGIS server manager>Logs > statics to check uses and other details.

Thanks in your patience in reading all this.

Find all details ...

Please share if you require more info...

Anonymous User

https://community.esri.com/people/patel1684/blog/2016/08/17/the-best-practice-for-authoring-a-mxd

Check this also and share your findings..

KathleenWallis

Belkiya thank you for all of your help and the great reference links.
KATY

KathleenWallis

Thank you Jake for your reply, also thank you for the overlay link. I had been changing the data FRAME to WBAS ( Web Mercator . . . .)
but did not know if this was sufficient. Glad to know I dont' have to reproject. Matchiing the scales to AGOL or google maps is also a good
tip that I had forgotten about.
katy

Anonymous User

There seem to be two schools of thought... Folks from Esri Performance advised me to use a file gdb if the viewer is a read-only viewer, and store this file gdb on the web server. And in that case, I'd presume projecting to 3857 can only help performance. If the data frame is 3857 but the data is state plane it'll reproject on the fly and I presume incur a performance penalty. While maybe small, I'd rather just let the Replication also project the data weekly. I am about to make this our new workflow: replicate weekly from 10.51 SDE to FGDBs on another machine that's our web server and ArcGIS services server. I will say, services from our state plane SDE to viewers (hosted on a second machine) with heavy dynamic map services, are strained under load. The servers are very powerful. I am looking at all options to attack the bottlenecks. I will get Monitor installed, one of these days, once the system is deployed. I've aggressively set draw scales. I may look at webGL layers as well. They looked sweet in Dev Conf this year. My main choice now now is: SDE or FGDB. Thus far, I'm going FGDB; will come back at some point and weigh in on how it goes...

KathleenWallis

Kevin -

Thank you for your input. Please keep us posted as to how your results go.
Katy

Anonymous User

Sure thing Katy! I'm setting up a lot of SDE backend stuff still but will gather it to a comprehensive post after it's all done in a few weeks. One thing I've noticed already though, beware you set your datum transform before setting up a child replica to different coordinate system. For us, and perhaps with your group Katy, and many local govs, our SDE is in state plane. Which is appropriate, for our scale. For web viewers I want to convert to web mercator for speed. But be sure to set your data frame in that case to ITRF00 WGS84<>NAD83 conversion. If you don't, even if you go through the instructions in Create a replica in a different coordinate sys ... then at least for our area, I found it was NOT converting the datum and everything was off by 4 feet. When I selected this transform (as opposed to leaving at None, which it apparently defaults to) though, then it worked nicely. You set it in the properties of the Data Frame in the MXD containing the layers that you will then run this child replica workflow on. I imagine transforms matter even more in Cali with plate movement!

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.