Release of the Deprecated Features Plan for ArcGIS 10.5.1

This blog post provides the latest updates regarding deprecated features in the recent release of ArcGIS 10.5.1.

With each release, Esri assesses and adjusts the products and functionality supported in the ArcGIS Platform based on customer needs and technological trends. The purpose of the Deprecated Features for ArcGIS document is to provide as much advanced notice as possible regarding these changes.

For more information on Esri’s plans for deprecating features, refer to the following PDF document, Deprecated Features for ArcGIS 10.5.1 (this deprecation plan is also available in the following technical article from the Esri Support Knowledge Base). The documentation linked above provides additional information about each note below, in addition to recommendations of alternative workflows and applications. Information from previous releases (10.4 and 10.5) is also included in the link above.

Here are some of the major changes in ArcGIS 10.5.1:

  • ArcGIS 10.5.1 is the last release to support Visual Studio 2013 for the ArcObjects SDK.
  • In the near future, the cluster functionality in the ArcGIS Server component of ArcGIS Enterprise will be deprecated. Instead, it is recommended to create separate ArcGIS Server sites where multiple clusters would have been used previously.
  • ArcGIS Enterprise 10.5.1 will stop bundling the portalpy module in favor of the ArcGIS API for Python. No further development is planned for this module.
  • ArcGIS 10.5.1 will be the last release to support the PostgreSQL 9.3.x series of releases, DB2 versions 9.7 and 10.1, and the ST_Raster data type for Oracle, SQL Server, and PostgreSQL.
  • ArcGIS 10.5.1 is the last release to support anything other than the Data Store product as a data store for a Hosting Server.

Note: The deprecation of cluster functionality does not affect the ability to create multi-machine sites. ArcGIS Server sites with multiple machines continue to be fully supported.


Gregory L. – Online Support Resources

This entry was posted in Announcements, ArcGIS Desktop, ArcGIS Enterprise, export, SDK and tagged , , , , , , , , , , , . Bookmark the permalink.

Leave a Reply

5 Comments

  1. xlhomme says:

    Hi , I’ve got an Portal 10.5 with a hosing server. In this hosting server I’ve referenced an egdb ( postgres ) datasource . I’m able to publish weblayer from ArcGIS Pro to portal with referenced data already stored in my egdb ( postgres ) datasource.

    If ArcGIS 10.5.1 is the last release to support anything other than the Data Store product as a data store for a Hosting Server. How could we publish referenced data with ArcGIS Pro ?
    ArcGIS Pro could publish only to a portal ans is not able to publish in a federated server which is not the hosting server !

    best regards

    • Thomas Edghill says:

      Thanks for submitting this comment. In 10.5.1, it is still possible to register enterprise geodatabases such as Postgres with ArcGIS Server, and proceed with the workflow you have described: publishing layers from ArcGIS Pro to the portal which is still referencing data located in your registered database. In fact, we promote this workflow as a great way to work with your data, as the styles defined in ArcGIS Pro will be retained when viewing the published content on the portal.

      The mention of “Hosting Server” above refers to the act of registering a database as ArcGIS Server’s managed database. When a server has a managed database, it can be configured in the Organization settings of Portal for ArcGIS as the Hosting Server for the portal.
      (Reference: http://server.arcgis.com/en/server/latest/administer/windows/configure-hosting-server-for-portal.htm)

      Once a hosting server is set for the Portal, when publishing from ArcGIS Pro, you will be able to select the “Copy all data” button instead of the “Reference registered data” button. With “Copy all data” selected, a copy of the underlying data for your layers will be placed in the managed database.
      (Reference: http://pro.arcgis.com/en/pro-app/help/sharing/overview/web-feature-layer.htm)

      This blog states that at 10.5.1, it will only be possible to set the ArcGIS Data Store product as the managed database for ArcGIS Server, but it will still be possible to register enterprise geodatabases for the purpose of using them as data sources for your published content when selecting the “Reference registered data” option when sharing from Pro.

      In your scenario, you should be able to retain your Postgres databases as a registered enterprise geodatabase, and then additionally configure the ArcGIS Data Store to be the registered managed database. Once the ArcGIS Data Store is configured and your ArcGIS Server is listed as the hosting server, you should be able to publish from ArcGIS Pro as you are currently doing. I hope this helps!

      • xlhomme says:

        Hi
        thanks!
        I better understand now the difference between a managed database and a database. And It’s deprecated to use something else than the ArcGIS datastore as a manager database for the hosting server.

        But when you say “when publishing from ArcGIS Pro, you will be able to select the “Copy all data” button instead of the “Reference registered data” button. With “Copy all data” selected, a copy of the underlying data for your layers will be placed in the managed database.” After checking on the arcgis server (10.5), the copyed data are stored in a GDB file but not in the ArcGIS DataStore. The only way I found to store the data in the arcgis data store is when you import some data from the “add data from my computer” in the content panel of portal .

        • Thomas Edghill says:

          I’m happy to help clarify!

          I believe I know the situation you are referring to – when you choose “Copy all data” when sharing a layer that is of the “Map Image” type, then ArcGIS Server does what you are referring to.
          (Source on Map Image Layers: http://pro.arcgis.com/en/pro-app/help/sharing/overview/map-image-layer.htm)

          If you are choosing “Copy all data” when sharing a layer that is of the “Feature” type, then you will be publishing a web feature layer, the equivalent of a Feature Service, and the data is copied into the ArcGIS Data Store – you should be able to find the Feature Layer in the “Hosted” folder in ArcGIS Server Manager, and in the Item Description on Portal for ArcGIS, the layer should be listed as “Feature Layer (Hosted)”.