Skip to content
URL:
https://<root>/system/upgrades/importManifest
Methods:
POST
Version Introduced:
10.9.1

Access requirements

Required privileges

The Enterprise Administrator API requires privilege-based access. An administrator must be assigned a specific user privilege, or role, to access any given endpoint. Listed below are the user privileges or roles an administrator can be assigned that provides access to this endpoint. If multiple privileges are listed, only one needs to be assigned to gain access.


Tokens

This API requires token-based authentication. A token is automatically generated for administrators who sign in to the Enterprise Administrator API directory's HTML interface. Tokens generated in this way are stored for the entirety of the session.

Those accessing the API directory outside of the HTML interface will need to acquire a session token from the generateToken operation in the Enterprise Directory API. For security reasons, all POST requests made to the Enterprise Administrator API must include a token in the request body.


Learn how to generate a token

Description

The importManifest operation allows organization administrators to import the version manifest into a disconnected environment that can be used to discover available updates and releases and upgrade an ArcGIS Enterprise on Kubernetes deployment. The version manifest must be downloaded from My Esri, which requires an initial internet connection.

Request parameters

ParameterDetails

manifestFile

The file containing the version manifest (.dat file), used to discover available updates or releases for an ArcGIS Enterprise on Kubernetes deployment.

f

The response format. The default format is html.

Values: html | json | pjson

Example usage

The following is a sample POST request for the importManifest operation:

Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
POST /<context>/admin/system/upgrades/importManifest HTTP/1.1
Host: organization.example.com
Content-Type: multipart/form-data; boundary=------boundary

------boundary
Content-Disposition: form-data; name="manifestFile"; filename=""
Content-Type: application/octet-stream

versionManifest.dat
------boundary
Content-Disposition: form-data; name="f"

pjson
------boundary
Content-Disposition: form-data; name="token"

ycIwQVgej6UA_ZHHgltGsXCLRP815k4nLCiNyQEqGfWztsccgK5XdTEellUjToKS3D2UoHxGDPff4OblGKwRsXA0eb1kIIei4Bi-Ke20Nw-NSZR8Z7ILCDoxqbmOnZLoeTssYMTkd_q-_OA00Aw_W2PG5UuzLyTq2EuJBiw6eMM2hZl3AubVc9aYjblgBG4t2vT5as-IGdhOVrWf5aD7fh3L_pQ70zKCPUubzxTJYoA.
------boundary

JSON Response example

Use dark colors for code blocksCopy
1
{"status": "success"}

Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.