Usage of ArcGIS Desktop licenses with the UT Asset Manager

Question:

Can the UT Asset Manager also be used with ArcGIS Desktop licenses instead of ArcGIS Engine licenses?

Answer:

Yes, this is possible. This requires an installation of ArcGIS Desktop so that a desktop license can be set in ArcGIS Administrator.

Installation

ArcGIS Desktop must be installed first. Extensions of ArcGIS Desktop such as Schematics or similar do not need to be installed. When installing UT Desktop Suite, the UT Editor component can be deselected if only a workplace with UT Asset Manager is required.

Setup of the licensing

The license is set as usual in the ArcGIS Administrator.

If the UT Asset Manager is only used as an information workplace and the Edit Extension is not installed, an ArcGIS Desktop Basic license is sufficient instead of an ArcGIS Engine Runtime license. However, it is also possible to use an ArcGIS Desktop Standard or ArcGIS Desktop Advanced license.

If the UT Asset Manager is also used to edit data and the Edit Extension is installed, an ArcGIS Desktop Standard license can be used instead of the ArcGIS Engine Geodatabase Update. Alternatively, it is also possible to use an ArcGIS Desktop Advanced license. An ArcGIS Desktop Basic license is not sufficient.

Adjustment of preferred licenses (optional)

The UT Asset Manager checks the availability of the various licenses at startup. The first available license is used. The list of licenses from the AssetManager-Licenses.components file is evaluated in the order in which they are defined there. If the Edit Extension is also installed, only the licenses that allow editing are taken into account.

You can slightly improve the start performance of the UT Asset Manager by storing your own components file with licenses, in which only the licenses that are available are listed. Furthermore, the order of the licenses can be used to determine which license type should be preferred.

You can derive and adapt your own components file with licenses as a copy of AssetManager-Licenses.components. Reset="true" must be inserted in the XML element <Licenses>. The elements for licenses that are not required can be deleted or commented out. The order of the elements of the individual licenses can be adjusted as required.

Example:

<?xml version="1.0" encoding="utf-8"?>
<Configuration>

  <Licenses Comment="my preferred Esri licenses" Reset="true">
    <!--<License Id="License_EsriEngine"
      Info="Esri Engine Runtime License"
      Type="esri" Name="esriLicenseProductCodeEngine"
    />-->
    <!--<License Id="License_EsriGeoDB"
      Info="Esri Engine GDB Update License"
      Type="esri" Name="esriLicenseProductCodeEngineGeoDB"
      Right="Edit"
    />-->
    <License Id="License_EsriBasic"
      Info="Esri Basic License"
      Type="esri" Name="esriLicenseProductCodeBasic"
    />
    <License Id="License_EsriStandard"
      Info="Esri Standard License"
      Type="esri" Name="esriLicenseProductCodeStandard"
      Right="Edit"
    />
    <!--<License Id="License_EsriAdvanced"
      Info="Esri Advanced License"
      Type="esri" Name="esriLicenseProductCodeAdvanced"
      Right="Edit"
    />-->
  </Licenses>

</Configuration>