Книга: Getting to Know ArcGIS Enterprise
Назад: Chapter 19: Patching ArcGIS Enterprise
Дальше: Conclusion

Chapter 20Upgrading ArcGIS Enterprise

Objectives

Introduction

Every new version of ArcGIS Enterprise brings changes to the capabilities of the system. In this chapter, you will learn the concepts and processes you need to upgrade to a new version.

Why upgrade?

The first question you need to answer is whether you should upgrade at all. It is not a good idea to upgrade just because a new version of the software has been released. You want to carefully consider the benefits that a new version would offer, and upgrade if it makes sense for your organization.

New capabilities

The obvious reason to upgrade is that your organization has needs that aren’t met by your current version of ArcGIS Enterprise but that would be met by some new capability available with a newer version. For example, an organization may need to audit changes made to the properties of hosted feature services. By upgrading to ArcGIS Enterprise 11.5 or later, the organization can use the built-in audit logging capability of ArcGIS Server to meet this need.

To effectively take advantage of new capabilities, you need to be aware of your organization’s evolving business needs. It may be the case that the capabilities of your current version met the needs you had in the past but are no longer adequate to the task because of changes in your needs. Regularly evaluate your business needs and compare them against the capabilities offered by your version of ArcGIS Enterprise.

In addition to your own changing needs, you need to stay current on the changing capabilities of ArcGIS Enterprise. Esri communicates those changes in blog posts, emails, and documentation pages for each version. Review the new capabilities to see whether they provide the functionality that your organization requires but that has not been previously available.

The ArcGIS Enterprise product life cycle

You also need to be aware of the life cycle for a version of ArcGIS Enterprise. As time passes since the original release of a version, it will go through different levels of support:

It is best practice to make sure that your version of ArcGIS Enterprise is still receiving updates and patches. For that reason, you want to avoid falling into mature or retired status. Esri publishes the product life cycle for each version, and you should know when your version is scheduled to go into mature support.

Versions of ArcGIS Enterprise alternate between short-term and long-term support releases. A short-term support release will be in general availability for about 18 months, whereas a long-term support release will be in general availability for about two years. Only long-term support releases have extended support, which lasts for roughly another two years. Short-term support releases go directly to mature status after the period for general availability. For that reason, if you need to stay on a single version of ArcGIS Enterprise for an extended period of time, you should choose a long-term support release.

Bug fixes

Even if your version of ArcGIS Enterprise has the GIS capabilities to meet all your business needs, it may have software defects that affect its usability. Later versions may fix those defects, and those fixes might not be available as patches for your current version. In addition to reviewing the new capabilities of each version, check the list of bug fixes to see if a new version would address software defects that could affect your deployment.

These bug fixes can include addressing security vulnerabilities, which makes them particularly important to implement. If the vulnerability is not fixed in a patch for your version, your organization’s security policies may require that you upgrade ArcGIS Enterprise to address the vulnerability.

.
  • Log on to each of the machines that are running ArcGIS Enterprise components (Portal for ArcGIS, ArcGIS Server, ArcGIS Data Store, ArcGIS Web Adaptors) and answer the following questions:
  • Review what’s new in the documentation

    Every new release, Esri publishes documentation that describes new capabilities and documents any deprecated or retired capabilities. The What’s new documentation is a good resource to summarize the differences between software versions.

    1. Navigate to the ArcGIS Enterprise documentation page at and click the What’s new link to view the documentation for the latest version.
    2. Review the new features for the latest version of ArcGIS Enterprise. Make sure you follow any links for more information about what’s new in each component of ArcGIS Enterprise you have in your deployment.
    3. At the top of the page, click Other versions to open the version drop-down list. Review what’s new for every version between your current version and the latest version.
      • What business needs does your organization have that aren’t currently met by your version of ArcGIS Enterprise? .
      • Scroll down to the ArcGIS Pro and ArcGIS Enterprise compatibility section.
        • Which version of ArcGIS Pro has a compatible geoprocessing environment to the version of ArcGIS Enterprise you are considering upgrading to?
        • If users need to upgrade ArcGIS Pro, how will you communicate that need to them?

    Take the next step

    If it’s appropriate for your circumstances, upgrade your deployment. We strongly recommend you create a backup and test the upgrade in a staging environment before upgrading.

    Summary

    In this chapter, you learned the process for upgrading ArcGIS Enterprise to a new version. Because each version of ArcGIS Enterprise will eventually go into mature support and later be retired, you will eventually need to upgrade. But you should think carefully about when and why you upgrade and be aware of the prerequisites you need to perform first.

    Because it can’t be said enough: Make a backup, verify your restore procedures are working and up-to-date, and test your upgrade process before you upgrade your production environment.

    Назад: Chapter 19: Patching ArcGIS Enterprise
    Дальше: Conclusion