ArcGIS Engine Developer Guide

DEPLOYMENT
License initialization must be built into your
application. For more information, see the earlier
section ‘License initialization’.
The custom application is deployed to an end
user machine that does not have the ArcGIS
Engine Runtime installed. This is the easiest
deployment method for the developer because
the end user must install, register, and authorize
the ArcGIS Engine Runtime software.
The Software Authorization Wizardopens after
installing the ArcGIS Engine Developer Kit.
However, installations of ArcGIS Engine Runtime
do not trigger the Software Authorization
Wizard to start automatically.
Software authorization is the process of unlocking the underlying ArcGIS Engine
Runtime software components. As a developer, you did this yourself when you
installed and set up the ArcGIS Engine Developer Kit. Once you had installed
the software, a Software Authorization wizard opened. It asked that you navigate
to the authorization file (.ecp) that had been
issued to you when you registered the product.
Only after the authorization file was read and
accepted were you able to design and run
applications that use ArcGIS Engine components.
All deployed applications must be
authorized in a similar manner, although there
are a number of different ways to achieve
authorization.
As discussed earlier in this chapter, every
application you build and deploy must first
initialize itself with a suitable license. The store
of suitable licenses that your application initializes
itself against are contained within the
software authorization or keycode file, whichever
is applicable, on the client machine or
network. If your application attempts to
initialize against a license that is not contained
in the authorization file or if all instances of
the needed license have been checked out, then
your application will not be able to run.
You, as the developer, must think in advance about how your clients will acquire
and access an authorization or keycode file suitable to run your application. Your
clients may fall into three categories:
• Licensed ArcGIS Desktop users who have access to the license features that
your application uses.
• Those that will acquire the ArcGIS Engine Runtime software, its authorizations,
or both directly from ESRI.
• Those who will receive the ArcGIS Engine Runtime software and authorizations
packaged within your application and have no direct contact with ESRI.
The following sections discuss the software authorization process for each of
these three user types.
ARCGIS DESKTOP USERS
If your client is a licensed ArcGIS Desktop user, you and your client would go
through the following process to install and run an application that you built:
1. You review and confirm licensing requirements of your application—
ArcView, ArcEditor, or ArcInfo (single use or concurrent) along with any
necessary extensions.
2. Your client confirms that it has the applicable ArcGIS Desktop authorization
or keycode files available for use with your application, as determined in the
previous step.
278 • ArcGIS Engine Developer Guide