Creating a runtime deployment

Because every application you deploy requires a minimum set of runtime 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 components you need, keeping your application footprint small. For a description of the optional components, see the section below, Runtime functionality options described.

When you're finished creating a runtime deployment, the components you need will reside in a single folder named 'arcgisruntime10.1.1', giving you an easy way to include the components with your application, data, and dependent .jar files.

The Deployment Builder does not collect/bundle:

• Dependent .jar files (platform-specific JARs). For details on which ones you must manually include, see Library file list for deployment.
• Your application files.
• Your application data. See step 7 below.

Caution:

A deployment for Windows 32 or 64 bit 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.

Steps:

1. In Windows, click 'Start > Programs > ArcGIS > Runtime SDK 10.1.1 for Java > Runtime Tools > Deployment Builder 10.1.1'.

   The ArcGIS Runtime Deployment Builder appears.

2. Click the Create Configuration button.
3. In the Deployment Configuration dialog box, in the Name text box, type a name for the configuration you are creating, then click OK. Configurations you create can be used as templates to base future configurations on.
4. On the Create Deployment Configuration dialog box, in the Name text 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.
5. In the Version text 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 have 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.
6. In the Platform area, check the check boxes that correspond to the deployment platform(s) for this deployment, for example, 32- and/or 64-bit.
7. In the Select Optional Functionality area, check the check boxes that correspond to the capabilities (runtime components) you've included in the application you are deploying. If you don't check any boxes, then only the required runtime 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 following section in this topic, Runtime functionality options described. You can also click on an item in the dialog box to view a brief description of it.
8. When you are finished selecting options, click OK to close the dialog box.
9. In the ArcGIS Runtime Deployment Builder dialog box, the deployment name and version you just specified will be selected. Click the Generate button to create a deployment for it.
10. In the Deployment Location dialog box, in the Folder text box, type in a path for or browse to an existing folder you want the Deployment Builder to write the runtime deployment to. If you previously created a deployment in this folder and you are using the same deployment name (step 4) and the same version (step 5) as you did previously, the previous deployment will be overwritten.
11. Click OK.

    The Deployment Builder writes the required runtime 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 are 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 below the package requires.

Option	Description
Local Server	Required if your application uses any local services.
Geocoding	Adds the ability to perform local geocoding. Requires your deployed application to be provisioned with a locator package.
Geoprocessing	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.
Python Scripting	Provides the ability to use Python scripts.
Additional data formats	Provides additional vector file data format and raster file data format support.
Vector	Provides additional vector file data format support such as the ability to use shapefiles.
Raster	Provides additional raster file data format support. For a list of supported rasters, see Supported raster types.
SDE	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 Coordinate system identifiers.
GPS	Adds support for using location information form a GPS receiver (a NMEA 0183 source) connected through a serial port or replayed from a file.
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.
S57 Hydrographic Symbology	Supports the handling and display of S57 data using S57 Symbology.