<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Add Layer to Map Service without Republishing? in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/add-layer-to-map-service-without-republishing/m-p/1213147#M34026</link>
    <description>&lt;P&gt;Clearly, I'm now aware of any of your licensing or IT constraints.&amp;nbsp; But, one of the ways that I've seen this tackled is to have two ArcGIS Servers.&amp;nbsp; Server A is live with the last release of data.&amp;nbsp; Server B is the release before.&amp;nbsp; When new data arrives, then Server B receives an updated Map Service with the new datasets.&amp;nbsp; A load balancer is then switched to Server B.&amp;nbsp; Server A then goes quiet until a new dataset comes in and the roles reverse again.&lt;/P&gt;&lt;P&gt;In this way, you never incur user downtime while republishing happens.&lt;/P&gt;&lt;P&gt;It's a reasonably advanced workflow, but I've seen it work to good effect.&lt;/P&gt;</description>
    <pubDate>Thu, 15 Sep 2022 20:48:53 GMT</pubDate>
    <dc:creator>Scott_Tansley</dc:creator>
    <dc:date>2022-09-15T20:48:53Z</dc:date>
    <item>
      <title>Add Layer to Map Service without Republishing?</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/add-layer-to-map-service-without-republishing/m-p/1213104#M34023</link>
      <description>&lt;P&gt;We host a map service with near-real-time satellite imagery. When we receive new image throughout the day, we currently use a script to add the .tif as a new layer and republish the service as quickly as possible.&lt;/P&gt;&lt;P&gt;However, this causes the service to come down briefly and this causes issues due to the high viewership of a web app using this service. Is there a way to add a layer to a map service without overwriting the service?&lt;/P&gt;&lt;P&gt;We need to retain the ability to click on and off layers, each with a name that contain timing information, so a mosaic dataset will not work for us, since it shows up as a single layer when hosted (unless someone knows how to split a mosaic dataset into layers within the AGOL environment).&lt;/P&gt;&lt;P&gt;We don't control the web app and thus have limited options post-publishing.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Sep 2022 19:38:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/add-layer-to-map-service-without-republishing/m-p/1213104#M34023</guid>
      <dc:creator>ojlarson</dc:creator>
      <dc:date>2022-09-15T19:38:31Z</dc:date>
    </item>
    <item>
      <title>Re: Add Layer to Map Service without Republishing?</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/add-layer-to-map-service-without-republishing/m-p/1213147#M34026</link>
      <description>&lt;P&gt;Clearly, I'm now aware of any of your licensing or IT constraints.&amp;nbsp; But, one of the ways that I've seen this tackled is to have two ArcGIS Servers.&amp;nbsp; Server A is live with the last release of data.&amp;nbsp; Server B is the release before.&amp;nbsp; When new data arrives, then Server B receives an updated Map Service with the new datasets.&amp;nbsp; A load balancer is then switched to Server B.&amp;nbsp; Server A then goes quiet until a new dataset comes in and the roles reverse again.&lt;/P&gt;&lt;P&gt;In this way, you never incur user downtime while republishing happens.&lt;/P&gt;&lt;P&gt;It's a reasonably advanced workflow, but I've seen it work to good effect.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Sep 2022 20:48:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/add-layer-to-map-service-without-republishing/m-p/1213147#M34026</guid>
      <dc:creator>Scott_Tansley</dc:creator>
      <dc:date>2022-09-15T20:48:53Z</dc:date>
    </item>
  </channel>
</rss>

