<?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 Changing ArcGIS Server v10.3.1 Cache Scales in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/changing-arcgis-server-v10-3-1-cache-scales/m-p/409104#M15817</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am in the process of changing scales on my basemap cached mapservices in AGS v10.3.1, but I am running into problems with tiles not showing up any more at some scales and the status getting corrupted.&amp;nbsp; This is the workflow that I intend to use:&lt;/P&gt;&lt;P&gt;1.) Use Manage Map Server Cache Scales to delete a scale and add a replacement scale in the same step&lt;/P&gt;&lt;P&gt;2.) Copy bundles from the same updated cache in test environment to appropriate folder in production environment(e.g. L02)&lt;/P&gt;&lt;P&gt;3.) Use Manage Map Server Cache Status to update the status for the copied bundles cache level&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would prefer to copy the bundles and update the Cache Status rather than build all the tiles as this process would take a fraction of the time.&amp;nbsp; Unfortunately as stated above some of the cache levels are not showing up.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone know of a better method than this to change cached service scales in a short period of time?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have been performing these updates in development and test environments where there is hardly a load on the cached mapservice.&amp;nbsp; Will I have issues when I try this same procedure in production where there could be a sizable load on the cached mapservice?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 06 Apr 2016 18:36:32 GMT</pubDate>
    <dc:creator>MichaelVolz</dc:creator>
    <dc:date>2016-04-06T18:36:32Z</dc:date>
    <item>
      <title>Changing ArcGIS Server v10.3.1 Cache Scales</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/changing-arcgis-server-v10-3-1-cache-scales/m-p/409104#M15817</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am in the process of changing scales on my basemap cached mapservices in AGS v10.3.1, but I am running into problems with tiles not showing up any more at some scales and the status getting corrupted.&amp;nbsp; This is the workflow that I intend to use:&lt;/P&gt;&lt;P&gt;1.) Use Manage Map Server Cache Scales to delete a scale and add a replacement scale in the same step&lt;/P&gt;&lt;P&gt;2.) Copy bundles from the same updated cache in test environment to appropriate folder in production environment(e.g. L02)&lt;/P&gt;&lt;P&gt;3.) Use Manage Map Server Cache Status to update the status for the copied bundles cache level&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would prefer to copy the bundles and update the Cache Status rather than build all the tiles as this process would take a fraction of the time.&amp;nbsp; Unfortunately as stated above some of the cache levels are not showing up.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone know of a better method than this to change cached service scales in a short period of time?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have been performing these updates in development and test environments where there is hardly a load on the cached mapservice.&amp;nbsp; Will I have issues when I try this same procedure in production where there could be a sizable load on the cached mapservice?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Apr 2016 18:36:32 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/changing-arcgis-server-v10-3-1-cache-scales/m-p/409104#M15817</guid>
      <dc:creator>MichaelVolz</dc:creator>
      <dc:date>2016-04-06T18:36:32Z</dc:date>
    </item>
  </channel>
</rss>

