<?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: Best Practices for publishing services on hosting server in Publishing and Managing Services Questions</title>
    <link>https://community.esri.com/t5/publishing-and-managing-services-questions/best-practices-for-publishing-services-on-hosting/m-p/1186208#M755</link>
    <description>&lt;P&gt;I will give the classic "It depends" answer. There is no problem with having both types of services published to the same GIS Server Site. I have a Site doing the same, as well as a site with strictly non-hosted services. Where it depends is the architecture of your specific GIS Site and the services being published there. How many machines are in your site? How much RAM and CPU resources do your servers have? Is the Data store installed on the same server? How many/what type of services are running and what kind of demand do they have? Are you utilizing Shared instances?&lt;/P&gt;&lt;P&gt;You can have hosted and user-managed data-based services on the same GIS Server Site, however just like any other environment it will require capacity planning, monitoring and adjusting to make sure the services are performing at the highest level possible.&lt;/P&gt;</description>
    <pubDate>Fri, 24 Jun 2022 18:49:55 GMT</pubDate>
    <dc:creator>TonyContreras_Frisco_TX</dc:creator>
    <dc:date>2022-06-24T18:49:55Z</dc:date>
    <item>
      <title>Best Practices for publishing services on hosting server</title>
      <link>https://community.esri.com/t5/publishing-and-managing-services-questions/best-practices-for-publishing-services-on-hosting/m-p/1185441#M753</link>
      <description>&lt;P&gt;Are there any specific recommendations for managing an ArcGIS Server in the Hosting role for ArcGIS Enterprise? More specifically, I'm wondering if it is discouraged to publish non-hosted services on this server. Is there any disadvantage to have a mixture of hosted and user-managed data source services on the same box?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jun 2022 12:42:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/publishing-and-managing-services-questions/best-practices-for-publishing-services-on-hosting/m-p/1185441#M753</guid>
      <dc:creator>HeatherM_JDI</dc:creator>
      <dc:date>2022-06-23T12:42:40Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practices for publishing services on hosting server</title>
      <link>https://community.esri.com/t5/publishing-and-managing-services-questions/best-practices-for-publishing-services-on-hosting/m-p/1186208#M755</link>
      <description>&lt;P&gt;I will give the classic "It depends" answer. There is no problem with having both types of services published to the same GIS Server Site. I have a Site doing the same, as well as a site with strictly non-hosted services. Where it depends is the architecture of your specific GIS Site and the services being published there. How many machines are in your site? How much RAM and CPU resources do your servers have? Is the Data store installed on the same server? How many/what type of services are running and what kind of demand do they have? Are you utilizing Shared instances?&lt;/P&gt;&lt;P&gt;You can have hosted and user-managed data-based services on the same GIS Server Site, however just like any other environment it will require capacity planning, monitoring and adjusting to make sure the services are performing at the highest level possible.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jun 2022 18:49:55 GMT</pubDate>
      <guid>https://community.esri.com/t5/publishing-and-managing-services-questions/best-practices-for-publishing-services-on-hosting/m-p/1186208#M755</guid>
      <dc:creator>TonyContreras_Frisco_TX</dc:creator>
      <dc:date>2022-06-24T18:49:55Z</dc:date>
    </item>
  </channel>
</rss>

