18.04.2015 Views

ArcGIS Engine Developer Guide

ArcGIS Engine Developer Guide

ArcGIS Engine Developer Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

DEPLOYMENT<br />

To successfully deploy custom applications to end user machines, <strong>ArcGIS</strong> <strong>Engine</strong><br />

Runtime will need to be installed, the custom application will need to be installed,<br />

and <strong>ArcGIS</strong> <strong>Engine</strong> Runtime may need to be software authorized depending<br />

on the current machine license configurations.<br />

DEPLOYING ARCGIS ENGINE RUNTIME<br />

The <strong>ArcGIS</strong> <strong>Engine</strong> Runtime must be installed on every end user machine to<br />

which a custom application is deployed. This includes machines that may have<br />

<strong>ArcGIS</strong> Desktop installed, where the custom application will initialize itself with<br />

an <strong>ArcGIS</strong> Desktop license. As a purchaser of the <strong>ArcGIS</strong> <strong>Engine</strong> <strong>Developer</strong> Kit,<br />

you can freely distribute <strong>ArcGIS</strong> <strong>Engine</strong> Runtime, either on a CD or within your<br />

custom applications installation program. See Appendix D, ‘Installing <strong>ArcGIS</strong><br />

<strong>Engine</strong> Runtime on Windows, Solaris, and Linux’, for further details on installing<br />

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

The custom application is deployed to an end<br />

user machine that does not have <strong>ArcGIS</strong> <strong>Engine</strong><br />

Runtime installed but has <strong>ArcGIS</strong> Desktop<br />

installed. In this case <strong>ArcGIS</strong> <strong>Engine</strong> Runtime<br />

must be installed on the machine, but the<br />

custom application initializes itself with the<br />

existing <strong>ArcGIS</strong> Desktop license.<br />

DEPLOYING CUSTOM APPLICATIONS<br />

The method used to create a setup for the custom application will have been<br />

decided on at the beginning of the development project and will depend on your<br />

organization, the end user requirements, and any previous experience you have of<br />

creating setups. The custom setup may use Microsoft Windows Installer (MSI)<br />

technology, may be a scripted setup or may simply be a batch file that is distributed<br />

on a CD to the end user.<br />

The following is an example of a batch file that installs both the <strong>ArcGIS</strong> <strong>Engine</strong><br />

Runtime and a custom application from setups on a CD, then launches the software<br />

authorization wizard for the end user.<br />

COPY PROTECTION AND SOFTWARE AUTHORIZATION FOR END<br />

USERS<br />

The final step in developing and deploying <strong>ArcGIS</strong> <strong>Engine</strong> applications is to<br />

ensure that all client machines have the correct license configuration to support<br />

your <strong>ArcGIS</strong> <strong>Engine</strong> application. This section details the various ways end users<br />

and developers can “authorize” the <strong>ArcGIS</strong> <strong>Engine</strong> Runtime components on<br />

client systems.<br />

Chapter 5 • Licensing and deployment • 277

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

Saved successfully!

Ooh no, something went wrong!