The following outlines the steps that must be taken to initialize the application with a license:. As previously stated, to run successfully, the application requires at minimum, an ArcGIS Engine product license with the corresponding 3D and Spatial extension licenses.
The application's first attempt at initialization should be against this minimal level of product licensing. The application's attempts at initialization follow the process previously discussed and described as follows:. In this example, a secondary level of licensing is available if the first ArcGIS Engine product level fails to initialize correctly.
The application once again attempts to initialize by following the defined process:. The checkout of licenses might fail even though the availability check has been successful. This is particularly true in cases in which Desktop Concurrent Use licenses were initially available, but might have since been checked out by another application. The application makes a final attempt to initialize by following the defined process:. In this scenario, the application is an enterprise geodatabase editing application; therefore, it requires the minimum of an ArcGIS Engine with Geodatabase Update extension license.
The application also requires Spatial extension functionality for it to run successfully, so the extension needs to be checked out for the duration of the application run time. If that fails, it attempts to initialize against a Standard license, and if still unsuccessful, the application finally attempts to initialize against the Advanced product license.
The following outlines the steps taken to initialize the application with a license:. As previously stated, to run successfully, the application requires at minimum, an ArcGIS Engine with Geodatabase Update extension product license with the corresponding Spatial extension license. The application's attempts at initialization follow the process previously discussed:. In this scenario, a secondary level of licensing is available if the first ArcGIS Engine product level fails to initialize correctly.
This is particularly true in cases where Desktop Concurrent Use licenses were initially available but might have since been checked out by another application. In this example, if both the first ArcGIS Engine and second Standard product levels fail to initialize correctly, a third level of licensing Advanced is available.
Similar to the previous examples, this application also includes the use of the Network extension functionality. However, in this case, the extension is not required simply to run the application. The application enables additional functionality to use the Network extension after it has started. As such, the Network extension will be checked out dynamically during the use of the application rather than at application startup.
If that fails, it makes additional attempts to initialize against a Basic license, then a Standard license, and if still unsuccessful, the application attempts to initialize against the Advanced product license. As previously indicated, to run successfully, the application requires at minimum, an ArcGIS Engine product license.
While network functionality is available within the application, its extension license can be checked out when needed, rather than for the duration of the session.
Since this application dynamically checks out the Network extension, this step is not performed at this time. Instead, the license will be checked out during usage of network functionality. For details on this process, see the Using network functionality section in this topic. In this example, no licenses beyond the ArcGIS Engine product license need to be checked out; therefore, if that license checks out, the application has been successfully configured with licenses.
Since this application dynamically checks out the ArcGIS Network Analyst extension, this step is not performed at this time. Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details. Get started. Install and set up. Amazon EMR. Azure Databricks. Azure Synapse Analytics. Google Cloud Dataproc. Spark Cluster Mode. Spark Local Mode Windows. Core concepts. Arcade expressions. Coordinate systems and transformations.
Data sources. GeoAnalytics comparison. Licensing and Authorization. Spatial relationships. Time stepping. Temporal relationships. Using DataFrames. For those outside the United States, contact your local distributor for information about your authorization numbers.
Recommended: Use an Internet connection to complete the authorization steps below. If you do not have an Internet connection for the machine on which you intend to install the software, you can authorize the software via email.
If you want to facilitate the authorization process or authorize silently, a provisioning file generated from the Licensing portal on My Esri can be used. Choose the desired Single Use product. Click Authorize Now. Select the default option, I have installed my software and need to authorize it. Select Authorize with Esri now using the Internet. If using a provisioning file, choose the option I have received an authorization file from Esri and browse to the file.
Enter your personal information where applicable. Enter your core product authorization number ESUxxxxxxxxx.
0コメント