This is the OLD license manager check. It is suggested to use the NEW License Manager Module going forward. The Esri® License Manager monitoring point queries a License Manager (located on the same network as the GeoSystems Monitor), to confirm that it is running and issues an alert when the number of licenses being used approaches (or exceeds) the number available. Optionally, this check can create a web page that is refreshed each time the check is run which can be used to present information to a broader audience on who is using which licenses or extensions. Note: For this check to function correctly, the LMutil.exe file must be copied from the current Esri® License Manager to the ‘Scripts’ folder on the GeoSystems Monitor server. Most any version of LMutil.exe will work. Example – From: ‘C:\Program Files (x86)\ArcGIS\License10.2\bin’ (on the License Manager server) |
The parameters that are unique to the Esri® License Manager include:
License Manager Name |
Name of the Esri® License Manager server to check |
License Manager Port # |
Port number that the Esri® License Manager runs on Note: Default License manager port value is 27000 |
License Type |
Type of license/extension to check for A license/extension can be checked in one of two ways:
Note: Only the information for the Info license type will be graphed; however alerts will be sent for the Info, Edit, and View Desktop licenses in accordance with the designated Warning Number.
Note: As a general rule, when checking extensions the user will want to set up the checks individually. The following are valid entries for the License Type parameter: Desktop Licenses All Info or Advanced Edit or Standard View or Basic In addition, the following parameters can be entered in the License Type field: FindPort – Will help find the port used by the license manager. Uses the ‘Port’ parameter as the starting point, normally 27000, and incrementally checks upward several ports. Debug – When entered in the ‘License Type’, creates a log entry for the COMPLETE output of the lmutil query. Good for troubleshooting issues with licenses and types. Information for AutoCAD licenses and for licenses associated with FlexNet Publisher. For AutoCAD, enter: ACAD::<auto cad license type>. If a web page only is desired, enter ACAD:: in the License type and the web page path. The web page created with this check is called ACADLicense.html. For FlexNet Publisher enter: FME::FmeLicenseType or OTHER::GenericLicenseType These web pages will be called FMELicense.html or OTHERLicense.html Extensions ACT - Users of ACT ARCSTORM - Users of ArcStorm ARCSTORMENABLE - Users of ArcStormEnable CITYENGADV - Users of CityEngAdv DATAREVIEWER - Users of DataReviewer GEOSTATS - Users of GeoStats GEOSTATISTICAL - Users of GeoStats GRID - Users of Grid SPATIAL - Users of Grid INTEROP - Users of Interop DATA - Users of Interop DATAINTEROPERABILITY - Users of Interop JTX - Users of JTX MRSID - Users of MrSID NETWORK - Users of Network PLOTTING - Users of Plotting PUBLISHER - Users of Publisher SCHEMATICS - Users of Schematics TIFFLZW - Users of TIFFLZW TIN - Users of TIN 3D - Users of TIN TRACKING - Users of Tracking VBA - Users of VBA |
Warning Number |
The number of licenses / extensions remaining at which the GeoSystems Monitor is to send an alert Note: The default Warning Number value is zero (0). |
Web Page Path |
(Optional) When entered, this parameter creates a Web page (arcgislicense.html) and saves license/extension information to this path. For example: c:\inetpub\wwwroot |
When the Web page Path parameter is populated, the GeoSystems Monitor creates a web page (arcgislicense.html) to the path specified which displays who is using what license and extension type. |
The webpage header can be modified using the following files, located in the ‘scripts’ folder.
The web page can be created whether or not other license or extension checks are in place. If the web application needs to be refreshed more often than the license or extensions need to be checked, create a point with only the ‘Web Page Path’ parameter and have it run more often (for example every two minutes).
The web page path can be on the local GeoSystems Monitor server, either under IIS or a UNC path to another server.
Note: This parameter should be entered in only ONE point check, in order to avoid a web page writing over itself unnecessarily