Create a Runtime deployment
In this topic
Because every application you deploy requires a minimum set of Runtime core components, you must create a Runtime deployment using the
Deployment Builder, as described in the following procedure. In this process, you also select optional components, which helps ensure you deploy only the Runtime core components you need, keeping your application footprint small. For a description of the optional components, see the Runtime functionality options described section.
When you're finished creating a Runtime deployment, the components you need will reside in a single folder named arcgisruntime10.2.6, giving you an easy way to include the components with your application, data, and client library files.
Deployment Builder does not collect/bundle:
- Client library files (platform-specific client library).
- Your application files.
A deployment for Windows cannot be used on a Linux environment, and a Linux deployment will not be suitable for Windows. Windows uses .dll (Dynamic Link Libraries) and Linux uses .so (Shared Object) files.
- In Windows, click Start > Programs > ArcGIS > Runtime SDK 10.2.6 for Qt > Runtime Tools > ArcGIS Runtime Qt Deployment Builder 10.2.6. In Linux, click Application Launcher Button > Applications > ArcGIS > Runtime SDK 10.2.6 for Qt > Runtime Tools > Deployment Tool 10.2.6 for Qt SDK .The ArcGIS Runtime Deployment Builder appears.
- Click the Create Configuration button.
- In the Deployment Configuration dialog box, in the
Nametext box, type a name for the configuration you're creating, then click OK. Configurations you create can be used as templates for future configurations.
- On the Create Deployment Configuration dialog box, in the
Nametext box, type a name for the deployment. Deployment Builder uses this name as the first part of the name of the folder it creates to store the Runtime deployment.
- In the
Versiontext box, type a number for the version of the deployment you named in the previous step. Deployment Builder uses this version as the last part of the name of the folder it creates to store the Runtime deployment. Once you've created at least one deployment, when you specify a different version for a deployment with the same name, Deployment Builder creates a new deployment folder for the new version.
- In the
and APIarea, select the deployment platform(s) for this deployment, for example, Windows 64-bit.
- In the
Select Optional Functionalityarea, check the check boxes that correspond to the capabilities (Runtime core components) you've included in the application you're deploying. If you don't check any boxes, only the required Runtime core components will be included, such as mapping functionality. When you package data for use with your application, a report is provided (by analyzers) that tells you which options to select in this step. For details on each functionality option, see the Runtime functionality options described section. You can also click an item in the dialog box to view a brief description of it.
- When you're finished selecting options, click
OKto close the dialog box.
- In the ArcGIS Runtime Deployment Builder dialog box, the deployment name and version you just specified will be selected. Click the
Generatebutton to create a deployment for it.
- In the Deployment Location dialog box, in the Folder text box, type a path for or browse to an existing folder where you want the Deployment Builder to write the Runtime deployment. If you previously created a deployment in this folder and you're using the same deployment name (step 4) and the same version (step 5) as you did previously, the previous deployment will be overwritten.
OK.The Deployment Builder writes the required Runtime core components and optional applicable Runtime components to the folder you specified and displays a summary dialog box that provides details on the files copied. Now you're ready to deploy it, along with your application files (for example, your .exe file, client .dll files, and any local data it requires).
Runtime functionality options described
When you package data for use with your application, a report is provided that helps you identify which options the package requires. The options are listed in the following tables. For additional information on which tools come with the Standard license level and which come with extension licenses, see Supported geoprocessing tools.
Select Local Server options if your application uses any local services.
|Local Server Option||Description|
Adds the ability to perform local geocoding using the Local Server. Requires your deployed application to be provisioned with a locator package.
Provides the ability to perform geoprocessing tasks via geoprocessing packages. For a list of supported tools, see Supported geoprocessing tools.
Spatial Analyst extension
Required for advanced spatial analysis.
3D Analyst extension
Required for visibility analysis, such as line of sight and viewshed.
Network Analyst extension
Required for route analysis beyond simple point-to-point routing.
Map Server Results
Required to add results produced as map services.
Provides the ability to use Python scripts.
Python geoprocessing tools
Provides support for geoprocessing tools that use python.
Python PDF output support
Provides support for tools that output PDF files.
Additional data formats
Provides additional vector file data format and raster file data format support.
Provides additional vector file data format support such as the ability to use shapefiles.
Provides additional raster file data format support. For a list of supported rasters, see Local Server raster support.
Raster — ECW Rasters
Provides support for ECW format Raster.
Adds support to let you connect directly to enterprise geodatabases. This option must be selected in conjunction with at least one of the following DBMS(s): DB2, Informix, Oracle, PostgresSQL, or SQL Server.
Additional projection engine transformations
Adds additional projections and geotransformations. For more information on coordinate systems, see Spatial references.
Adds support for using location information form a GPS receiver (a NMEA 0183 source) connected through a serial port or replayed from a file.
Advanced Symbology supports handling advanced symbology with complex renders.
|Advanced Symbology Option||Description|
Military Message Processing (MIL2525C)
Supports the handling and display of military messages using a MIL-STD-2525C-based symbol dictionary.
Military Message Processing (App6B)
Supports the handling and display of military messages using an App6B symbol dictionary.