Deploy an App

Deployment Stages

Once you have saved your app, you can push it through the deployment stages in the following order:

  1. Development

  2. Testing (optional)

  3. Staging (optional)

  4. Production

At each stage, a copy of the application is created and given an ID. Once the app reaches Production, it gets an ID that remains with the app and can be sent to end users. An app only moves in one direction through the stages. Any changes must be made in Development and then moved through the stages again to Production.

In the diagram above, we see for each deployment stage, a copy of the app's web map (or web scene) is made. As of Geocortex Web 5.9, for each deployment stage, copies of the app's capabilities owned by the app author—such as workflows, reports and print templates—are also made. Any app capability not owned by the user will not be copied and remain the same reference for all deployment stages.

Environment Values

Environment Values allow you to substitute text for each deployment stage. This feature is most useful to allow the various deployment stages of the app to use different service URLs.

Any parts of your app that are affected by these text changes are listed in the Pre-Deployment Summary window that appears when you deploy your app from one stage to another.

Deploy the App

Once you have selected the deployment stages for your app, you can push it through the deployment stages.

To deploy an app to a deployment stage, you must have at least read-only access for items representing web maps, web scenes and client-side workflows, as well as write access for server-side items such as reports, print templates and server-side workflows. The simplest way to verify you have write access is to ensure you can open the server-side item in its own Designer software. For example, open a server-side workflow in Workflow Designer. When deploying to a deployment stage that has previously been pushed, you should be the owner of the target items.

To select the deployment stages for your app:

If you reduce the number of deployment stages for your app, the excluded stages are permanently discarded.

  1. Once you have saved your app in Designer, in the taskbar, click Deploy.

  2. Click Change Deployment Strategy.

    The Change Deployment Strategy window appears.

  3. In the Deployment Strategy menu, choose one of the following:

  4. Click FileSave.

To deploy the app:

  1. Once you have saved your app in Web Designer and selected the deployment stages, click Deploy.

  2. If applicable, once your app is ready for testing, click Push to Testing.

    If applicable, in the Pre-Deployment Summary window that appears, review the changes that have occurred since the last time you pushed to the Testing stage, and click Continue.

    If the app contains certain kinds of capabilities whose information is stored on other servers, such as server-based workflows, you may be required to enter login credentials for those resources.

  3. If applicable, once your app is ready for staging, click Push to Staging.

    If applicable, in the Pre-Deployment Summary window that appears, review the changes that have occurred since the last time you pushed to the Staging stage, and click Continue.

    If the app contains certain kinds of capabilities whose information is stored on other servers, such as server-based workflows, you may be required to enter login credentials for those resources.

  4. Once your app is ready for production, click Push to Production.

    In the Pre-Deployment Summary window that appears, review the changes that have occurred since the last time you pushed to the Production stage, and click Continue.

    If the app contains certain kinds of capabilities whose information is stored on other servers, such as server-based workflows, you may be required to enter login credentials for those resources.

    The various deployment stage versions of the Web Mapping Applications, Web Maps, Web Scenes, and owned Workflows, Reports and Print Templates are stored in the My Content section within the Geocortex Viewer files (don't delete) folder of your ArcGIS portal and contain the following suffixes:

    • Development: No suffix

    • Testing: (test)

    • Staging: (staging)

    • Production: (prod)

  5. Configure the sharing permissions of the deployment stages of your app as appropriate.

© 2020 VertiGIS North America Ltd. All Rights Reserved.

Documentation Version 5.10