18.04.2015 Views

ArcGIS Engine Developer Guide

ArcGIS Engine Developer Guide

ArcGIS Engine Developer Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ARCGIS LICENSING OPTIONS<br />

PRODUCT LICENSING<br />

On installation of the <strong>ArcGIS</strong> <strong>Engine</strong> <strong>Developer</strong> Kit and <strong>ArcGIS</strong> <strong>Engine</strong><br />

Runtime, you will need to read and agree to the ESRI Master License Agreement<br />

(MLA). The MLA defines the permitted use of the software. A copy of the MLA<br />

can be found in C:\Program Files\<strong>ArcGIS</strong>\License or at<br />

http://www.esri.com/licenseagreement.<br />

The <strong>ArcGIS</strong> <strong>Engine</strong> <strong>Developer</strong> Kit is a single-use license product, meaning a<br />

license must be dedicated for each computer that has access to the software. With<br />

the <strong>ArcGIS</strong> <strong>Engine</strong> <strong>Developer</strong> Kit, you have the right to develop an unlimited<br />

number of applications on a single computer and deliver the applications to<br />

others. It is illegal to redistribute the <strong>ArcGIS</strong> <strong>Engine</strong> <strong>Developer</strong> Kit registration<br />

number or authorization file.<br />

The <strong>ArcGIS</strong> <strong>Engine</strong> Runtime is also a single-use license, meaning it is intended for<br />

dedicated desktop computers. Each machine running a custom application developed<br />

with the <strong>ArcGIS</strong> <strong>Engine</strong> <strong>Developer</strong> Kit will require an <strong>ArcGIS</strong> <strong>Engine</strong><br />

Runtime license or an <strong>ArcGIS</strong> Desktop license. The <strong>ArcGIS</strong> <strong>Engine</strong> Runtime<br />

license does not permit the <strong>ArcGIS</strong> <strong>Engine</strong> Runtime to be used for development<br />

purposes, nor can it be deployed on a server machine. The <strong>ArcGIS</strong> <strong>Engine</strong><br />

Runtime setup can be redistributed, but the license and registration number<br />

cannot without authorization from ESRI. Any number of applications can use<br />

the same <strong>ArcGIS</strong> <strong>Engine</strong>, as long as they are all installed on the same machine.<br />

Licensing and deployment considerations for<br />

<strong>ArcGIS</strong> Server-based development are discussed<br />

in the <strong>ArcGIS</strong> Server Administrator and<br />

<strong>Developer</strong> <strong>Guide</strong>.<br />

The <strong>ArcGIS</strong> controls, as part of <strong>ArcGIS</strong> <strong>Engine</strong>,<br />

also follow this runtime licensing model.<br />

MapControl, PageLayoutControl, ReaderControl,<br />

TOCControl, and ToolbarControl applications can<br />

utilize the <strong>ArcGIS</strong> <strong>Engine</strong> Runtime, ArcView,<br />

ArcEditor, or ArcInfo product licenses. Since<br />

GlobeControl and SceneControl extend core<br />

<strong>ArcGIS</strong> <strong>Engine</strong> functionality, they require a<br />

corresponding 3D extension license in addition<br />

to the core product license.<br />

RUNTIME LICENSING<br />

There are two types of <strong>ArcGIS</strong> <strong>Engine</strong> Runtime licenses—product licenses and<br />

extension licenses. Product licenses include core ESRI software, such as <strong>ArcGIS</strong><br />

<strong>Engine</strong> Runtime, <strong>ArcGIS</strong> Desktop licenses (ArcView, ArcEditor, ArcInfo), and<br />

<strong>ArcGIS</strong> Server. Extension licenses include additional ESRI products that build<br />

on those core licenses, such as the Spatial extension for <strong>ArcGIS</strong> <strong>Engine</strong>, the<br />

3D Analyst extension, and the Network extension. This book deals solely with<br />

<strong>ArcGIS</strong> <strong>Engine</strong>-based development; therefore, <strong>ArcGIS</strong> Server product and extension<br />

licensing will be ignored. Since, as mentioned in Chapter 1, <strong>ArcGIS</strong> <strong>Engine</strong><br />

Runtime is the platform on which <strong>ArcGIS</strong> Desktop is built, <strong>ArcGIS</strong> Desktop<br />

licensing may factor into your application development and is discussed here.<br />

Custom applications that utilize core <strong>ArcGIS</strong> <strong>Engine</strong> features can be built to run<br />

against any or all of the following product runtime licenses:<br />

• <strong>ArcGIS</strong> <strong>Engine</strong> Runtime<br />

• ArcView<br />

• ArcEditor<br />

• ArcInfo<br />

Applications that utilize extended <strong>ArcGIS</strong> <strong>Engine</strong> features require extension<br />

licenses that correspond to the <strong>ArcGIS</strong> product providing the core license. In<br />

other words, if your application initializes with an <strong>ArcGIS</strong> <strong>Engine</strong> Runtime<br />

license, any needed extension licenses must be <strong>ArcGIS</strong> <strong>Engine</strong> Runtime extensions,<br />

not <strong>ArcGIS</strong> Desktop extensions.<br />

Chapter 5 • Licensing and deployment • 255

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!