Geocortex Essentials 4.5. Installation Guide

Transcription

1 Geocortex Essentials 4.5 Installation Guide

2 2016 Latitude Geographics Group Ltd. All Rights Reserved. Printed in Canada The information contained in this document is the exclusive property of Latitude Geographics Group Ltd. This work is protected under Canadian and US copyright law and copyright laws of the given countries of origin and applicable international laws, treaties, and/or conventions. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying or recording, or by any information storage or retrieval system, except as expressly permitted in writing by Latitude Geographics Group Ltd. All requests should be sent to Attention: Contracts Manager, Latitude Geographics Group Ltd, Wharf Street, Victoria, British Columbia V8W 1T7. This information is subject to change without notice. US Government Restricted Rights The Software and documentation are provided with restricted rights. Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFARS , or subparagraphs (c)(1) and (2) of the Commercial Computer Software - Restricted Rights at 48 CFR , as applicable. The Contractor/Manufacturer is Latitude Geographics Group Ltd., Wharf Street Victoria, British Columbia V8W 1T7. Geocortex and Latitude Geographics are registered trademarks of Latitude Geographics Group Ltd. in the United States and Canada, and are trademarks in other jurisdictions around the world. Esri, the Esri globe logo, and esri.com are trademarks, service marks, or registered marks of Esri in the United States, the European Community, or certain other jurisdictions. Trademarks are provided under license from Esri. Microsoft and the Windows logo are registered trademarks of Microsoft Corporation. Other companies and products mentioned herein are trademarks or registered trademarks of their respective trademark owners.

3 Contents Contents 1 Welcome to Geocortex Essentials About this Guide Getting Help Use the Discussion Forum Communicate by Provide Feedback on Documentation Disclaimer 2 2 Requirements Hardware Requirements for Essentials Servers Minimum Requirements for Essentials Servers Requirements for Servers Running Instant Search Software Requirements for Essentials Servers Operating System Requirements NET Framework Requirements Web Server Requirements Geocortex Essentials Manager Requirements Supported Versions of the Geocortex Viewers Supported Versions of Esri Software Supported Versions of ArcGIS Server Supported Versions of Portal for ArcGIS 8 3 Deployment Single-Server Deployments Dual-Server Clusters Run Essentials Behind a Reverse Proxy Set Up Cross-Origin Resource Sharing (CORS) 13 4 About Installation What the Installer Installs About Post-Installation Configuration Installation Options Installation Options for Essentials Installation Options for Geocortex Core Installation Options for the Viewer Frameworks Essentials Trial Versions 21 5 Download the Software 22 6 First-Time Installation Install Essentials for the First Time Get Started with Essentials 33 i

4 Geocortex.Essentials.4.5.Installation Guide 7 Upgrading Upgrading Essentials Essentials Versions that Require Manual Steps Upgrade Essentials Upgrading Viewers About Upgrading Viewers Using Essentials Viewer Versions that Require Manual Steps Upgrade Viewers Using Essentials Restore a Viewer 48 8 Post-Installation Configuration Launch the Post Installer Activate Geocortex Essentials Choose a Method to Sign In to Manager Account Types that have Access to Manager Hosts that have Access to Manager Configure Single Sign-On to Manager Configure Manager Sign-In Using Portal for ArcGIS Configure Manager Sign-In Using ArcGIS Online Configure Manager Sign-In Using Windows Change which Accounts have Access to Manager Manage the Essentials Web Applications About the Application Pools About the IIS Virtual Directories About the Websites About Hosts Configure Hosts Change IIS Settings for Essentials Change IIS Settings for Essentials Manager Change IIS Settings for Identity Server Manage Viewer Templates Install Viewer Templates Deploy a Viewer Template to IIS Deploy a Viewer's Management Pack Enable Cross-Domain Support Configure Windows Features 82 9 Manual Site Migration Back Up and Restore Your Essentials Installation Back Up Essentials Data Back Up HTML5 Viewer Data Steps to Restore Geocortex Essentials Data from a Backup Schedule Virtual Machine Backups 86 ii 2016 Latitude Geographics Group Ltd. All Rights Reserved

5 Contents Appendix A: Geocortex Core Ports and Firewall Access 87 A.1 Default Ports Used by Geocortex Core 87 A.2 Change the Data Store's Port 87 A.3 Firewall Access for Geocortex Core 89 Appendix B: Locations of Essentials Files and Folders 90 Appendix C: Uninstallation 93 C.1 Components (Programs) 93 C.2 Web Server Configuration 93 iii

6 1 Welcome to Geocortex Essentials 1 Welcome to Geocortex Essentials Engineered from the ground up to work with Esri ArcGIS, Geocortex Essentials provides cutting edge tools, processes, and features that dramatically reduce the time and effort it takes to create and maintain quality ArcGIS applications. The Geocortex viewers that ship with Essentials the Geocortex Viewer for HTML5 and the Geocortex Viewer for Silverlight enable you to create working, configurable, web mapping applications with a few clicks. 1.1 About this Guide This guide has the following sections: Welcome: Provides guidance on getting help. Requirements: Specifies the hardware and software requirements for running Essentials. Deployment: Outlines how to deploy Essentials as a distributed system with redundant REST APIs. About Installation: Describes the main steps to install Essentials and the viewer frameworks, and the options that you have at each step. Download the Software: Provides instructions for downloading the Essentials installer, and downloading the installation packages for the Geocortex Viewer for HTML5 and the Geocortex Viewer for Silverlight. First-Time Installation: Provides instructions for installing the software and performing the initial postinstallation configuration, including installing viewer templates. This section also provides direction on getting started with Essentials, for administrators who are new to Essentials. Upgrading: Provides instructions for upgrading Essentials and viewers. Post-Installation Configuration: Provides instructions for using all of the Post Installer's functions. Manual Site Migration: Provides instructions for manually copying a site from one instance of Essentials to another. 1.2 Getting Help Use the Discussion Forum The Geocortex Support Center has an Essentials discussion forum where you can post questions about Geocortex Essentials. The forum is a great place to get answers from the Geocortex community Communicate by If you have a question that is not suitable for posting to the forum, and you have an active Support agreement, send an message to the Geocortex Support team at support@geocortex.com. The Support team will respond by . 1

7 Geocortex Essentials 4.5.Installation Guide Provide Feedback on Documentation Send comments, suggestions, and requests regarding Geocortex product documentation to Disclaimer Essentials works with other licensed software products. You are responsible for ensuring that all the required software licenses are in place and appropriate for your chosen system configuration. Any software installation involves some risk to your system. Make sure you back up all software and data before you install any Essentials components. Please refer to your Essentials software license agreement for information about limitations on liability and other legal considerations Latitude Geographics Group Ltd. All Rights Reserved.

8 2 Requirements 2 Requirements 2.1 Hardware Requirements for Essentials Servers Any computer that can run one of the supported operating systems is compatible with Geocortex Essentials 4.5. If you are going to use the Instant Search feature, you will need a more powerful server. To ensure adequate performance, follow the guidelines given below. For additional information about Instant Search, refer to the Geocortex Essentials Administrator Guide Minimum Requirements for Essentials Servers More memory and a faster CPU improve Essentials performance. We recommend that your servers surpass the minimum requirements. Minimum Hardware Requirements for an Essentials Server Hardware Component Minimum Recommended Random Access Memory (RAM) 4 GB 8 GB or higher Storage Drive (HDD, SSD) 1 GB 5 GB or higher CPU 2 GHz, x64 2 GHz or higher, x Requirements for Servers Running Instant Search Instant Search is I/O bound. When serving search requests, Instant Search accesses both system memory (RAM) and the storage drive. You can improve the performance of Instant Search by increasing RAM and upgrading the storage drive. Instant Search is not CPU bound improving the server's CPU does not significantly improve the performance of Instant Search. To improve Instant Search performance: Upgrade to a Solid-State Drive: Instant Search reads from the storage drive where the index is stored. Reading from a solid-state drive (SSD) is much faster than reading from a hard disk drive. To ensure the quickest access times, set up the Geocortex Core data folder on a partition on a solid-state drive. To do this, change the location of the data folder to point to the SSD partition. You can change the location of the data folder when you run the Geocortex Core installer with the Geocortex Core Management Application. For a typical installation, you can find this application at C:\Program Files\Latitude Geographics\Geocortex Core\Management\Geocortex.Platform.Management.exe. Increase Server RAM: Increasing the server's RAM allows you to allocate more RAM to Instant Search, and have more RAM for the other processes that the server runs. Increase the RAM Available to Instant Search: Instant Search uses the amount of RAM that is configured for it in Geocortex Core. You can increase the amount of RAM that Geocortex Core allocates to Instant Search. For instructions, see "Optimize Instant Search" in the Geocortex Essentials Administrator Guide. 3

9 Geocortex Essentials 4.5.Installation Guide Hardware Requirements for an Essentials Server Running Instant Search Hardware Component Minimum Recommended Notes Random Access Memory (RAM) 6 GB 8 GB or higher St Storage Drive (HDD, SSD) 40 GB HDD 100+ GB SSD As a guideline, the Instant Search index requires about 2 GB of disk space per 1 million features. This ratio varies with feature size. 2.2 Software Requirements for Essentials Servers The software requirements are the same for all servers, whether they are running Geocortex Core and Essentials, or just the REST API. For more information, see Deployment on page 9. Before starting the installation, the installer checks whether the server meets the software requirements. The installer will not install a component if the component's requirements are not met Operating System Requirements Because Essentials is built on Microsoft's.NET Framework, Essentials must be deployed on Microsoft Windows, specifically, on 64-bit Windows. Essentials supports the following versions of 64-bit Windows: Windows Server 2012 R2 x64 Windows Server 2012 x64 Windows Server 2008 R2 x64 (Standard / Enterprise) Windows Server 2008 x64 Service Pack 2 (Standard / Enterprise) Windows 10 x64 Windows 8.1 x64 Windows 8 x64 Windows 7 x NET Framework Requirements Geocortex Essentials is built on Microsoft's.NET Framework. Essentials requires.net Framework 4.5 or newer. You must download and install the.net Framework before you can install Essentials. You can download the.net Framework from the Microsoft Download Center Web Server Requirements Geocortex Essentials requires Internet Information Services (IIS) 7.0 or newer Latitude Geographics Group Ltd. All Rights Reserved.

10 2.2.3 Web Server Requirements Specific IIS components must be enabled. If your operating system supports Deployment Image Servicing and Management (DISM), the Post Installer enables the required components automatically when you run the Post Installer after installing Essentials. If your operating system does not support DISM, you must manually enable the required Windows features following the instructions below. To find out if the operating system you are using supports DISM, refer to DISM Supported Platforms ( The list and screen capture below show the IIS components that Essentials requires. Essentials requires the following IIS components: Management Tools IIS Management Console IIS Management Scripts and Tools Management Service Web Server Application Development.NET Extensibility 4.5 * ASP.NET 4.5 * ISAPI Extensions ISAPI Filters Common HTTP Features Default Document ** Static Content Security Basic Authentication Request Filtering Windows Authentication * The.NET Extensibility 4.5 and ASP.NET 4.5 options are not present in versions of Windows older than Windows Server 2012 and Windows 8 select.net Extensibility and ASP.NET instead. ** Older versions of Windows may not require the Default Document component. Having additional IIS components enabled does not affect Essentials. IIS components required for Geocortex Essentials, shown in Windows 8 5

11 Geocortex Essentials 4.5.Installation Guide Enable IIS Components in Windows Server 2012 To enable IIS components that are required by Essentials in Windows Server 2012: 1. Open Server Manager. 2. In the Manage menu, select Add Roles and Features. The Add Roles and Features wizard opens. 3. Step through the wizard, following the instructions in each panel, until you reach the Server Roles panel. 4. Click the plus sign beside Web Server (IIS) to expand the hierarchy. 5. Expand Web Server. 6. Expand Common HTTP Features and select the check boxes beside: Default Document Static Content 7. Expand Security and select the check boxes beside: Request Filtering Basic Authentication Windows Authentication 8. Expand Application Development and select the check boxes beside:.net Extensibility 4.5 ASP.NET 4.5 ISAPI Extensions ISAPI Filers 9. Expand Management Tools and select the check boxes beside: IIS Management Console IIS Management Scripts and Tools Management Service 10. Finish the wizard. Enable IIS Components in Windows 8 To enable IIS components that are required by Essentials in Windows 8: 1. In the Windows Start menu, click Control Panel. The Control Panel opens. 2. Click Programs and Features. The Programs and Features panel opens Latitude Geographics Group Ltd. All Rights Reserved.

12 2.3 Geocortex Essentials Manager Requirements 3. In the side panel, click Turn Windows features on or off. The Windows Features dialog box opens. 4. Click the plus sign beside Internet Information Services to expand the hierarchy. 5. Expand Web Management Tools and select the check boxes beside: IIS Management Console IIS Management Scripts and Tools IIS Management Service 6. Expand World Wide Web Services. 7. Expand Application Development Services and select the check boxes beside:.net Extensibility ASP.NET ISAPI Extensions ISAPI Filters 8. Expand Common HTTP Features and select the check boxes beside: Default Document Static Content 9. Expand Security and select the check boxes beside: Basic Authentication Request Filtering Integrated Windows Authentication 10. Click OK. The dialog box closes. 11. Close the Control Panel. 2.3 Geocortex Essentials Manager Requirements Geocortex Essentials Manager runs in a web browser. Manager supports the following browsers: Chrome: Current version Firefox: Current version Internet Explorer: Versions 9, 10, and 11 Microsoft Edge: Current version These browsers are supported in the sense that their use with Manager is tested. Other browsers and browser versions may also work with Manager. Geocortex Essentials Manager uses cookies. To use Manager, cookies must be enabled in your web browser. 7

13 Geocortex Essentials 4.5.Installation Guide 2.4 Supported Versions of the Geocortex Viewers We recommend using the following versions of the Geocortex viewer frameworks with Geocortex Essentials 4.5: Geocortex Viewer for HTML5 2.6 Geocortex Viewer for Silverlight 2.5 Running Essentials with older versions of the viewer frameworks results in reduced viewer capabilities. 2.5 Supported Versions of Esri Software Supported Versions of ArcGIS Server Geocortex Essentials 4.5 supports ArcGIS Server 10.1 and newer Supported Versions of Portal for ArcGIS Geocortex Essentials 4.5 works with the following versions of Portal for ArcGIS: Portal for ArcGIS 10.3, : Portal for ArcGIS 10.3 or newer is required for secured content and sign-in to Manager using Portal for ArcGIS accounts. Portal for ArcGIS 10.2.x: Supports unsecured content only. Does not support signing in to Manager using Portal for ArcGIS accounts or securing sites using Portal for ArcGIS Latitude Geographics Group Ltd. All Rights Reserved.

14 3 Deployment 3 Deployment A Geocortex Essentials deployment consists of one or more servers that run Essentials and Geocortex Core. Geocortex Core provides software services that Geocortex applications like Essentials use. You can connect Essentials servers in a cluster. A cluster is a group of servers that work together to behave like a single system. The end user's experience is the same no matter which server in the cluster the user connects to. In an Essentials cluster, the servers use the same server-side configuration (sites), client-side web applications (viewers), and Core data (for example, security settings and Instant Search index). Clusters provide redundancy. Redundancy ensures that failure of an individual component does not cause the entire system to fail. Clusters also enable you to scale up and load balance your system. Load balancing distributes processing loads across multiple servers to improve performance. Essentials deployments fall into three categories: One Server: A single-server deployment has no redundancy. If the server fails, end users lose access to your sites. Two Servers: The servers share a single copy of the configuration, which is stored on a network share. Each server has a full copy of Geocortex Core's data. If one of the servers fails, end users continue to have access to your sites. For more information, see Dual-Server Clusters on page 10. Three or More Servers: The servers share a single copy of the configuration, which is stored on a network share. Geocortex Core's data can be distributed in different ways, depending on how Core's subsystems are configured. By default, the data is distributed across the different servers, so each server stores a portion of the data no server has a full copy of the data. If you remove a server from a system with three or more servers, you may lose Core data such as your security settings or part of your Instant Search index. Setting up a Geocortex Essentials system for redundancy or load balancing is an advanced scenario. Contact Geocortex Support to arrange a consultation. The time required to complete the set-up depends on the complexity of your environment. Please ensure that you have adequate Support hours available. Geocortex Essentials is not engineered to automatically upgrade load balanced deployments. Manual steps may be required to upgrade Essentials in a load-balanced, multi-server environment. If you need help upgrading a multi-server deployment, contact Geocortex Support. The time required to complete the upgrade depends on the complexity of your environment. Please ensure that you have adequate Support hours available. 3.1 Single-Server Deployments The simplest Geocortex Essentials deployment consists of a single Essentials server that handles all requests from client web applications. A single-server deployment does not provide redundancy. If the server fails, end users lose access to your sites. Single-server deployments usually have all of Geocortex Essentials's components installed on the server. Geocortex Core must also be installed. When you launch the Post Installer, it automatically runs the Geocortex Core installer if Geocortex Core is not yet installed. 9

15 Geocortex Essentials 4.5.Installation Guide 3.2 Dual-Server Clusters The diagram below shows an example of a dual-server cluster. Example of a secure, load-balanced deployment with redundancy Latitude Geographics Group Ltd. All Rights Reserved.

16 3.3 Run Essentials Behind a Reverse Proxy The example deployment is architected for redundancy and security. Clustering provides redundancy of the REST API and Geocortex Core data. Placing the Essentials Sites and Temp folders in a redundant file share provides redundancy for configuration files, resource files, and temporary files. The Temp folder is used by various Essentials features, including printing and reporting. Workflows can also write to the Temp folder. The example deployment uses two firewalls. This creates two demilitarized zones (DMZs) a private zone with an internal IP address (internal.mycompany.com) for the Essentials servers and the file share, and a public zone with an external IP address (external.mycompany.com) for the viewers. The use of a reverse proxy ensures that there is another address between what end users see and your servers and file share. Additional security is provided by the use of the secure socket layer (SSL) protocol, HTTPS. 3.3 Run Essentials Behind a Reverse Proxy One way to make an Essentials deployment publicly available is to use a reverse proxy. In this deployment scenario, incoming requests from the Internet go to the reverse proxy. The reverse proxy forwards the request to the server that hosts Essentials. Responses from Essentials go back through the reverse proxy. Microsoft Application Request Routing (ARR) works well with Geocortex Essentials. There are two main steps to configure Essentials to run behind a reverse proxy: 1. Register the reverse proxy's URL with Essentials. This tells Essentials to accept requests that come from the reverse proxy. 2. Configure the REST API's external URL. (optional) You only need to do this if you use different internal and external URLs for your servers. The external URL that you configure in Step 2 is used for operations that return a URL, such as reporting and printing. For example, when an end user runs a report, Essentials returns the URL to the report. The viewer displays a hyperlink to the URL, which the user clicks to download the report. Suppose your Essentials server is essentialsserver.internal.com and your reverse proxy is myreverseproxy.public.com. The URL that Essentials creates is based on internal.com, which the end user is not allowed to access. Configuring the external URL enables Essentials to convert the URL to the external form, public.com, which the user can access. To configure Essentials to run behind a reverse proxy: Step 1: Register the Reverse Proxy with Essentials 1. In the Post Installer, click Configure Geocortex Essentials REST API in the side panel. 2. Click Hosts. 3. In the blank box at the bottom of the list, type the fully qualified host name for the reverse proxy, for example, myreverseproxy.domain.com. If you are not using the default port (port 80 for HTTP, port 443 for HTTPS), make sure to include the port, for example, myreverseproxy.domain.com: If the reverse proxy uses SSL, make sure that is selected in the Type box. If the reverse proxy does not use SSL, click the down arrow in the Type box and select 11

17 Geocortex Essentials 4.5.Installation Guide If you want the reverse proxy to accept both HTTP and HTTPS, without upgrading HTTP to HTTPS, register both versions of the URL and make sure that the HTTP version is higher in the list than the HTTPS version. Click to drag an entry up or down in the list. Example of a reverse proxy host name configured in the Post Installer 5. Click OK. 6. Click Finish. Step 2: Configure the REST API's External URL (optional) Do this step if you use different internal and external URLs for your servers. 1. In Manager, click the Application Settings hyperlink at the top of the page. Location of Application Settings hyperlink 2. In the External REST URL box, enter the URL to the REST API's root, for example: 3. Click OK. The setting takes effect immediately Latitude Geographics Group Ltd. All Rights Reserved.

18 3.4 Set Up Cross-Origin Resource Sharing (CORS) 3.4 Set Up Cross-Origin Resource Sharing (CORS) An Essentials system can have multiple servers, with applications and other resources on different domains. Web servers and web browsers restrict cross-domain requests for security reasons. If Essentials and the HTML5 Viewer are installed on different machines, you must set up Cross-Origin Resource Sharing (CORS) so that browsers running the HTML5 Viewer do not block requests. CORS was introduced in HTML5 as a way to allow legitimate interactions between origins. The Wikipedia article Crossorigin resource sharing provides an introduction to CORS. For information about setting up cross-domain access for Silverlight viewers, refer to the Geocortex Viewer for Silverlight Administrator and Developer Guide. Two common scenarios that use CORS are: Essentials and the HTML5 Viewer are deployed to different domains. By default, the HTML5 Viewer will not load configuration from a different domain, and Essentials will not allow cross-domain requests. For example, you may want to embed the HTML5 QuickStart viewer into an existing site that is on a different domain. (The QuickStart viewer is included in the HTML5 Viewer's installation package.) The viewer accesses resources, such as workflows or a geometry service, that are on a different domain than the Viewer. In this case, you can use a proxy page to set up cross-origin access instead of using CORS. Refer to the Geocortex Viewer for HTML5 Administrator and Developer Guide for information on setting up a proxy page. We recommend deploying Essentials and the HTML5 Viewer to the same domain. For performance reasons, we do not recommend installing Essentials on the same machine hosting ArcGIS Server. As of version 4.5 of Essentials, we recommend you configure CORS in Essentials using the following new method. The legacy method to configure CORS in Essentials in previous versions is still supported, but you must only choose one method. The new method allows you to safely specify multiple origins. If the HTML5 Viewer is hosted on a separate domain to Essentials and you want to use the Geocortex Mobile App Framework, you must use the following new method to configure CORS. The steps in the new method to configure CORS are: 1. Remove the previous CORS configuration from Essentials You must only use a single method to configure CORS in Essentials, otherwise Essentials may not function properly. 2. Configure CORS in Essentials Assuming Essentials lacks any previous CORS configuration, running the Post Installer adds CORS configuration to your REST App Settings file, which you can then edit. 3. Configure trusted origins in your HTML5 viewers Add trusted origins to all viewer host files, such as Index.html. 13

19 Geocortex Essentials 4.5.Installation Guide To set up Cross-Origin Resource Sharing between Essentials and HTML5 viewers: These instructions assume that you are running Geocortex Viewer for HTML5 version 2.4 or newer. Step 1: Remove the previous CORS configuration from Essentials 1. In IIS Manager, expand the folders in the Connections panel and select the REST application. Default location of the REST application 2. In the center panel's IIS section, double-click HTTP Response Headers. A list of custom HTTP response headers appears. Note the details of any HTTP response headers you might want to keep. 3. Remove every HTTP response header with following name: Access-Control-Allow-Origin Access-Control-Allow-Methods Access-Control-Allow-Headers To remove an HTTP response header, right-click it and click Remove. 4. Close IIS Manager. Step 2: Configure CORS in Essentials 1. Open the Post-Installation Configuration application. 2. Click Finish. 3. Click OK. If prompted, sign in. 4. Click OK. The Post Installer adds a <Cors> section to the REST App Settings file, assuming you removed the previous configuration of CORS or have not previously configured CORS Latitude Geographics Group Ltd. All Rights Reserved.

20 3.4 Set Up Cross-Origin Resource Sharing (CORS) 5. Run a text editor as an Administrator. 6. In the text editor, open the REST App Settings file in the following location: {GE_Sites}\RestAppSettings.xml 7. Locate the <Cors> section. For example, your configuration might look similar to the following: <Cors> <AllowOrigins> <Origin Url=" /> </AllowOrigins> <AllowHeaders> <Header Name="Content-Type" />... </AllowHeaders> <AllowMethods> <Method Name="GET" />... </AllowMethods> </Cors> Do not remove <Origin Url=" />. This origin entry is required for the Geocortex Mobile App Framework to work properly. The Geocortex Mobile App Framework always uses the http URL scheme. 8. Add an origin entry for the domain where your HTML5 Viewer is hosted, and any other domains for which you want to enable CORS. For example: <Cors> <AllowOrigins> <Origin Url=" /> <Origin Url=" /> </AllowOrigins>... </Cors> The origin is sensitive to the URL scheme specified. If you use both http and https to access the viewer, ensure you include both forms of the URL. 9. Save the file. Step 3: Configure trusted origins in your HTML5 viewers 1. Run an HTML editor or text editor as an administrator. 2. Open the viewer's host file in the editor. The default host page for HTML5 viewers is Index.html. By default, the host file is located here: C:\inetpub\wwwroot\Html5Viewer\Index.html 15

21 Geocortex Essentials 4.5.Installation Guide 3. Find where the viewerconfig variable is defined: var viewerconfig = { Immediately before the section where the viewerconfig variable is defined, configure the Essentials origin to be a trusted origin. Use the geocortex._configdomains object to configure trusted origins. For example, if Essentials is hosted at geocortex._configdomains = { }; 5. Save the file. 6. Close the file. " true 7. Repeat these steps for each host file and each HTML5 viewer Latitude Geographics Group Ltd. All Rights Reserved.

22 4 About Installation 4 About Installation Installing Essentials is a three-step process: Install Essentials: This step installs Essentials's software components and tools. Install or Upgrade Geocortex Core: This step installs Geocortex Core, if it is not already installed. Essentials cannot run without Geocortex Core. If the server is running another Geocortex product that uses Geocortex Core, such as Geocortex Insight, then Geocortex Core is already installed. In this case, Geocortex Core is upgraded. You do not need to upgrade your other Geocortex products when Geocortex Core is upgraded they will work with the upgraded version of Geocortex Core. Perform Post-Installation Configuration: The post-installation configuration step creates the web components that Essentials requires, configures the information that Essentials requires to control sign-in to Manager, and deploys viewer templates. To install Essentials and Geocortex Core in a single-server system, you only need one installer the Essentials installer. The Geocortex Core installer and upgrader are bundled with the Essentials installer. When the Essentials installer completes, the Geocortex Core installer or upgrader runs if necessary. The Geocortex Essentials installer is a.msi file. You can download the installer from the Geocortex Support Center. For instructions, see Download the Software on page 22. Installing Essentials and Geocortex Core in a dual-server or multi-server system requires a standalone version of the Geocortex Core installer. You must run the standalone Geocortex Core installer before you run the Essentials installer. Setting up a dual-server or multi-server Essentials system is an advanced scenario. Contact Geocortex Support to arrange a consultation. The time required to complete the set-up depends on the complexity of your environment. Please ensure that you have adequate Support hours available. To install Essentials on a server that does not already have Essentials installed, follow the instructions in First-Time Installation on page 24. If the server already has Essentials installed, follow the instructions in Upgrading on page What the Installer Installs Software By default, the Essentials installer installs all of the software components. In general, there is no reason to install a subset of the components there is no harm in installing components that you do not use. The components are: Essentials REST API: Used by viewers to get information about the site and its services. You must install the REST API. Essentials Manager: Used to create and manage Essentials sites and their viewers. Identity Server: Provides security services for securing sites. 17

23 Geocortex Essentials 4.5.Installation Guide Desktop Tools: Workflow Designer: Used to program workflows complex, interactive GIS and business processes. Report Designer: Used to create report templates and print templates for Essentials's Reporting and Printing features. Language Tool: Used to translate Manager and the Silverlight Viewer. Geocortex Core: Provides software services to Geocortex products. If you are using other Geocortex products besides Essentials, Geocortex Core may already be installed on the server. If Geocortex Core is already installed, Essentials uses the existing instance. If Geocortex Core is not already installed, the Geocortex Core installer launches when the Essentials installer completes. Support Materials Essentials product documentation Sample sites 4.2 About Post-Installation Configuration Post-installation configuration includes a variety of tasks: Activate Essentials Licenses: When you install Essentials for the first time, you have 60 days to activate your Essentials licenses. During this time, you have the full Geocortex Essentials product to work with, not a subset. Configure Environmental Settings: Configure settings related to the environment that Essentials runs in web server settings, host names, cross-domain support, and Windows features. Add and Upgrade Viewer Templates: Deploy viewer templates to IIS and install viewer management packs so that you can use Manager to add viewers to your sites. Configure Sign-In Method: Configure the method for signing in to Manager Portal for ArcGIS, ArcGIS Online, or Windows. The sign-in method has implications for the types of content that you can use in your sites and the methods that you can use to secure your sites. For information, see Choose a Method to Sign In to Manager on page 53. You must run the Post Installer at least once after you install or upgrade Essentials. You can re-run the Post Installer at any time. For detailed information about what you can configure in the Post Installer, see Post-Installation Configuration on page Installation Options Installation Options for Essentials The Essentials installer provides several options that control such things as the naming and location of the installation Latitude Geographics Group Ltd. All Rights Reserved.

24 4.3.1 Installation Options for Essentials The options are: Unnamed vs. Named Instance: You can install multiple instances of a particular version of Essentials on one server by naming the instances. Typical vs. Custom Installation: The typical installation installs all the components and support materials. A custom installation can install a subset of the components. Both typical and custom installations can be named or unnamed. Default vs. Custom Locations: Both the typical installation and custom installation allow you to choose the location in the file system to install Essentials. Named Instances You can install multiple instances of a particular version of Essentials on one server. The ability to name instances makes this possible. Essentials does not place any limit on the number of named instances you can install. In addition to running multiple instances of one version of Essentials on a server, you can run multiple different versions, provided each version has a different name. If you do not specify a name when you perform the installation, the instance is unnamed. At most one instance of a particular version of Essentials can be unnamed. Instance names must be unique across versions. For example, you cannot have an instance of Essentials 4.0 named Public and an instance of Essentials 4.2 named Public installed on the same server. In a multi-server system, Essentials must either be installed under the same name on every server, or installed as the unnamed instance on every server. The Essentials installer operates on a single instance at one time. You must re-run the installer for each instance that you want to install or upgrade. 19

25 Geocortex Essentials 4.5.Installation Guide By default, the installer operates on the unnamed instance. To specify a named instance to install or upgrade, click the Options button in the installer's Welcome panel. Location of the Options button on the Essentials installer's Welcome panel If you select a named instance for the Essentials installer to install or upgrade, the instance's name appears in the installer's title bar. If there is no name in the title bar, then the installer is operating on the unnamed instance. The same is true of the Post Installer the Post Installer's title bar shows the name of the instance that is being configured. Each instance of Essentials has its own copy of the Post Installer. To modify the post-installation configuration for a particular instance of Essentials, you must run the Post Installer that belongs to that instance. Typical vs. Custom Installation If you select the typical installation in the Essentials installer, you can choose where to install Essentials, but not which components to install the typical installation installs all the software components and support materials. If you select the custom installation, you can choose which components to install and where to install them Installation Options for Geocortex Core When the Essentials installer completes, if Geocortex Core needs to be installed, the Geocortex Core installer launches automatically. The Geocortex Core installer has the following options: Geocortex Core Location: Select the location in the file system to install Geocortex Core. Data Folder Location: Select the location in the file system for Geocortex Core' data folder. The data folder has a Search subfolder that the Instant Search feature uses to store its indexed files. Instant Search reads from the storage drive where the index is stored. If you will be using the Instant Search feature, we recommend that you use a partition on a solid-state drive (SSD) for the data folder. For instructions on changing the data folder's location, see Install Essentials for the First Time on page Latitude Geographics Group Ltd. All Rights Reserved.

26 4.3.3 Installation Options for the Viewer Frameworks If you are not going to use Instant Search, there is no reason to change the location of the data folder. For more information about Instant Search, refer to the Geocortex Essentials Administrator Guide Installation Options for the Viewer Frameworks There are two ways to install a viewer framework: Use the Viewer Template: Use the Post Installer to add the viewer template, deploy the template to IIS, and install the management pack. Installing the management pack enables you to manage viewers using Essentials Manager. Install the Viewer Manually: Drop the viewer directly into a web server. The manual method is for advanced users with a good understanding of web servers and a willingness to manage their viewers by hand. Refer to the viewer's Administrator and Developer Guide for information. 4.4 Essentials Trial Versions The first time Essentials is installed on a server, it defaults to a 60-day evaluation period. This is true whether you have purchased Essentials or not. During the evaluation period, you have the full Geocortex Essentials product to work with, not a subset. If you do not activate Essentials within the 60-day evaluation period, the license status will change to Expired and you will not be able to use Essentials anymore. If you need more time for your evaluation, you can request an extension from your Account Manager. The expiry date for your Essentials trial is displayed on Manager's banner, as well as on the Post Installer's Activation panel. To prevent service interruptions, make sure you activate Essentials before you deploy it to a production server. To install a trial version of Essentials, follow the instructions in First-Time Installation on page 24 21

27 Geocortex Essentials 4.5.Installation Guide 5 Download the Software This section provides instructions for downloading: Geocortex Essentials: The Geocortex Essentials installer installs Geocortex Essentials and its components and tools, including Geocortex Essentials Manager, Geocortex Workflow Designer, Geocortex Report Designer, and the Geocortex Post-Installation Configuration tool. It also allows you to install Geocortex Core if Geocortex Core is not already installed on the server. To install Geocortex Core in a dual-server or multi-server system, you must use a standalone Geocortex Core installer instead of the Geocortex Core installer that is bundled with the Essentials installer. Setting up a dual-server or multi-server Essentials system is an advanced scenario. Contact Geocortex Support to arrange a consultation. The time required to complete the set-up depends on the complexity of your environment. Please ensure that you have adequate Support hours available. Geocortex Viewer for HTML5: (optional) The Geocortex Viewer for HTML5 is a framework for creating HTML5- based map viewers. Geocortex Viewer for Silverlight: (optional) The Geocortex Viewer for Silverlight Management Pack is a framework for deploying Silverlight-based map viewers. If you are installing Essentials for the first time, we recommend that you download also download the Geocortex Viewer for HTML5. To download the software: Step 1: Sign In to the Geocortex Support Center 1. Open the Geocortex Essentials Downloads page in the Geocortex Support Center. Step 2: Download the Geocortex Essentials Installer 1. In the Geocortex Essentials area, click the Download button. This downloads the current version of Essentials. To download an older version, click Previous Versions, click the version that you want to download, and click the Geocortex Essentials [version] link. 2. Save the file to your computer's storage drive. The file is called Geocortex-Essentials-[version].msi, where [version] is the version number. 3. Click the Release Notes (.pdf) hyperlink to download the release notes. The release notes summarize the new features, known issues, and other important information about this release of Essentials. In addition to installing Geocortex Essentials, the Essentials installer installs Geocortex Report Designer, Geocortex Workflow Designer, Geocortex Language Tool, and the product guides, so you do not need to download them individually from the Support Center Latitude Geographics Group Ltd. All Rights Reserved.

28 5 Download the Software Step 3: Download the Geocortex Viewer for HTML5 1. In the Geocortex Viewer for HTML5 area, click the Download button. This downloads the current version of the Geocortex Viewer for HTML5. To download an older version, click Previous Versions, click the version that you want to download, and click the Geocortex Viewer for HTML5 [version] link. 2. Save the file to your computer's storage drive. The file is a ZIP archive called Geocortex-Viewer-for-HTML5-[version].zip, where [version] is the version number. 3. Extract the files from the ZIP archive. The ZIP archive contains the HTML5 Viewer release notes and product guides, so you do not need to download them individually from the Support Center. Step 4: Download the Geocortex Viewer for Silverlight 1. In the Geocortex Viewer for Silverlight area, click the Download button. This downloads the current version of the Geocortex Viewer for Silverlight. To download an older version, click Previous Versions, click the version that you want to download, and click the Geocortex Viewer for Silverlight [version] link. 2. Save the file to your computer's storage drive. The file is a ZIP archive called Geocortex-Viewer-for-Silverlight-[version].zip, where [version] is the version number. 3. Extract the files from the ZIP archive. The ZIP archive contains the Silverlight Viewer release notes and product guides, so you do not need to download them individually from the Support Center. 23

29 Geocortex Essentials 4.5.Installation Guide 6 First-Time Installation The instructions in this section apply to single-server systems. To install the software in a system with more than one server, contact Geocortex Support to arrange a consultation. Please ensure that you have adequate Support hours available. This section explains how to install Essentials on a server that does not already have Essentials installed. If the server already has Essentials installed, follow the instructions in Upgrading on page 34. The procedure in this section explains how to: Install Essentials and its components and tools. Install Geocortex Core. Perform the most common post-installation configuration, specifically: Install viewer templates for the Geocortex Viewer for HTML5 and Geocortex Viewer for Silverlight. Configure hosts. Configure the method for signing in to Manager. The sign-in method has implications for the types of content that you can use in your sites and the methods that you can use to secure your sites. For information, see Choose a Method to Sign In to Manager on page 53. You must run the Post Installer at least once after you install Essentials, even if you do not install viewer templates or make any changes to the configuration when you click Finish, the Post Installer deploys the Essentials web applications to IIS. When you complete this procedure, you will be able to run Essentials on this server. If you want to do additional postinstallation configuration, such as activating your Essentials licenses or configuring cross-domain support, follow the instructions in Post-Installation Configuration on page 51. You should also reserve the ports that Geocortex Core uses and, if necessary, configure firewall access for Geocortex Core. For information, see Geocortex Core Ports and Firewall Access on page 87. This section does not provide instructions for setting up a reverse proxy. To run Essentials behind a reverse proxy, install Essentials, and then follow the instructions in Run Essentials Behind a Reverse Proxy on page Install Essentials for the First Time Before you begin the installation, download the installation packages following the instructions in Download the Software on page 22. For information about which components to install on a server, see Deployment on page Latitude Geographics Group Ltd. All Rights Reserved.

30 6.1 Install Essentials for the First Time To install Essentials for the first time: Step 1: Install Essentials 1. Run the Essentials installer that you downloaded from the Support Center. The Geocortex Essentials Setup Wizard launches. 2. If you want to give your Essentials installation a name: a. Click the Options button. Location of the Options button on the Essentials installer's Welcome panel b. In the Install a new instance of Geocortex Essentials box, type the instance name to use. c. Click Next. 3. Click Next. 4. Read the license agreement. If you agree to the terms of the license agreement, select the I accept the terms in the License Agreement check box, and then click Next. 5. Do one of the following: Install the Typical Installation The typical installation installs all software components. a. Click Typical. b. If you want to change the location in the file system where Essentials is installed, type in the path, or click Change to browse to the location. c. Click Next. 25

31 Geocortex Essentials 4.5.Installation Guide Install a Custom Installation The custom installation allows you to choose which components to install. a. Click Custom. b. If you do not want to install a component, click the icon beside the component and deselect it. This prevents the component from being installed. c. If you want to change the location in the file system where Essentials is installed, type in the path, or click Change to browse to the location. d. Click Next. 6. Click Install. The Setup Wizard installs the software. When the installation is complete, the Setup Wizard's final panel displays. 7. Make sure the Launch Post-Installation Configuration check box is selected. 8. Click Finish. The Essentials Setup Wizard closes. Step 2: Install Geocortex Core If Geocortex Core is not already installed on the server, the Geocortex Core Setup Wizard launches. Follow the instructions below to install Geocortex Core. If Geocortex Core is already installed but Essentials needs a newer version, Geocortex Core will be upgraded. Wait until the upgrade completes, skip the remainder of this step, and then continue at Step 3: Install the Viewer Templates (recommended) on page Click Next. 2. Click Next. This accepts the default installation location. 3. If you want to change the location in the file system where the data files and log files are stored, type in the path, or click Change to browse to the location. If you are going to use Instant Search, the data folder can get very large. Running out of disk space interferes with indexing. Make sure your server meets the Requirements for Servers Running Instant Search on page Click Next. 5. Click Install. 6. Click Finish. The Geocortex Core Setup Wizard closes Latitude Geographics Group Ltd. All Rights Reserved.

32 6.1 Install Essentials for the First Time Step 3: Install the Viewer Templates (recommended) If you do not want to install the viewer templates now, you can install them later. For instructions, see Install Viewer Templates on page 78. Continue the post-installation configuration at Step 5: Configure the Sign-In Method on page 28. If you have not yet downloaded the viewers' installation packages, download them from the Geocortex Support Center. For instructions, see Download the Software on page In the Post Installer's side panel, click Configure Viewer Templates. 2. Click Add. 3. Browse to the folder where you extracted the files from the installation package. 4. Select the template file (.vte file), and then click Open. You are prompted to install the management pack. 5. Click Yes. You are prompted to deploy the template to an IIS virtual directory. 6. Click Yes. The Deploy Template to IIS dialog box opens. 7. If the virtual directory listed in the Select Virtual Directory box already exists, type a name for a new virtual directory. Each viewer template must be deployed to a virtual directory that does not yet exist in the selected website. 8. Click Deploy, and then close the success message that displays. The template is listed in the Installed Templates area. Step 4: Configure Hosts You must configure the host names that browsers and other web applications will use to reach the Essentials web applications. For information, see About Hosts on page Open the list of hosts for the desired website: REST API: To configure the host names for the website that the REST API uses, click Configure Geocortex Essentials REST API in the Post Installer's side panel, and then click Hosts. Manager: To configure the host names for the website that Manager uses, click Configure Geocortex Essentials Manager in the Post Installer's side panel, and then click Hosts. Manager uses Windows Authentication by default and may require the computer name as a host name to allow an administrator to log in on the server. Identity Server: To configure the host names for the website that Identity Server uses, click Configure Geocortex Identity Server in the Post Installer's side panel, and then click Hosts. If any two of the web applications use the same website, you can access the list of hosts from either panel there is only one list of hosts for a particular website. 27

33 Geocortex Essentials 4.5.Installation Guide 2. Add Hosts: a. In the blank box at the bottom of the list, copy or type the host name that you want to add. If you are not using the default port (port 80 for HTTP, port 443 for HTTPS), make sure to include the port, for example, host.domain.com:7777. b. Click the down arrow in the Type box and select the protocol or If you want Essentials to accept both HTTP and HTTPS, without upgrading HTTP to HTTPS, add both versions of the URL and make sure that the HTTP version is higher in the list than the HTTPS version. c. Continue adding host names until you have added all the names that you want to allow. 3. Remove Hosts: a. If you do not want to allow a default host name, click the Remove tool beside the name to remove it. 4. Order the List: a. Click beside a host name that you want to move and drag the name to its new position in the list. b. Continue dragging and dropping host names until the list is ordered the way that you want it. 5. Click OK. Step 5: Configure the Sign-In Method If you do not configure the sign-in method, the default sign-in method, Windows Authentication, will be used. You can change the sign-in method later. For instructions, see Install Viewer Templates on page 78. Continue the postinstallation configuration at Step 6: Complete the Post-Installation Configuration on page 32. There are three options for how administrators sign in to Manager: Portal for ArcGIS: See Upgrading Essentials on page 34. ArcGIS Online: See Upgrading Essentials on page 34. Windows: See Upgrading Essentials on page 34. Option 1: Configure Sign-In Using Portal for ArcGIS 1. In the Post Installer, click Configure Sign-In Options in the side panel. 2. Beside Sign in using, select ArcGIS. 3. In the URL box, type or paste the URL for your portal. If you deployed Portal for ArcGIS to the default location, the URL will be similar to Replace server.domain.com with the fully qualified host name of the server that hosts Portal for ArcGIS. 4. Click Test. The Post Installer connects to the URL. When the connection succeeds, the Post Installer displays a hyperlink to your portal. 5. Click the hyperlink to open your portal in a browser Latitude Geographics Group Ltd. All Rights Reserved.

34 6.1 Install Essentials for the First Time 6. Sign in to your portal. 7. In your portal, create a Portal for ArcGIS application for the Post Installer to use. The Post Installer will use this application to add two web mapping applications to your portal. Essentials and Manager use the web mapping applications to access your private portal content. a. Click Add Item. b. Select An application from the The item is drop-down list. c. Select Application. d. In the Title box, enter a title for the application, for example, Geocortex Post Installer. e. In the Tags box, add a search tag to help locate this application, for example, Geocortex. Add a Portal for ArcGIS application for the Post Installer to use f. Click Add Item. The application's details page opens. 29

35 Geocortex Essentials 4.5.Installation Guide Details page for the Geocortex Post Installer application in Portal for ArcGIS In the screen capture above, the App Registration area has a Registered Info hyperlink. This indicates that the application was registered automatically when you added it. 8. If the App Registration area has a Register hyperlink instead of a Registered Info hyperlink, you must register the application manually: a. In the App Registration area, click Register. b. In the App Type drop-down list, select Multiple. c. In the Redirect URI box, type or paste the following URI: d. Click Add. urn:ietf:wg:oauth2.0:oob e. Click Register. The dialog box closes and the application is registered. Registration creates the application's ID and secret, which are used like a user name and password. 9. In the App Registration area, click Registered Info. You will need the App Registration information when you finish the post-installation configuration. App Registration information in Portal for ArcGIS Latitude Geographics Group Ltd. All Rights Reserved.

36 6.1 Install Essentials for the First Time 10. In the Post Installer, click Finish. 11. In the dialog box, copy and paste the App ID and App Secret from Portal for ArcGIS to the Post Installer. The App Secret is encrypted in Essentials. Essentials does not share this information with any other application. 12. Click OK. You are prompted to sign in to Portal for ArcGIS. 13. Sign in to Portal for ArcGIS using the same account that you signed in with when you created the application. The Post Installer sets up access to your private Portal for ArcGIS content for Essentials, and then signs you out of Portal for ArcGIS. If you clear the Remember Me check box when you sign in, you will have to enter the App ID and App Secret each time you run the Post Installer. 14. Follow the prompts to close the Post Installer. Continue the post-installation configuration at Step 6: Complete the Post-Installation Configuration on page 32. Option 2: Configure Sign-In Using ArcGIS Online 1. In the Post Installer, click Configure Sign-In Options in the side panel. 2. Beside Sign in using, select ArcGIS. 3. Do one of the following: In the URL box, type or paste the ArcGIS Online URL where you want end users to sign in: Enter the URL for Your Organization's ArcGIS Online Portal 1. In the URL box, type or paste the URL for your organization's ArcGIS Online portal. For example, Replace organization with the name of your organization's ArcGIS Online subdomain. Enter URL of ArcGIS Online's Home Page 1. In the URL box, type or paste the URL for ArcGIS Online's home page. The URL is Alternatively, you can click the hyperlink to enter the URL. 4. Click Test. The Post Installer connects to the URL. When the connection succeeds, the Post Installer displays a hyperlink for the URL. You will be prompted to sign in to ArcGIS Online when you finish the post-installation configuration. This allows the Post Installer to set up access to ArcGIS Online for Essentials. Continue the post-installation configuration at Step 6: Complete the Post-Installation Configuration on page

37 Geocortex Essentials 4.5.Installation Guide Option 3: Configure Sign-In Using Windows 1. In the Post Installer, click Configure Sign-In Options in the side panel. 2. Beside Sign in using, select Windows. 3. In the Group box, type the name of the Windows group that users must belong to in order to sign in to Manager. The default value is the built-in administrators group. Step 6: Complete the Post-Installation Configuration This step is required, even if you have not performed any configuration in the Post Installer. In this step, the Post Installer deploys the Essentials web applications to IIS. 1. Click Finish. 2. If you configured one of the ArcGIS methods of signing in to Manager, follow the instructions for the method that you configured: Portal for ArcGIS 1. In the App Registration dialog box, copy and paste the App ID and App Secret from Portal for ArcGIS to the Post Installer, and then click OK. You are prompted to sign in to Portal for ArcGIS. The application's secret is encrypted in Essentials. Essentials does not share this information with any other application. 2. Sign in to Portal for ArcGIS using the same account that you signed in with when you created the application. The Post Installer sets up access to your private Portal for ArcGIS content for Essentials, and then signs you out of Portal for ArcGIS. If you clear the Remember Me check box when you sign in, you will have to enter the App ID and App Secret each time you launch the Post Installer. ArcGIS Online 1. In the App Registration dialog box, sign in to ArcGIS Online. The Post Installer sets up access to your private ArcGIS Online content for Essentials, and then signs you out of ArcGIS Online. The information gathered from ArcGIS Online is encrypted in Essentials. Essentials does not share this information with any other application. You have now completed the installation Latitude Geographics Group Ltd. All Rights Reserved.

38 6.2 Get Started with Essentials 6.2 Get Started with Essentials To learn about Essentials and begin creating sites, refer to the Geocortex Essentials Administrator Guide. You can download the Administrator Guide from the Geocortex Support Center. The Administrator Guide has a Quick Start section that steps you through creating a simple site, adding a viewer, and launching the viewer in a browser to view the site you created. The Quick Start also has a section on exploring the sample site that ships with Essentials. If you are new to Essentials, the Quick Start section is a good place to start. 33

39 Geocortex Essentials 4.5.Installation Guide 7 Upgrading Upgrading installs the same components in the same location as the existing installation. You can upgrade Essentials and the viewers independently you can upgrade only Essentials, or only the viewers, or both Essentials and the viewers. To use certain features, you may have to upgrade both Essentials and the viewers. For best results, we recommend upgrading both Essentials and the viewers. To find out the Essentials version that a particular viewer version works with best, see the "Geocortex Essentials Requirements" section in the viewer's documentation. Usually, your custom files such as sites, viewers, and projects, are upwardly compatible after you upgrade the software, the old files still work. Occasionally, improvements to the software break upward compatibility. In this case, you may have to perform some manual steps to complete the upgrade. For information, see Essentials Versions that Require Manual Steps on page 34 and Viewer Versions that Require Manual Steps on page Upgrading Essentials To upgrade Essentials, you run the installer for the version that you want to upgrade to. The installer will detect your existing installation and offer to perform an upgrade instead of a new installation. After the installer finishes, you must run the Post Installer. This allows the Post Installer to update the web configuration. For some upgrades, you may have to perform some additional, manual steps. For information, see Essentials Versions that Require Manual Steps on page 34. Usually you do not have to restart the server after upgrading. In rare cases, you may have to restart the server for the upgrade to complete. Geocortex Essentials is not engineered to automatically upgrade load balanced deployments. Manual steps may be required to upgrade Essentials in a load-balanced, multi-server environment. If you need help upgrading a multi-server deployment, contact Geocortex Support. The time required to complete the upgrade depends on the complexity of your environment. Please ensure that you have adequate Support hours available Essentials Versions that Require Manual Steps Depending on the version that you are upgrading from, you may have to perform one or more manual steps when you upgrade Essentials. For example, you may have to update a feature's configuration to make the feature work in the new version of Essentials, or you may have to manually update the IIS configuration so Essentials can take advantage of improvements to IIS. For some versions, you do not have to perform any manual steps. The list below lists the versions of Essentials that may require manual steps when you upgrade to Essentials 4.5.x. Scan the list to determine which steps apply to you, if any. To find out more about a step, click the link. Note that you may have to perform more than one of the steps in the list. Upgrading from the following versions may require manual steps: Versions Older than 4.5: Add Tables of existing map services. See Upgrade Essentials from a Version that is Older than 4.5 on page 35. Versions Older than 4.3: Update workflows to work with nullable results from Date Picker form items. See Upgrade Essentials from a Version that is Older than 4.3 on page Latitude Geographics Group Ltd. All Rights Reserved.

40 7.1.1 Essentials Versions that Require Manual Steps Versions Older than 4.2: Configure sign-in and hosts, upgrade viewers, and update application pools. See Upgrade Essentials from a Version that is Older than 4.2 on page 36. Versions Older than 3.15: Upgrade custom Web.config files. See Upgrade Essentials from a Version that is Older than 3.15 on page 36. Versions Older than 3.6: Update application pools. See Upgrade Essentials from a Version that is Older than 3.6 on page x Versions: Upgrade Essentials Security. See Upgrade Essentials from Version 3.x on page 37. Upgrade Essentials from a Version that is Older than 4.5 In versions prior to Essentials 4.5, related table data automatically appeared in the HTML5 Viewer. As of Essentials 4.5, you can now explicitly choose which tables of a map service to include. By default, when a map service is added to a map, all of its tables are included. However, for existing map services, you must manually add the tables. To add a table to an existing map service: 1. In Manager, edit the site that you want to configure, and then click Map in the side panel. 2. Edit the map service that contains the table. 3. Click the Add/Remove Tables tab. 4. To include one or more tables, select the tables in the Excluded Tables column, and then click the» button. To exclude one or more tables, select the tables in the Included Tables column, and then click the «button. To select multiple tables, hold the Ctrl key down while selecting tables. 5. Click Submit Layer Changes. 6. Click Save Site. For more information, see "ArcGIS Tables" in the Geocortex Essentials Administrator Guide. Upgrade Essentials from a Version that is Older than 4.3 Starting in Essentials 4.3, Date Picker form items in workflows return a System.Nullable<System.DateTime> result, instead of a System.DateTime. If you have older workflows that use System.DateTime output arguments for Date Pickers, the workflows will continue to work as before, as long as you do not modify the form in Workflow Designer. Modifying the form changes the output argument's type to System.Nullable<System.DateTime>. You may have to update your workflow to work with the new output type. To prevent future problems, you may want to update all your forms and workflows to use System.Nullable<System.DateTime> Date Picker results. This saves you from having to remember to do it later, when you change a form. 35

41 Geocortex Essentials 4.5.Installation Guide Upgrade Essentials from a Version that is Older than 4.2 If you are upgrading from a version of Essentials that is older than 4.2, there are several manual steps that you must take: Configure the Sign-In Method: Starting in Essentials 4.2, you must configure the method that administrators will use to sign in to Manager. Depending on the method you choose, administrators will sign in using an ArcGIS Online account, a Portal for ArcGIS account, or a Windows account. The sign-in method has implications for the types of content that you can use in your sites and the methods that you can use to secure your sites. For information, see Choose a Method to Sign In to Manager on page 53. Before Essentials version 4.2, you could add ArcGIS Online security providers in Manager. Starting in Essentials 4.2, you can no longer add ArcGIS Online security providers. If you have an existing (pre-4.2) ArcGIS Online security provider, the security provider and its permissions will continue to work when you upgrade to Essentials 4.2 or newer, as long as you configure the ArcGIS Online sign-in method. If you have a pre-4.2 ArcGIS Online security provider and you configure one of the other sign-in methods (Portal for ArcGIS or Windows) when you upgrade to Essentials 4.2 or newer, you will lose your ArcGIS Online security provider and all of its associated permissions. If you do not have a pre-4.2 ArcGIS Online security provider and you want to use ArcGIS Online to secure your sites, configure the ArcGIS Online method of signing in to Manager the Post Installer will create an ArcGIS-type security provider that works the same as pre-4.2 ArcGIS Online security providers. Starting in version 4.2, the only way to create a security provider that uses ArcGIS Online to authenticate end users is by configuring the ArcGIS Online sign-in method. Configure Hosts: Starting in Essentials 4.2, you must register the hosts through which communications with Essentials are routed. Follow the instructions in Configure Hosts on page 75. Upgrade Viewers: Upgrade the Geocortex Viewer for HTML5 and the Geocortex Viewer for Silverlight to a version that works with the Essentials version you are upgrading to. To find out the viewer version that the Essentials version works with, see the Geocortex Essentials Release Notes. Follow the instructions in Upgrading Viewers on page 40. Update Application Pools: Starting in Essentials 4.2, the Essentials and Manager application pools use the built-in IIS identity, ApplicationPoolIdentity. Older versions of Essentials create local users for the application pools. Upgrading Essentials does not update the identities. As a result, you may be denied access when you try to sign in to Manager. To prevent this, open IIS Manager and configure the EssentialsAppPool4 and EssentialsAdministrationAppPool4 application pools to run as the ApplicationPoolIdentity user. Afterward, re-run the Post Installer and click Finish, so the Post Installer can detect the change. Upgrade Essentials from a Version that is Older than 3.15 Depending on the upgrade history of your Essentials installation, upgrading may overwrite the Essentials REST and Manager Web.config files. If you are upgrading from a version that is older than 3.15, you will have to make backups of the old Web.config files and then manually copy your changes to the new Web.config files after upgrading. If you are upgrading from Essentials 3.15 or newer, the installer is capable of automatically carrying forward modifications from the old Web.config files to the new Web.config files Latitude Geographics Group Ltd. All Rights Reserved.

42 7.1.1 Essentials Versions that Require Manual Steps To upgrade the Web.config files if you have customized them: Step 1: Back Up the Web.config Files You must do this before you upgrade Essentials. 1. If you are upgrading from a version of Essentials that is older than 3.15, and you have modified one or both of the Web.config files, make backups of the modified files. The Web.config files are: Essentials REST API Web.config: If you installed Essentials in the default location, Essentials's Web.config file is here: C:\Program Files (x86)\latitude Geographics\Geocortex Essentials\ [instance]\rest Elements\REST\Web.config Manager Web.config: If you installed Essentials in the default location, Manager's Web.config file is here: C:\Program Files (x86)\latitude Geographics\Geocortex Essentials\ [instance]\rest Elements\Manager\Web.config Step 2: Carry Forward your Web.config Customization Do this after you upgrade Essentials. 1. Run a text editor as an administrator. 2. Open the backup copy of the Web.config file and the upgraded version of the Web.config file in the text editor. 3. Copy your modifications from the backup file to the corresponding position in the upgraded file. 4. Save the upgraded file. 5. Repeat these steps for the other Web.config file, if it also has modifications that you want to carry forward. Upgrade Essentials from a Version that is Older than 3.6 Before version 3.6, all Essentials web applications ran in 32-bit application pools in Classic mode. Upgrading Essentials does not update the application pools. If you upgrade from a version of Essentials that is older than 3.6, we recommend that you use 64-bit Integrated application pools unless you have a specific reason to use some other mode. Upgrade Essentials from Version 3.x If you have one or more 3.x sites that are secured, you must take additional steps to carry forward your security configuration. For instructions, see the Geocortex Knowledge Base article Upgrade Security in Essentials from 3.x to 4.x. 37

43 Geocortex Essentials 4.5.Installation Guide Upgrade Essentials To upgrade to a version of Essentials other than 4.5.x, follow the instructions for the version that you are upgrading to. You can download other versions of the Installation Guide from the Essentials Downloads page in the Geocortex Support Center. To upgrade Essentials: Step 1: Before You Begin 1. Download the Essentials installer for the version of Essentials that you want to upgrade to. For instructions, see Download the Software on page Read Essentials Versions that Require Manual Steps on page 34 to find out if you need to perform any manual steps as part of the upgrade. Sometimes you must perform manual steps before you upgrade Essentials, so it is important to read this section before you begin the upgrade. 3. Perform any manual steps that must be done before you begin the upgrade. Step 2: Run the Installer 1. Run the Essentials installer. The installer is Geocortex-Essentials-[version].msi, where [version] is the version of Essentials that you want to upgrade to. The Geocortex Essentials Setup Wizard launches. The Welcome panel indicates that the installer will upgrade the existing installation of Essentials. Welcome panel with message about upgrading Latitude Geographics Group Ltd. All Rights Reserved.

44 7.1.2 Upgrade Essentials 2. If you want to upgrade a named instance of Essentials a. Click Options. b. Select Upgrade an existing instance of Geocortex Essentials. c. Select the instance that you want to upgrade from the drop-down list. 3. Click Next. 4. Read the license agreement. 5. If you agree to the terms, select the I accept the terms in the License Agreement check box and click Next. 6. Click Install. 7. When the installer completes, make sure the Launch Post Installation Configuration check box is selected, and then click Finish. The Post Installer launches. You must run the Post Installer at least once after upgrading. This allows the Post Installer to update the web configuration. Step 3: Run the Post-Installer 1. Follow the instructions that apply to you: Upgrade from Essentials 4.2 or Newer If you want to upgrade your viewers, follow the instructions in Upgrading Viewers on page 40. If you do not want to upgrade your viewers at this time, click Finish and follow the prompts to close the Post Installer. Upgrade from a Version of Essentials that is Older than Configure the method to sign in to Manager. The sign-in method has implications for the types of content that you can use in your sites and the methods that you can use to secure your sites. For information, see Choose a Method to Sign In to Manager on page 53. If you have an existing (pre-4.2) ArcGIS Online security provider, you must configure the ArcGIS Online sign-in method. Otherwise, you will lose your ArcGIS Online security provider and all of its associated permissions. The methods are: Portal for ArcGIS: Follow the instructions in Configure Manager Sign-In Using Portal for ArcGIS on page 56. ArcGIS Online: Follow the instructions in Configure Manager Sign-In Using ArcGIS Online on page

45 Geocortex Essentials 4.5.Installation Guide Windows: Follow the instructions in Configure Manager Sign-In Using Windows on page 62. To enable single sign-on, make sure that Windows Authentication is enabled in IIS for the RestManager application. Follow the instructions in Configure Windows Features on page Configure the hosts through which communications with Essentials are routed. For instructions, see Configure Hosts on page Upgrade the Geocortex Viewer for HTML5 and the Geocortex Viewer for Silverlight. For instructions, see Upgrading Viewers on page Update the application pools that Essentials REST and Essentials Manager use. For instructions, see Update Application Pools (page 36). Step 4: Perform Manual Steps 1. If you have manual steps to perform, do them now. 7.2 Upgrading Viewers The method that you use to upgrade a viewer depends on how you installed the viewer: Installed Using a Viewer Template: You can use Essentials to upgrade the viewer. Read About Upgrading Viewers Using Essentials on page 40. Read Viewer Versions that Require Manual Steps on page 41. Follow the instructions in Upgrade Viewers Using Essentials on page 45. Installed Manually: If you installed the viewer by dropping it directly into a web server, you must upgrade it manually back up and remove the old viewer, install the new viewer, and then manually copy over any changes from the backup files to the new files. Read Viewer Versions that Require Manual Steps on page 41 to see if you need to perform any manual steps About Upgrading Viewers Using Essentials There are two main steps to upgrading a viewer using Essentials: Upgrade the Template: See Step 1: Upgrade the Viewer Template on page 41. Upgrade your Configured Viewers to Use the New Template: See Step 2: Upgrade Configured Viewers on page 41. Upgrading the template removes the old template. This means that the viewers are unusable between the time you upgrade the template and the time you upgrade the configured viewers they cannot be launched or edited during this time Latitude Geographics Group Ltd. All Rights Reserved.

46 7.2.2 Viewer Versions that Require Manual Steps Step 1: Upgrade the Viewer Template To upgrade a viewer template, you use the Post Installer's Upgrade function. The Upgrade function partially automates the process of upgrading the viewer files that are deployed to the web server. When you upgrade a viewer, you want to take advantage of the new features and improvements that the new template offers. At the same time, you want to preserve any changes that you have made to the viewer, such as customizations to. The Upgrade function examines each file in your existing viewer so your customizations can be preserved: Installed File Not Customized: Viewer files that you have not customized are replaced when you upgrade. This means that you benefit from any changes that have been made in the new versions of these files. Installed File Customized, Unchanged in New Template: If you have modified a viewer file, but the file has not changed in the new release, then the installed version of the file is preserved. This preserves your customization. Installed File Customized, Changed in New Template: If you have modified a viewer file and the file has changed in the new release, the Upgrade function allows you to decide how to upgrade the file keep the installed file, replace the installed file with the new version of the file, or merge the two versions together. If the server has WinMerge installed, the Upgrade function uses WinMerge to show a side-by-side comparison of the two versions of the file. You can use WinMerge's merge functions to selectively merge the differences. If WinMerge is not installed, you must merge the files manually, by editing them and copying over the changes. WinMerge is not installed with Essentials. If you want to use WinMerge to compare and merge files, you must install WinMerge before you perform the upgrade. You can download WinMerge for free from New Custom Files: If you have added new files to the viewer, upgrading preserves them. For example, if you have created custom modules, the files that implement the modules are not affected by upgrading they remain in the same location, with the same names, as before the upgrade. By default, the Upgrade function deploys the upgrade to the same location as the existing viewer. Deploying to the same location ensures that the viewer's URLs stay the same, so you do not need to update the launch links and URLs that you provide to users. You can change the location if you want. If you deploy the viewer to a different location, you will have to update the launch links and URLs that you provide to users. The Upgrade function creates a backup of the existing viewer. Step 2: Upgrade Configured Viewers After you upgrade the template, you must upgrade the viewers of that type (HTML5 or Silverlight) that are configured in your sites. You cannot run or edit the viewers until you have upgraded them to use the new template. Manager has an Upgrade Viewers function that enables you to upgrade all your configured viewers with a single click. Alternatively, you can upgrade viewers individually Viewer Versions that Require Manual Steps Depending on the version that you are upgrading from, you may have to perform one or more manual steps when you upgrade a viewer. For some versions, you do not have to perform any manual steps. 41

47 Geocortex Essentials 4.5.Installation Guide The list below lists the viewer versions that may require manual steps. Scan the list to determine which steps apply to you, if any. To find out more about a step, click the link. Note that you may have to perform more than one of the steps in the list. Upgrading from the following versions may require manual steps: Geocortex Viewer for HTML5: Versions Older than 2.6: Upgrade currency formatting in charts. See Upgrade the HTML5 Viewer from a Version that is Older than 2.6 on page 42. Versions Older than 2.5: Upgrade custom Offline content. See Upgrade the HTML5 Viewer from a Version that is Older than 2.5 on page 42. Versions Older than 2.4: Update viewer URLs and configure trusted domains. See Upgrade the HTML5 Viewer from a Version that is Older than 2.4 on page 43. Geocortex Viewer for Silverlight: 1.x Versions: Update the configuration for User Layer Addition. See Upgrade the Silverlight Viewer from Version 1.x on page 45. Upgrade the HTML5 Viewer from a Version that is Older than 2.6 Starting in HTML5 Viewer 2.6, you can configure the currency type when you select the Currency format for the chart's category, series source, and series aggregator. By default, the currency type is based on the location of the Essentials server. For example, if the server is in the USA, the currency type is US dollars. If a chart's data is stored in a different currency than the currency of your server's locale, you must edit the chart and set the three new Currency settings to the correct currency type. This ensures that the viewer interprets the chart's data correctly. For information on setting the Currency format for a chart's category, see "Category Setup (Horizontal Axis)" in the Geocortex Essentials Administrator Guide. For information on setting the Currency format for a series source and series aggregator, see "Series Setup (Vertical Axis)" in the Geocortex Essentials Administrator Guide. Upgrade the HTML5 Viewer from a Version that is Older than 2.5 As of HTML5 Viewer 2.5, the cache manifest no longer exists. Instead, all content within the following folders will be made available offline in the Geocortex Mobile App Framework: The folder where the HTML5 Viewer is hosted. For example, C:\inetpub\wwwroot\Html5Viewer. The virtual directory of the HTML5 Viewer on the Essentials server. For example, C:\Program Files (x86)\latitude Geographics\Geocortex Essentials\Default\REST Elements\Sites\MySite\Viewers\MyViewer\VirtualDirectory. If you have customized your cache manifest file, ensure all of your content is within these two folders so it will be available in the Geocortex Mobile App Framework. The existing cache manifest is located in the viewer's virtual directory at: Resources\Config\CacheManifestConfig.xml Latitude Geographics Group Ltd. All Rights Reserved.

48 7.2.2 Viewer Versions that Require Manual Steps Upgrade the HTML5 Viewer from a Version that is Older than 2.4 This section applies to you if you are upgrading from a pre-2.4 version of the HTML5 Viewer and you have not performed the steps for Geocortex Viewer for HTML5 Security Update If you performed the Security Update, or you installed the Geocortex Viewer for HTML5 for the first time in version 2.4 or newer, you can skip this section. You may have to perform one or more of the following steps to complete a successful upgrade to Geocortex Viewer for HTML Perform these steps after you have upgraded the HTML5 Viewer. Upgrading the Viewer replaces the Viewer's Framework.js file with a more secure version of the file. The steps are: 1. If you use the configbase parameter in viewer URLs, update the URLs to use fully qualified domain names. If you have not updated your viewer URLs, the URLs may not work in Geocortex Viewer for HTML5 2.4 or newer. Follow the instructions in Load Files from the Same Domain on page If you use CORS to allow cross-origin resource sharing between Essentials and your HTML5 viewers, configure the viewers' trusted domains. If you have not configured trusted domains for your viewers, the viewers may not work in Geocortex Viewer for HTML5 2.4 or newer. Follow the instructions in Load Files from a Different Domain on page 44. Load Files from the Same Domain Geocortex HTML5 2.4 and newer viewers will not load a configuration file that is hosted in the same domain as the viewer if the domains do not match exactly. For example, the following URL will fail to launch a version 2.4 or newer HTML5 viewer because the viewer's domain, myserver, does not exactly match the configuration's domain, myserver.mydomain.com, even though they map to the same machine: Invalid viewer URL with non-matching domains If your environment is configured to produce URLs with domains that do not match, you may have to update the configuration to make the URLs work with version 2.4 and newer. Specifically, if CORS is set up on your server or your server is behind a proxy, you must update the configuration. We recommend that you use fully qualified domains in your URLs, even if you are not using CORS or a proxy. The procedure below updates the viewer launch links that appear in Manager. In addition to updating the viewer launch links in Manager, you must update the launch links that you provide to end users. 43

49 Geocortex Essentials 4.5.Installation Guide To update the launch links in Manager to use fully qualified domains: 1. Update the HTML5 Viewer framework's base launch link: a. Run an XML editor or text editor as an administrator. b. Open the RestManagerAppSettings.xml file in the editor. By default, the file is located here: C:\Program Files (x86)\latitude Geographics\Geocortex Essentials\ [instance]\rest Elements\Manager\App_Data\RestManagerAppSettings.xml c. In the HTML5 Viewer's ViewerFramework element, update the Url attribute to use a fully qualified domain, for example: <ViewerFramework ProductID="..." TemplateID="Html5Viewer_2_6" Url=" /> d. Save the file. 2. Update the Essentials URL: a. Open Manager's web.config file in the editor. By default, the file is located here: C:\Program Files (x86)\latitude Geographics\Geocortex Essentials\ [instance]\rest Elements\Manager\web.config b. In the appsettings element, find the add element for the EssentialsUrl key. c. Update the value attribute to use a fully qualified domain, for example: <add key="essentialsurl" value=" /> d. Save the file. Load Files from a Different Domain If you use CORS to allow cross-origin resource sharing between Essentials and HTML5 viewers, starting in version 2.4 of the HTML5 Viewer, you must configure trusted domains for your viewers. The trusted domains list is configured in a viewer's host page. You must configure the trusted domains for each viewer. To specify trusted domains for an HTML5 viewer: 1. Run an HTML editor or text editor as an administrator. 2. Open the viewer's host file in the editor. The default host page for HTML5 viewers is Index.html. By default, the host file is located here: C:\inetpub\wwwroot\Html5Viewer\Index.html 3. Find where the viewer is created: var viewer = new geocortex.essentialshtmlviewer.viewerapplication (viewerconfig.viewerconfiguri, null, viewerid); Latitude Geographics Group Ltd. All Rights Reserved.

50 7.2.3 Upgrade Viewers Using Essentials 4. Immediately before the section where the viewer is created, specify your trusted domain(s) using the geocortex._configdomains object, for example: geocortex._configdomains = { }; 5. Save the file. " true 6. Repeat these steps for each host file in each HTML5 viewer. Upgrade the Silverlight Viewer from Version 1.x If you have one or more Silverlight 1.x viewers that have User Layer Addition enabled, and you configured map service providers for User Layer Addition, you must take additional steps to carry forward your User Layer Addition configuration to version 2.0 or newer. For instructions, refer to the Geocortex Knowledge Base article Upgrade User Layer Addition from Silverlight Viewer 1.x to 2.x Upgrade Viewers Using Essentials If you installed a viewer framework manually, you cannot use this method to upgrade the viewer. Step 1: Upgrade a Viewer Template To upgrade a viewer template using Essentials: Before you begin, you must download the installation package for the version of the viewer framework that you want to upgrade to. See Download the Software on page 22. Upgrading a viewer template removes the existing template. 1. In the Post Installer, click Configure Viewer Templates in the side panel. 2. In the Installed Templates area, click the template that you want to upgrade. The template management buttons show. 45

51 Geocortex Essentials 4.5.Installation Guide Location of the Upgrade button for upgrading a viewer template 3. Click Upgrade. 4. Browse to the location where you extracted the installation package. 5. Select the template file, and then click Open. The Upgrade Template dialog box opens. Example of the Upgrade Template dialog box 6. Viewer Location: If the folder location given in the Viewer Location box is not where you want to deploy the upgrade, click Browse, select the folder where you want to deploy the upgrade, and then click OK. By default, the Viewer Location box shows the location where the viewer was installed. If you moved the viewer after installing it, you will have to change the location. 7. Backup Location: If you want to change the folder where the upgrader puts the backup of the old viewer, click Browse, select the folder where you want to put the backup, and then click OK Latitude Geographics Group Ltd. All Rights Reserved.

52 7.2.3 Upgrade Viewers Using Essentials 8. Modified Files: If there are modified files, review each file and indicate whether you want to keep the existing version of the file or overwrite the existing file with the new version. A file appears in the list only if there are software updates in the new version of the file, and you have customized the existing version of the file. This step gives you the opportunity to merge your modifications into the new file before the upgrader overwrites the installed file, thus preserving your customization. Alternatively, you could merge the software updates into the existing file and use the Keep Existing action. The easiest approach is to merge into whichever file has the most changes. a. Merge your modifications to the new file using one of the following methods: If you have WinMerge installed, click the Compare button to review the differences between the two files in WinMerge, and then use WinMerge's Merge function to merge your customization into the new file. Save your merges. If you do not have WinMerge installed, perform your merges manually by copying and pasting your customizations into the new file using a text editor. Save the file. b. In the Post Installer, set the file's action to Overwrite. Overwrite replaces the installed version of the file with the new version. To change the action from Keep Existing to Overwrite, click the Keep Existing button. 9. Click Upgrade Template. The old template is removed and the new template is installed. 10. When the success message displays, click OK. The Upgrade Template dialog box closes. You have completed the template upgrade. You are ready to upgrade the viewers that are configured in your sites. Click Finish and follow the prompts to close the Post Installer. Step 2: Upgrade your Configured Viewers You can upgrade all your configured viewers at one time (instructions below), or upgrade them individually (see To upgrade a single viewer: on page 48). To upgrade all of your configured viewers at one time: 1. Do one of the following: If Manager is Closed 1. Launch Manager. You will be prompted to upgrade your viewers. If Manager is Open 1. In Manager, click the Sites tab. If a site is open for editing, click Save Site if necessary, and then click Close Site. 2. Click the Upgrade Viewers hyperlink on the Sites tab. 47

53 Geocortex Essentials 4.5.Installation Guide Location of the Upgrade Viewers hyperlink 2. Make sure the check boxes for the types of viewers you want to upgrade (HTML5 or Silverlight) are selected and click OK. If you click Cancel instead of OK, you can upgrade the viewers later using the Upgrade Viewers hyperlink on the Sites tab. 3. When the Done message shows, click Close. The Upgrade Viewers dialog box closes. You have completed upgrading your viewers. You can now run your viewers and edit them in Manager. To upgrade a single viewer: 1. If Manager is closed, launch Manager and click Cancel when you are prompted to upgrade your viewers. 2. When you are ready to upgrade a viewer, edit the viewer. You will be prompted to upgrade the viewer. 3. Click Upgrade. Manager upgrades the viewer Restore a Viewer If you upgraded a viewer using Essentials, and then decide that you want to roll back to the older version, follow the instructions below to remove the new version and restore the old version. Viewer Backups To restore a viewer, you must have a copy of the folder where the viewer was deployed in the web server. If you upgraded the viewer using the Post Installer's Upgrade function, a backup is made automatically. For an instance of Essentials called Default, viewer backups created by the Upgrade function are in the following folder: C:\Program Files (x86)\latitude Geographics\Geocortex Essentials\Default\Backups Latitude Geographics Group Ltd. All Rights Reserved.

54 7.2.4 Restore a Viewer When the Post Installer's Upgrade function is used to upgrade a HTML5 viewer, a site's old configuration settings get backed up as well. You can find the configuration settings for the old viewer at this location: C:\Program Files (x86)\latitude Geographics\Geocortex Essentials\Default\REST Elements\Sites\Your Site\Viewer\VirtualDirectory\Resources\Config\Default The backup configurations have the file extension.backup.yyyymmdd, where YYYYMMDD is the date that the backup was made. Compatibility Issues A minor release may introduce breaking changes in the configuration settings. Incompatible configuration is automatically fixed by the software during the upgrade process, but it must be manually fixed if you are downgrading. To test your site's configuration for backwards compatibility, we recommend that you install both versions of the viewer, attempt to view your site through both of them, and compare the configuration settings side by side. You can use a tool like DiffChecker.com to visualize the configuration changes. To restore a previous version of a viewer: 1. In the file system, locate the folder that contains the backup of the viewer that you want to restore. If you upgraded the viewer using the Post Installer's Upgrade function, the backups are in the following folder: C:\Program Files (x86)\latitude Geographics\Geocortex Essentials\Default\Backups The folder Default name may be different depending on the name of your instance of Essentials. 2. Download the old template from the Geocortex Support Center ( See Download the Software on page 22 for instructions. 3. Launch the Post Installer: Windows Server 2012 or Windows 8, and Newer Versions: On the Start screen, type Post Install, and then click Post Installer. Windows Server 2008 or Windows 7, and Older Versions: In the Start menu, click All Programs Latitude Geographics Geocortex Essentials [Version] [Instance] Post Installer. [Version] is the Essentials version number. [Instance] is the instance name, if Essentials is installed as a named instance. The default installation does not have an instance name. 4. Select Configure Viewer Templates in the menu. 5. In the Installed Templates area, click the template that you want to roll back. The template's management buttons are displayed. 6. Click Remove, and then click Yes to confirm. The removed viewer remains in the webroot directory after this operation. If you wish to deploy to the same folder, you can go into the file system and manually rename or remove the viewer folder. 7. Install the old template. See Install Viewer Templates on page 78 for instructions. 8. Copy the backup of the old viewer to the folder in the web server where you just deployed the viewer template. 49

55 Geocortex Essentials 4.5.Installation Guide 9. Reload Manager and navigate to the Viewers page. 10. Ensure the viewer Launch URL matches the name of the folder where you just deployed the viewer template. If you deployed the old template to the same folder, the viewer may still reference the deleted template. In this case, the viewer does not display a Launch URL. To change the template the viewer references, select the Edit icon next to the viewer to launch the Select Template dialog box and point the viewer to your preferred viewer template. The Select Template dialog 11. Open the viewer in a web browser and verify that it works. Troubleshooting If your rolled back viewer does not open or states that the viewer configuration is invalid or malformed, we recommend examining the configuration of the viewer and a backup configuration of the site before it had been upgraded. If you upgraded an HTML viewer template using the Post Installer's Upgrade function, you can compare your new configuration with the backup copies of your old configuration files. See Viewer Backups for information. You can also generate a new viewer using the template that has just been installed. If the new viewer launches properly and the old one does not, compare the two viewer configurations to determine what the problem is. You can use a tool like DiffChecker.com to visualize the configuration changes Latitude Geographics Group Ltd. All Rights Reserved.

56 8 Post-Installation Configuration 8 Post-Installation Configuration Post-installation configuration is configuration related to the environment that Essentials runs in. This is mostly web server configuration, but also includes activating the Essentials software and configuring the method for signing in to Geocortex Essentials Manager. Essentials includes a desktop application, the Geocortex Post-Installation Configuration tool (the Post Installer), to help you perform the post-installation configuration. You can run the Post Installer at any time to modify the postinstallation configuration. You must run the Post Installer at least once after you install or upgrade Essentials and before you run Manager. The Post Installer allows you to: Activate Essentials. See Activate Geocortex Essentials on page 52. Choose the type of account administrators will use to sign in to Manager Portal for ArcGIS, ArcGIS Online, or Windows. If you choose ArcGIS, you will use the Post Installer to set up access to Portal for ArcGIS or ArcGIS Online. See Choose a Method to Sign In to Manager on page 53. Manage how Essentials is deployed in Internet Information Services (IIS). See Change IIS Settings for Essentials on page 75. Configure the host names that users and applications will use to access the Essentials web applications. See Configure Hosts on page 75. Manage how Essentials Manager is deployed in IIS. See Change IIS Settings for Essentials Manager on page 76. Add templates for the Geocortex Viewer for HTML5 and Geocortex Viewer for Silverlight. See Install Viewer Templates on page 78. Manage how Geocortex Identity Server is deployed in IIS, and configure the security certificate and SSL. See Change IIS Settings for Identity Server on page 77. Register a reverse proxy with Essentials. See Run Essentials Behind a Reverse Proxy on page 11. Configure cross-domain support. See Enable Cross-Domain Support on page 81. Enable Windows Authentication. See Configure Windows Features on page Launch the Post Installer You can launch the Post Installer from the Windows Start screen or Start menu at any time after Essentials is installed. 51

57 Geocortex Essentials 4.5.Installation Guide To launch the Post Installer: 1. Follow the instructions for the operating system that you are using: Windows Server 2012 or Windows 8, and Newer Versions: On the Start screen, type Post Install, and then click Post Installer. Windows Server 2008 or Windows 7, and Older Versions: In the Start menu, click All Programs Latitude Geographics Geocortex Essentials [Version] [Instance] Post Installer. [Version] is the Essentials version number. [Instance] is the instance name, if Essentials is installed as a named instance. The default installation does not have an instance name. 8.2 Activate Geocortex Essentials The first time Geocortex Essentials is installed on a computer, it defaults to a 60-day evaluation period. If you do not activate Essentials within the evaluation period, or arrange an extension, the license will expire and you will not be able to use Essentials. See First-Time Installation on page 24 for more information. Depending on how many computers Essentials is installed on, you will need one or more activation keys. For information, contact your Account Manager. Essentials must be activated on every server that it is installed on. Once Essentials has been activated on a computer, you do not have to activate it again on that computer, even if you upgrade or install additional instances. None of the information that is sent to Latitude Geographics during activation can be used to identify you or your computer. To activate Essentials: Before you begin, make sure you have your activation key at hand. 1. Launch the Post Installer. If you have multiple instances of Essentials installed, it does not matter which instance of the Post Installer you use to perform the activation the activation is for the computer, not the Essentials instance. 2. In the Product Activation part of the side panel, click Activate Geocortex Essentials. 3. Enter the activation key in the Activate area. 4. Click Activate. If you have the activation key in a file on your computer, you can either drag and drop the entire key into any one of the subfields, or copy and paste the key into a subfield the key will populate the subfields correctly. 5. Follow the instructions that apply to you: Scenario 1: Successful Activation If activation was successful, the license status will appear as Licensed Latitude Geographics Group Ltd. All Rights Reserved.

58 8.3 Choose a Method to Sign In to Manager Scenario 2: Offline Activation Required Activation requires the Post Installer to communicate with the licensing server over the Internet. If activation could not be completed online, an Activation Pending message will display and the Complete Activation Offline area will expand to show instructions for completing the activation offline. a. Click the "here" hyperlink in Step 1 of the Complete Activation Offline area and locate the Geocortex Essentials license file. b. the license file to support@geocortex.com and request offline activation. c. Latitude Geographics will activate your license file and it back to you. Save the file to the computer where Essentials is installed. d. Launch the Post Installer on the computer you are activating and click Activate Geocortex Essentials. e. Click the button in the Complete Activation Offline area and browse to the activated license file. f. Click Activate. The License Status will be "Licensed". 6. Click Finish. You have now completed the activation. 8.3 Choose a Method to Sign In to Manager Before you can use Geocortex Essentials Manager, you must specify how to authenticate administrators when they sign in to Manager. The sign-in methods are: Portal for ArcGIS: Use a Portal for ArcGIS account to sign in to Manager. Portal for ArcGIS performs the authentication. ArcGIS Online: Use an ArcGIS Online account to sign in to Manager. ArcGIS Online performs the authentication. 53

59 Geocortex Essentials 4.5.Installation Guide Windows: Use a Windows account to sign in to Manager. Windows performs the authentication. Windows supports single sign-on. To be signed in to Manager automatically, the administrator must already be signed in to Windows and the browser's security settings must have automatic authentication enabled under the current user name and password, for the appropriate zone. If one or more of these conditions is not met, the administrator will be prompted to sign in. The sign-in method that you choose has implications beyond how administrators are authenticated. The sign-in method also affects: The types of content that you can use in your sites: Portal for ArcGIS: If you want to use private Portal for ArcGIS content in your sites, you must configure sign-in using Portal for ArcGIS. You do not need to configure the Portal for ArcGIS sign-in method to use public Portal for ArcGIS content in your sites. ArcGIS Online: If you want to add private ArcGIS Online web maps and services to your sites, you must configure sign-in using ArcGIS Online. You do not need to configure the ArcGIS Online sign-in method to use public ArcGIS Online content in your sites. You cannot mix private Portal for ArcGIS content and private ArcGIS Online content within one instance of Essentials. You can always use public Portal for ArcGIS and ArcGIS Online content in your sites, no matter which sign-in method you choose Portal for ArcGIS, ArcGIS Online, or Windows. How end users can be authenticated when they access secured sites: Portal for ArcGIS: If you want end users to be able to sign in using their Portal for ArcGIS account when they launch a viewer, you must configure the Portal for ArcGIS sign-in method. ArcGIS Online: If you want end users to be able to sign in using their ArcGIS Online account when they launch a viewer, you must configure the ArcGIS Online sign-in method. Configuring one of the ArcGIS sign-in methods creates an ArcGIS-type security provider that you can use to configure permissions in Manager. For information about securing sites, see "Essentials Security" in the Geocortex Essentials Administrator Guide. Essentials always has a Windows Integrated security provider that enables you to secure your sites using Windows Authentication. You do not have to configure the Windows sign-in method in the Post Installer to get a Windows Integrated security provider. Service Connections: When Essentials is registered with ArcGIS Online, your Essentials installation has a built-in service connection for your private ArcGIS Online content. The built-in connection enables you to search your private ArcGIS Online content. The only way to use private ArcGIS Online content in Essentials sites is to register Essentials with ArcGIS Online when you configure the method to sign in to Manager. The built-in ArcGIS Online service connection does not appear in the list of service connections in Manager, and you cannot add an ArcGIS Online service connection when Essentials is registered with ArcGIS Online. There is no reason to add an ArcGIS Online service connection, because your Essentials instance has a built-in connection Latitude Geographics Group Ltd. All Rights Reserved.

60 8.3.1 Account Types that have Access to Manager Account Types that have Access to Manager By default, users with the following types of account can sign in to Manager: Portal for ArcGIS: If you configure sign-in using Portal for ArcGIS, the following accounts have access to Manager: Administrative accounts in your Portal for ArcGIS organization. The account that you use to set up access to Portal for ArcGIS in the Post Installer. ArcGIS Online: If you configure sign-in using ArcGIS Online, the accounts that have access to Manager depend on the URL that you configure in the Post Installer: Main ArcGIS Online URL: If you enter in the URL box, the only account that has access to Manager is: The account that you use to set up access to ArcGIS Online in the Post Installer. Organization URL: If you enter the URL for your organization's ArcGIS Online portal, for example, the following accounts have access to Manager: Administrative accounts in your ArcGIS Online organization. The account that you use to set up access to ArcGIS Online in the Post Installer. Windows: If you configure sign-in using Windows, the following accounts have access to Manager: Accounts that belong to the Windows group that you configure in the Post Installer. If you try to sign in to Manager using any other type of account, you are denied access. You can change which accounts have access to Manager. For instructions, see Change which Accounts have Access to Manager on page Hosts that have Access to Manager If you attempt to sign in to Manager from a host that is not registered with Essentials, you are denied access. You must register the hosts that communications are routed through. For instructions, see Configure Hosts on page Configure Single Sign-On to Manager Single sign-on signs you in automatically, so you do not need to enter your user name and password. Single sign-on to Manager requires the Windows sign-in method. The ArcGIS sign-in methods do not support single sign-on. When you launch Manager, in order to be signed in automatically, you must already be signed in to Windows. In addition, your browser's security settings must have automatic authentication enabled under the current user name and password, for the appropriate zone. If one or more of these conditions are not met, you will have to enter your user name and password to sign in. 55

61 Geocortex Essentials 4.5.Installation Guide To configure single sign-on to Manager: 1. Choose the Windows sign-in method. Follow the instructions in Configure Manager Sign-In Using Windows on page Enable Windows Authentication. Follow the instructions in Configure Windows Features on page Configure Manager Sign-In Using Portal for ArcGIS Configuring the Portal for ArcGIS sign-in method enables you to: Use your private Portal for ArcGIS content in your Essentials sites. Secure your Essentials sites using Portal for ArcGIS to authenticate end users. Sign in to Manager using one of the following types of account: Administrative accounts for your Portal for ArcGIS organization. The account that you use to set up access to Portal for ArcGIS in the Post Installer. You can change the Portal for ArcGIS account types that are allowed to sign in to Manager. For instructions, see Change which Accounts have Access to Manager on page 63. When you configure Portal for ArcGIS sign-in, you must set up access to Portal for ArcGIS for Essentials ("register" Essentials with Portal for ArcGIS). To register Essentials, you will: Configure the Portal for ArcGIS URL for the administrator's browser to point to when Manager launches. Add an application in Portal for ArcGIS. Sign in to Portal for ArcGIS when the Post Installer prompts you to. The Portal for ArcGIS application that you add is used by the Post Installer to create two web mapping applications, called Geocortex Essentials and Geocortex Essentials Manager. Essentials and Manager use these web mapping applications to access your private Portal for ArcGIS content. After you have completed the post-installation configuration, you can sign in to Portal for ArcGIS and see these web mapping applications in the Geocortex Products folder on your My Content page. Portal for ArcGIS web mapping applications created by the Post Installer Latitude Geographics Group Ltd. All Rights Reserved.

62 8.3.4 Configure Manager Sign-In Using Portal for ArcGIS Configuring the Portal for ArcGIS sign-in method creates an ArcGIS security provider in Manager. This enables you to secure sites by applying permissions to Portal for ArcGIS users and roles. When users launch a viewer, they can be authenticated by Portal for ArcGIS. For more information, refer to "The ArcGIS Security Provider" in the Geocortex Essentials Administrator Guide. The only way to add a security provider that authenticates users using Portal for ArcGIS is to configure the Portal for ArcGIS sign-in method in the Post Installer. To configure sign-in to Manager using Portal for ArcGIS: 1. In the Post Installer, click Configure Sign-In Options in the side panel. 2. Beside Sign in using, select ArcGIS. 3. In the URL box, type or paste the URL for your portal. If you deployed Portal for ArcGIS to the default location, the URL will be similar to Replace server.domain.com with the fully qualified host name of the server that hosts Portal for ArcGIS. 4. Click Test. The Post Installer connects to the URL. When the connection succeeds, the Post Installer displays a hyperlink to your portal. 5. Click the hyperlink to open your portal in a browser. 6. Sign in to your portal. 7. In your portal, create a Portal for ArcGIS application for the Post Installer to use. The Post Installer will use this application to add two web mapping applications to your portal. Essentials and Manager use the web mapping applications to access your private portal content. If you have already created an application for the Post Installer to use, you can skip this step and use the existing application. a. Click Add Item. b. Select An application from the The item is drop-down list. c. Select Application. d. In the Title box, enter a title for the application, for example, Geocortex Post Installer. 57

63 Geocortex Essentials 4.5.Installation Guide e. In the Tags box, add a search tag to help locate this application, for example, Geocortex. Add a Portal for ArcGIS application for the Post Installer to use f. Click Add Item. The application's details page opens. Details page for the Geocortex Post Installer application in Portal for ArcGIS In the screen capture above, the App Registration area has a Registered Info hyperlink. This indicates that the application was registered automatically when you added it. 8. If the App Registration area has a Register hyperlink instead of a Registered Info hyperlink, you must register the application manually: a. In the App Registration area, click Register. b. In the App Type drop-down list, select Multiple. c. In the Redirect URI box, type or paste the following URI: urn:ietf:wg:oauth2.0:oob Latitude Geographics Group Ltd. All Rights Reserved.

64 8.3.4 Configure Manager Sign-In Using Portal for ArcGIS d. Click Add. e. Click Register. The dialog box closes and the application is registered. Registration creates the application's ID and secret, which are used like a user name and password. 9. In the App Registration area, click Registered Info. You will need the App Registration information when you finish the post-installation configuration. App Registration information in Portal for ArcGIS 10. In the Post Installer, click Finish. 11. In the dialog box, copy and paste the App ID and App Secret from Portal for ArcGIS to the Post Installer. The App Secret is encrypted in Essentials. Essentials does not share this information with any other application. 12. Click OK. You are prompted to sign in to Portal for ArcGIS. 13. Sign in to Portal for ArcGIS using the same account that you signed in with when you created the application. The Post Installer sets up access to your private Portal for ArcGIS content for Essentials, and then signs you out of Portal for ArcGIS. If you clear the Remember Me check box when you sign in, you will have to enter the App ID and App Secret each time you run the Post Installer. 14. Follow the prompts to close the Post Installer. 13. Click Finish. 14. In the App Registration dialog box, copy and paste the App ID and App Secret from Portal for ArcGIS to the Post Installer, and then click OK. You are prompted to sign in to Portal for ArcGIS. The application's secret is encrypted in Essentials. Essentials does not share this information with any other application. 15. Sign in to Portal for ArcGIS using the same account that you signed in with when you created the application. The Post Installer sets up access to your private Portal for ArcGIS content for Essentials, and then signs you out of Portal for ArcGIS. 59

65 Geocortex Essentials 4.5.Installation Guide If you clear the Remember Me check box when you sign in, you will have to enter the App ID and App Secret each time you run the Post Installer. You have now completed the configuration of Portal for ArcGIS sign-in Configure Manager Sign-In Using ArcGIS Online Configuring the ArcGIS Online sign-in method enables you to: Use your private ArcGIS Online content, such as web maps and services, in your Essentials sites. Secure your Essentials sites using ArcGIS Online to authenticate end users. Sign in to Manager using one of the following types of account: Administrative accounts for your ArcGIS Online organization. The account that you use to set up access to ArcGIS Online in the Post Installer. You can change the ArcGIS Online account types that are allowed to sign in to Manager. For instructions, see Change which Accounts have Access to Manager on page 63. When you configure ArcGIS Online sign-in, you must set up access to ArcGIS Online for Essentials ("register" Essentials with ArcGIS Online). To register Essentials, you will: Configure the ArcGIS Online URL for the administrator's browser to point to when Manager launches. Sign in to ArcGIS Online when the Post Installer prompts you to. You have two choices for the URL that you configure: URL for Your Organization in ArcGIS Online: For example, If you specify the URL of your organization's ArcGIS Online portal, launching Manager opens the ArcGIS Online enterprise sign-in page. Only ArcGIS Online users from your organization can sign in. URL for ArcGIS Online: If you specify the URL for ArcGIS Online's home page, launching Manager opens the main ArcGIS Online sign-in page. You can configure which users can access your site from your ArcGIS Online account, including any unknown user with an ArcGIS Online account. You can select permissions for particular users and organizations from the Permissions page in Manager. See Permissions in the Geocortex Essentials Administrator Guide for more information. The Post Installer adds two web mapping applications to your ArcGIS Online portal. The web mapping applications are called Geocortex Essentials and Geocortex Essentials Manager. Essentials and Manager use these web mapping applications to access your private ArcGIS Online content. After you have completed the post-installation configuration, you can sign in to ArcGIS Online and see these web mapping applications in the Geocortex Products folder on your My Content page Latitude Geographics Group Ltd. All Rights Reserved.

66 8.3.5 Configure Manager Sign-In Using ArcGIS Online ArcGIS Online web mapping applications created by the Post Installer Configuring the ArcGIS Online sign-in method creates an ArcGIS security provider in Manager. This enables you to secure sites by applying permissions to ArcGIS Online users and roles. When users launch a viewer, they can be authenticated by ArcGIS Online. For more information, refer to "The ArcGIS Security Provider" in the Geocortex Essentials Administrator Guide. Before Essentials version 4.2, you could add ArcGIS Online security providers in Manager. Starting in version 4.2, the only way to add a security provider that authenticates users using ArcGIS Online is to configure the ArcGIS Online sign-in method in the Post Installer. If you configured an ArcGIS Online security provider before Essentials version 4.2, the security provider and its associated permissions will continue to work when you upgrade to Essentials 4.2 or newer, as long as you configure the ArcGIS Online sign-in method. You can have at most one ArcGIS security provider. If you configured an ArcGIS Online security providers before Essentials version 4.2, and you configure one of the other sign-in methods (Portal for ArcGIS or Windows) when you upgrade to Essentials 4.2 or newer, you will lose your ArcGIS Online security provider and all of its associated permissions. To configure sign-in to Manager using ArcGIS Online: 1. In the Post Installer, click Configure Sign-In Options in the side panel. 2. Beside Sign in using, select ArcGIS. 3. Do one of the following: In the URL box, type or paste the ArcGIS Online URL where you want end users to sign in: Enter the URL for Your Organization's ArcGIS Online Portal 1. In the URL box, type or paste the URL for your organization's ArcGIS Online portal. For example, Replace organization with the name of your organization's ArcGIS Online subdomain. 61

67 Geocortex Essentials 4.5.Installation Guide Enter URL of ArcGIS Online's Home Page 1. In the URL box, type or paste the URL for ArcGIS Online's home page. The URL is Alternatively, you can click the hyperlink to enter the URL. 4. Click Test. The Post Installer connects to the URL. When the connection succeeds, the Post Installer displays a hyperlink for the URL. You will be prompted to sign in to ArcGIS Online when you finish the post-installation configuration. This allows the Post Installer to set up access to ArcGIS Online for Essentials. 8. Click Finish. 9. In the App Registration dialog box, sign in to ArcGIS Online. The Post Installer sets up access to your private ArcGIS Online content for Essentials, and then signs you out of ArcGIS Online. The information gathered from ArcGIS Online is encrypted in Essentials. Essentials does not share this information with any other application. You have now completed the configuration of ArcGIS Online sign-in Configure Manager Sign-In Using Windows Choosing the Windows sign-in method: Enables you to sign in to Manager using an account that belongs to the Windows group that you configure in the Post Installer. Enables single sign-on to Manager when Windows Authentication is turned on. For information on turning on Windows Authentication, see Configure Windows Features on page 82. To configure sign-in to Manager using Windows: 1. In the Post Installer, click Configure Sign-In Options in the side panel. 2. Beside Sign in using, select Windows. 3. In the Group box, type the name of the Windows group that users must belong to in order to sign in to Manager. The default value is the built-in administrators group. 4. Click Finish. You have now completed the configuration of Windows sign-in Latitude Geographics Group Ltd. All Rights Reserved.

68 8.3.7 Change which Accounts have Access to Manager Change which Accounts have Access to Manager The default types of account that can sign in to Manager are listed in Account Types that have Access to Manager on page 55. You can change which accounts have access to Manager. The method that you use to change the account types depends on the sign-in method. Follow the instructions for the sign-in method that is configured in the Post Installer ArcGIS sign-in or Windows sign-in. ArcGIS Sign-In Use this method if you configured Manager sign-in using Portal for ArcGIS or ArcGIS Online. Security-related settings and data are stored in the XML-based Security Store, which is a component of Geocortex Core. The Security Store has a ClaimsToAccept element that you can edit to change the accounts that have access to Manager. Each Claim element within ClaimsToAccept defines one or more accounts that have access to Manager. The default ArcGIS claims are: <Claim Type=" Value="this_app:shared" /> <Claim Type=" Value="this_app:owner" /> <Claim Type=" Value="this_org:org_admin" /> If you configured Manager sign-in using Portal for ArcGIS, these claims apply to Portal for ArcGIS accounts. If you configured Manager sign-in using ArcGIS Online, the claims apply to ArcGIS Online accounts. Follow the instructions below to: Allow an individual to sign in to Manager. (page 63) Allow a group to sign in to Manager. (page 65) Allow your entire organization to sign in to Manager. (page 68) Prevent organization administrators from signing in to Manager. (page 70) Allow someone from outside your organization to sign in to Manager. Follow the instructions to allow a group to sign in to Manager. (page 65) To allow a particular individual in your ArcGIS organization to sign in to Manager: Step 1: Edit the Security Store 1. Launch the Post Installer. 2. Right-click the Geocortex Essentials title bar icon and select Edit Security Store. 63

69 Geocortex Essentials 4.5.Installation Guide The Post Installer's title bar menu offers the Edit Security Store option 3. After the Security Store opens, find the following markup in the XML: <PolicyDetails xml:id="manageraccess"> This element controls access to Manager. 4. Find the ClaimsToAccept element within the PolicyDetails element. 5. Add the following Claim element anywhere within the ClaimsToAccept element: <Claim Type=" Value="[account]" Issuer="[issuer]" /> 6. In the Value attribute of the new Claim element, replace [account] with the ArcGIS user name of the user that you want to add, for example, Value="amarch". To find out the user name, go to the My Organization page in your portal. Note that, if you are using ArcGIS Online sign-in to Manager and Enterprise Logins are configured for your ArcGIS Online organization, the user name is appended with an underscore followed by an identifier for your organization, for example, amarch_latitudegeo. 7. Find the IssuersToAccept element within the same PolicyDetails element as ClaimsToAccept. 8. Find the Issuer value that starts with urn:gcx:ags, for example, Issuer="urn:gcx:ags: F3-45B7-8B8E-5BBBFA89F44E" Latitude Geographics Group Ltd. All Rights Reserved.

70 8.3.7 Change which Accounts have Access to Manager 9. In the Issuer attribute of the new Claim element, replace [issuer] with the Issuer value that you located in the previous step. The new Claim element should now look something like this: <Claim Type=" Value="amarch" Issuer="urn:gcx:ags: F3-45B7-8B8E-5BBBFA89F44E" /> 10. Select Save. You do not need to remove any Claim elements from the XML. Step 2: Restart the RestManager Web Application in IIS This makes the changes to the XML take effect. 1. Launch Internet Information Services (IIS) Manager. 2. In the Connections panel, click Application Pools. 3. In the Application Pools panel, right-click EssentialsAdministrationAppPool4 and click Recycle. 4. Close IIS Manager. To allow an ArcGIS group to access Manager: Step 1: Create an ArcGIS Group 1. Sign in to Portal for ArcGIS or ArcGIS Online using the same account that you used to sign in to Portal for ArcGIS or ArcGIS Online in the Post Installer. 2. Create a group for Geocortex Essentials administrators. We recommend that you make the group private. 3. Invite the users that you want to be able to sign in to Manager to join the new group. You can invite members of your organization, as well as ArcGIS users who do not belong to your organization. 4. Share the Geocortex Essentials Manager web mapping application with the new group: a. Click My Content. b. In the side panel's Folders area, click Geocortex Products. The Geocortex Products folder contains two web mapping applications that were created by the Post Installer Geocortex Essentials and Geocortex Essentials Manager. c. Click Geocortex Essentials Manager to view its details. 65

71 Geocortex Essentials 4.5.Installation Guide d. Click Share. e. Select the check box for the group that you want to be able to sign in to Manager. f. Click OK. 5. Get the ID for the new group: a. Click Groups. b. Click Details to view the group's details. c. Click Share. d. Follow the instructions for the sign-in method that you are using: Portal for ArcGIS 1. In the Link to this group box, copy the value of the id parameter. You will use this value in Step 2. Copy the ID ArcGIS Online 1. In the Link to this group box, copy the URL. Copy the URL 2. Point your web browser to a site that expands short URLs, such as or 3. Paste the URL into the input box Latitude Geographics Group Ltd. All Rights Reserved.

72 8.3.7 Change which Accounts have Access to Manager 4. Click the button to expand the URL. 5. In the expanded URL, copy the value of the id parameter. You will use this value in Step 2. Step 2: Edit the Security Store 1. Launch the Post Installer. 2. Right-click the Geocortex Essentials title bar icon and select Edit Security Store. The Post Installer's title bar menu offers the Edit Security Store option 3. After the Security Store opens, find the following markup in the XML: <PolicyDetails xml:id="manageraccess"> This element controls access to Manager. 4. Find the ClaimsToAccept element within the PolicyDetails element. 5. Add the following Claim element anywhere within the ClaimsToAccept element: <Claim Type=" Value="[group]" Issuer="[issuer]" /> 67

73 Geocortex Essentials 4.5.Installation Guide 6. In the Value attribute of the new Claim element, replace [group] with the ID that you located in Step 1, for example, Value="c71a947bb05d4c3d890d e". 7. Find the IssuersToAccept element within the same PolicyDetails element as ClaimsToAccept. 8. Find the Issuer value that starts with urn:gcx:ags, for example, Issuer="urn:gcx:ags: F3-45B7-8B8E-5BBBFA89F44E". 9. In the Issuer attribute of the new Claim element, replace [issuer] with the Issuer value that you located in the previous step. The new Claim element should now look something like this: <Claim Type=" Value="c71a947bb05d4c3d890d e" Issuer="urn:gcx:ags: F3-45B7-8B8E-5BBBFA89F44E" /> 10. Select Save. You do not need to remove any Claim elements from the XML. Step 3: Restart the RestManager Web Application in IIS This makes the changes to the XML take effect. 1. Launch Internet Information Services (IIS) Manager. 2. In the Connections panel, click Application Pools. 3. In the Application Pools panel, right-click EssentialsAdministrationAppPool4 and click Recycle. 4. Close IIS Manager. To give your entire ArcGIS organization access to Manager: Giving your entire organization access to Manager is not recommended. We recommend that you limit access to particular individuals or to a group that is created for this purpose. Step 1: Edit the Security Store 1. Launch the Post Installer. 2. Right-click the Geocortex Essentials title bar icon and select Edit Security Store Latitude Geographics Group Ltd. All Rights Reserved.

74 8.3.7 Change which Accounts have Access to Manager The Post Installer's title bar menu offers the Edit Security Store option 3. After the Security Store opens, find the following markup in the XML: <PolicyDetails xml:id="manageraccess"> This element controls access to Manager. 4. Find the ClaimsToAccept element within the PolicyDetails element. 5. Add the following Claim element anywhere within the ClaimsToAccept element: <Claim Type=" Value="this_ app:org" /> 6. Select Save. You do not need to remove any Claim elements from the XML. 69

75 Geocortex Essentials 4.5.Installation Guide Step 2: Restart the RestManager Web Application in IIS This makes the change to the XML take effect. 1. Launch Internet Information Services (IIS) Manager. 2. In the Connections panel, click Application Pools. 3. In the Application Pools panel, right-click EssentialsAdministrationAppPool4 and click Recycle. 4. Close IIS Manager. To prevent organization administrators from signing in to Manager: If you do not want organization administrators to be able to sign in to Manager, remove the this_org:org_admin claim from the Security Store. Step 1: Edit the Security Store 1. Launch the Post Installer. 2. Right-click the Geocortex Essentials title bar icon and select Edit Security Store. The Post Installer's title bar menu offers the Edit Security Store option Latitude Geographics Group Ltd. All Rights Reserved.

76 8.4 Manage the Essentials Web Applications 3. After the Security Store opens, find the following markup in the XML: <PolicyDetails xml:id="manageraccess"> This element controls access to Manager. 4. Find the ClaimsToAccept element within the PolicyDetails element. 5. Delete the following Claim element from the ClaimsToAccept: <Claim Type=" Value="this_ org:org_admin" /> 6. Select Save. Step 2: Restart the RestManager Web Application in IIS The change to the XML take effect. 1. Launch Internet Information Services (IIS) Manager. 2. In the Connections panel, click Application Pools. 3. In the Application Pools panel, right-click EssentialsAdministrationAppPool4 and click Recycle. 4. Close IIS Manager. Windows Sign-In If you configured Manager sign-in using Windows, you can change which accounts have access to Manager by selecting a different Windows group in the Post Installer. To change the Windows accounts that have access to Manager: 1. On the server that hosts Manager, use the Windows management tools to create a local group. Alternatively, you can use a domain group. 2. Add the users that you want to be able to sign in to Manager to the group. 3. Launch the Post Installer and click Configure Sign-In Options in the side panel. 4. In the Group box, type the name of the group that users must belong to in order to sign in to Manager. 5. Click Finish and close the Post Installer. 8.4 Manage the Essentials Web Applications Essentials has three web applications that run on the server the Essentials REST API, Manager, and Identity Server. These web applications must be deployed to Internet Information Services (IIS). In IIS, the applications are called REST, RestManager, and IdentityServer respectively. 71

77 Geocortex Essentials 4.5.Installation Guide You may also have viewer applications in IIS. This section does not discuss viewers. See Manage Viewer Templates on page 77. You can use the Post Installer to perform the deployment. The first time that you run the Post Installer in a new Essentials installation, the Post Installer deploys the web applications to IIS. Thereafter, the Post Installer redeploys the web applications if necessary, for example, if you have changed the configuration. The actual deployment occurs when you click Finish in the Post Installer. You must always click Finish after installing or upgrading Essential, even if you have not changed the configuration. The Post Installer performs a number of other functions besides deploying the web applications when you click Finish. To deploy a web application, the Post Installer creates the specified virtual directory and application pool in IIS and adds the Essentials web application to the specified IIS website. Most installations can use the default configuration. One exception is Essentials hosting services that support multiple domains with multiple websites in each domain (multihoming). In this case, you will need to change the configuration. Similarly, if you are running multiple instances of Essentials on a server, you will want to change the configuration. We recommend that you use the default configuration if you can. If you are going to use a custom website, you must first create the website in IIS Manager and assign the host names. To change the remaining configuration, you can either use the Post Installer or IIS Manager. If you use IIS Manager, you must run the Post Installer afterwards and click Finish. Running the Post Installer keeps the IIS and Post Installer configurations synchronized with each other, so changes in one are reflected in the other. The Post Installer keeps a list of hosts for each IIS website that contains an Essentials web application. You must configure the host names that browsers and other web applications will use to access the Essentials web applications. See also... Run Essentials Behind a Reverse Proxy on page About the Application Pools The Post Installer creates the application pools that are required to run the Essentials web applications. By default, the application pools are: Essentials REST API: EssentialsAppPool4 Manager: EssentialsAdministrationAppPool4 Identity Server: IdentityServerAppPool Starting in Essentials 4.1, the default application pools use the built-in IIS identity, ApplicationPoolIdentity. Older versions of Essentials created local users for the application pools. Upgrading Essentials does not update the identities. To update an application pool's identity, open the application pool's Advanced Settings in IIS Manager, expand Process Model, and edit the Identity setting. Afterwards, re-run the Post Installer and click Finish. Before version 3.6, the Essentials web applications ran in 32-bit application pools in Classic mode. When you upgrade Essentials, the existing application pools continue to be used. If you upgrade from a version of Essentials that is older than 3.6, we recommend that you use 64-bit Integrated application pools unless you have a specific reason to use some other mode Latitude Geographics Group Ltd. All Rights Reserved.

78 8.4.2 About the IIS Virtual Directories We recommend that you use the default application pools and identities for whichever version of Essentials you are running About the IIS Virtual Directories The Post Installer creates the virtual directories for the Essentials web applications. The default virtual directories are: Essentials REST API: /Geocortex/Essentials/REST Manager: /Geocortex/Essentials/RestManager Identity Server: /Geocortex/IdentityServer The virtual directories that host the Essentials web applications cannot coincide with physical locations that already exist or are reserved. For example, if your website is at C:\gis and you want to use /MyEssentials/Web as the virtual directory, C:\gis\MyEssentials\Web must either be non-existent or empty. For this reason, a virtual directory cannot refer to existing applications or another virtual directory. This restriction means you cannot use the root of the website as the virtual directory for an Essentials web application. If you need to create a new virtual directory for one or more of the Essentials web applications, you can use the Post Installer to create the virtual directory you do not need to go into IIS Manager to create a custom virtual directory About the Websites By default, the Essentials web applications use IIS's Default Web Site. If you want to use a custom website for an Essentials web application, you must first create the website using IIS Manager, and then, in the Post Installer, configure the website for each Essentials web application that you want to be in that website. Later, if you change the website's bindings in IIS, re-run the Post Installer and click Finish to automatically detect the changes About Hosts In the context of Essentials, hosts are the contact points for browsers and other web applications to reach the Essentials web applications. When you first set up an Essentials system, one of the decisions that you make is what host names you will use in URLs that access the REST API and Manager. For example, in the host name is map.mydomain.com. The host names themselves are defined in different places in website bindings in IIS, or in network appliances like firewalls, proxies, and load balancers. The computer name can also be used as a host name. You must configure host names in the Post Installer. The Essentials web applications use the host names to assemble return URLs. In some cases, incoming communications have the return URL attached. In other cases, the URL has been removed by a network appliance. In this case, Essentials must assemble the return URL. The Post Installer keeps a list of hosts for each website that contains an Essentials web application. In the default configuration, the web applications all belong to the same website the Default Web Site. In this case, the Post Installer only keeps one list of hosts, which all three of the Essentials web applications use. If you use the default configuration to deploy the Essentials web applications, the list initially contains two host names, where machine-name is the name of the computer that the Post Installer runs on: machine-name.domain.com machine-name 73

79 Geocortex Essentials 4.5.Installation Guide Example of the default hosts list The list should include exactly those host names that you want users and applications to use to access the Essentials web applications. If your system uses different internal and external host names, make sure that the list includes both. Do not add extra host names to the list. If you do not want to use the default host names, remove them from the list. Essentials processes the hosts list starting from the top and working down. This means that the list's order can affect how Essentials assembles return URLs. As a general rule, put your preferred host names higher in the list. If you want to allow host names that are not fully qualified, place the short name above the fully qualified name in the list. Short host name positioned above the fully qualified host name If you want Essentials to accept both HTTP and HTTPS, without upgrading HTTP to HTTPS, configure both versions of the host name and make sure that the HTTP version is higher in the list than the HTTPS version. Place HTTP above HTTPS to allow both without upgrading HTTP Latitude Geographics Group Ltd. All Rights Reserved.

80 8.4.5 Configure Hosts Configure Hosts To add host names to a website's list of hosts: 1. Open the list of hosts for the desired website: REST API: To configure the host names for the website that the REST API uses, click Configure Geocortex Essentials REST API in the Post Installer's side panel, and then click Hosts. Manager: To configure the host names for the website that Manager uses, click Configure Geocortex Essentials Manager in the Post Installer's side panel, and then click Hosts. Manager uses Windows Authentication by default and may require the computer name as a host name to allow an administrator to log in on the server. Identity Server: To configure the host names for the website that Identity Server uses, click Configure Geocortex Identity Server in the Post Installer's side panel, and then click Hosts. If any two of the web applications use the same website, you can access the list of hosts from either panel there is only one list of hosts for a particular website. 2. Add Hosts: a. In the blank box at the bottom of the list, copy or type the host name that you want to add. If you are not using the default port (port 80 for HTTP, port 443 for HTTPS), make sure to include the port, for example, host.domain.com:7777. b. Click the down arrow in the Type box and select the protocol or If you want Essentials to accept both HTTP and HTTPS, without upgrading HTTP to HTTPS, add both versions of the URL and make sure that the HTTP version is higher in the list than the HTTPS version. c. Continue adding host names until you have added all the names that you want to allow. 3. Remove Hosts: a. If you do not want to allow a default host name, click the Remove tool beside the name to remove it. 4. Order the List: 5. Click OK. a. Click beside a host name that you want to move and drag the name to its new position in the list. b. Continue dragging and dropping host names until the list is ordered the way that you want it Change IIS Settings for Essentials You only need to configure the settings in the Configure Essentials panel if you want to change how the Essentials web application is deployed in IIS. If you are happy with the default configuration, you can skip this procedure. 75

81 Geocortex Essentials 4.5.Installation Guide To change the IIS settings for Essentials: 1. Launch the Post Installer. 2. Click Configure Essentials REST API in the side panel. 3. Website: To change the website where Essentials is deployed: a. Create and configure the website in IIS. b. On the Configure Essentials REST API panel of the Post Installer, select the website from the Select Web Site drop-down list. 4. Application Pool: We recommend that you use the default application pool. 5. Virtual Directory: To change the virtual directory that Essentials uses, type the virtual directory's path in the Select Virtual Directory box. 6. Click Finish. The Post Installer updates the IIS configuration for the Essentials REST web application Change IIS Settings for Essentials Manager This section applies only to the server that Manager is installed on. You only need to configure the settings in the Configure Essentials Manager panel if you want to change how the Manager web application is deployed in IIS. If you are happy with the default configuration, you can skip this procedure. To change the IIS settings for Essentials Manager: 1. Launch the Post Installer. 2. Click Configure Essentials Manager in the side panel. The Configure Essentials Manager panel displays. 3. Website: To change the website where Manager is deployed: a. Create and configure the website in IIS. b. On the Configure Essentials Manager panel of the Post Installer, select the website from the Select Web Site drop-down list. 4. Application Pool: We recommend that you use the default application pool. 5. Virtual Directory: To change the virtual directory that Manager uses, type the virtual directory's path in the Select Virtual Directory box. 6. Click Finish. The Post Installer updates the IIS configuration for the Essentials RestManager web application Latitude Geographics Group Ltd. All Rights Reserved.

82 8.4.8 Change IIS Settings for Identity Server Change IIS Settings for Identity Server You only need to configure the settings in the Configure Identity Server panel if you want to change how the Identity Server web application is deployed in IIS. To change the IIS settings for Identity Server: 1. Launch the Post Installer. 2. Click Configure Identity Server in the side panel. 3. Website: To change the website where Identity Server is deployed: a. Create and configure the website in IIS. b. On the Configure Identity Server panel of the Post Installer, select the website from the Select Web Site drop-down list. 4. Application Pool: We recommend that you use the default application pool. 5. Virtual Directory: To change the virtual directory that Identity Server uses, type the virtual directory's path in the Select Virtual Directory box. 6. Require SSL: When the Require SSL setting is turned on, applications must use the HTTPS protocol to communicate with Geocortex Identity Server. By default, SSL is required. If there is a message beside the Require SSL check box that says that the website does not support SSL, you must bind Identity Server's website to HTTPS in IIS. We recommend that you do not turn off the requirement for SSL. 7. Click Finish. The Post Installer updates the IIS configuration for the IdentityServer web application. 8.5 Manage Viewer Templates The Post Installer provides a number of functions to add and manage viewer templates. When you install a viewer template, the management functions become available in the list of installed templates. To show the management functions for a particular template, click the template. 77

83 Geocortex Essentials 4.5.Installation Guide Location of the buttons to manage a viewer template The management functions are: Upgrade: Use this function to upgrade your viewers to a new version. See About Upgrading Viewers Using Essentials on page 40. Deploy Management Pack: If you did not deploy the management pack when you first installed the viewer template, use this function to integrate the template with Manager, so you can use Manager to add and configure viewers. See Deploy a Viewer's Management Pack on page 81 for instructions. Deploy Template to IIS: Use this function to deploy the viewer template to IIS if you did not deploy the viewer template to IIS when you first installed the template. You can also use this function to deploy additional instances of the viewer template to IIS. See Deploy a Viewer Template to IIS on page 80 for instructions. Remove: Remove the viewer template. You will no longer be able to run viewers that are based on this template Install Viewer Templates Viewers are applications that end users use to view your maps and related GIS resources in other words, to view your Essentials sites. Geocortex has two viewer frameworks: Geocortex Viewer for HTML5 Geocortex Viewer for Silverlight A viewer template is a file that packages the application files that make up the viewer framework. This includes the management pack, which integrates the viewer framework with Manager. Installing the management pack enables you to use Manager to add viewers to your sites and configure the viewers you have added. The file extension for template files is.vte. You only need to install the template once in an instance of Essentials, and then you can add as many viewers of that type as you want, to as many sites as you want. You use the Post Installer to install viewer templates. Before you begin, download the installation packages for the viewer frameworks from the Geocortex Support Center. For instructions, see Download the Software on page Latitude Geographics Group Ltd. All Rights Reserved.

84 8.5.1 Install Viewer Templates To install a viewer template: 1. In the Post Installer, click Configure Viewer Templates in the side panel. 2. Click Add. 3. Browse to the template (.vte) file, and then click Open. You are prompted to install the management pack. 4. To install the management pack, click Yes. If you click No, you can install the management pack later, after you have installed the template. See Deploy a Viewer's Management Pack on page 81 for instructions. A prompt asks you if you want to deploy the viewer application to IIS. 5. To deploy the viewer application to IIS, click Yes. If you click No, you can deploy the template later, after you have installed the template. See Deploy a Viewer Template to IIS on page 80 for instructions. The Deploy Template to an IIS Virtual Directory dialog box opens. 6. If you want to deploy the viewer to a website that does not exist yet, create the site in IIS. 7. In the Select Web Site box, select the website you want to deploy the viewer to. 8. In the Select Virtual Directory box, type a name or path for the virtual directory where you want the viewer to be deployed. The virtual directory must not already exist Essentials will create the web folder needed to deploy the viewer. 9. If you want to be able to launch your viewers from Manager, make sure the Register URL with Manager check box is selected. If you clear the Register URL with Manager check box, the launch links do not appear in Manager, but you can still add and configure viewers in Manager. For the HTML5 viewer, the URL you register with Manager must have the same domain as Manager the viewer cannot launch or load configuration from a different domain. 10. If the URL beside the check box is not fully qualified, replace it with the fully qualified URL. A fully qualified URL specifies the host and domain, for example, host.domain.com. A URL that omits the domain is not fully qualified. Geocortex Essentials and later versions provide the fully qualified URL by default. 11. Click Deploy. A success message displays. 12. Click OK. The viewer is listed in the Installed Templates area of the Configure Templates panel. To remove a template from the list, select it from the list of templates and click Remove. This does not remove the viewer framework from Manager, nor does it remove virtual directories from IIS. 79

85 Geocortex Essentials 4.5.Installation Guide 13. Click Finish. You have now installed the viewer template Deploy a Viewer Template to IIS If you did not deploy a viewer template to IIS when you installed the template, you can deploy it later at any time. To deploy a template to an IIS virtual directory: 1. In the Post Installer, click Configure Templates in the side panel. 2. Click the template that you want to deploy. Clicking the template in the list reveals buttons that you can use to manage the template. 3. Click Deploy Template to IIS. The Deploy Template to an IIS Virtual Directory dialog box opens. 4. If you want to deploy the viewer to a website that does not exist yet, create and configure the website in IIS. 5. In the Select Web Site box, select the website you want to deploy the viewer to. 6. In the Select Virtual Directory box, type a name or path for the virtual directory where you want the viewer to be deployed. The virtual directory must not already exist Essentials will create the web folders needed to deploy the viewer. 7. If you want to be able to launch your viewers from Manager, make sure the Register URL with Manager check box is selected. If you clear the Register URL with Manager check box, the launch links do not appear in Manager, but you can still add and configure viewers in Manager. For the HTML5 viewer, the URL you register with Manager must have the same domain as Manager the viewer cannot launch or load configuration from a different domain. 8. If the URL beside the check box is not fully qualified, replace it with the fully qualified URL. A fully qualified URL specifies the host and domain, for example, host.domain.com. A URL that omits the domain is not fully qualified. Geocortex Essentials and later versions provide the fully qualified URL by default. 9. Click Deploy. A success message displays. 10. Click OK. 11. Click Finish. You have now deployed the viewer template to IIS Latitude Geographics Group Ltd. All Rights Reserved.

86 8.5.3 Deploy a Viewer's Management Pack Deploy a Viewer's Management Pack If you did not deploy a viewer's management pack when you installed the viewer template, you can deploy it later at any time. To deploy a viewer's management Pack: 1. In the Post Installer, click Configure Templates in the side panel. 2. Click the template that you want to deploy. Clicking the template in the list reveals buttons that you can use to manage the template. 3. Click Deploy Management Pack. A success message displays. 4. Click OK. 5. Click Finish. You have now deployed the viewer's management pack. 8.6 Enable Cross-Domain Support The Post Installer's Configure Cross Domain Support page applies to the Silverlight Viewer only. Geocortex Essentials provides REST-based services that can be consumed by client applications. Normally, browser applications only allow site-of-origin communication for requests other than images. For example, a Silverlight application hosted at can only access services on the domain. It cannot access resources on a domain such as without special permission. Silverlight applications use a clientaccesspolicy.xml file at the root of a domain to permit cross domain access. Cross domain access is not a requirement for Geocortex Essentials, however, it is necessary in many common deployment scenarios that involve multiple servers and domains. You might need to enable cross domain support on the Core server, and on each server that hosts a copy of the REST API. To enable a cross domain support for the domain hosting Essentials: 1. Launch the Post Installer. 2. Click Configure Cross Domain Support in the side panel. The Cross Domain Support panel opens. 3. Select the website that is hosting Geocortex Essentials. 4. Click Enable on the clientaccesspolicy.xml entry to enable cross domain support using a clientaccesspolicy.xml file. This deploys a default crossdomain.xml file to the root of IIS (typically C:\Inetpub\wwwroot\clientaccesspolicy.xml). You may edit this file to fine tune its behavior. 81

87 Geocortex Essentials 4.5.Installation Guide If a clientaccesspolicy.xml file already exists for the selected website, the Enable button is disabled. 5. Click Enable for the crossdomain.xml entry to enable cross domain support using a crossdomain.xml file. This deploys a default crossdomain.xml file to the root of IIS (typically C:\Inetpub\wwwroot\crossdomain.xml). You may edit this file to fine tune its behavior. If a crossdomain.xml file already exists for the selected website, the Enable button is disabled. 6. Click Finish. You have now enabled cross-domain support. 8.7 Configure Windows Features The Post Installer's Configure Windows Features panel enables you to turn on Windows Authentication. Turning on Windows Authentication in the Post Installer is equivalent to installing Windows Authentication in Internet Information Services (IIS) and enabling the Windows Authentication Windows feature. Windows Authentication feature in the Windows Features panel There are two reasons to enable Windows Authentication: Essentials Security: To secure Essentials using the Windows Integrated security provider. For information, refer to the "Essentials Security" section in the Geocortex Essentials Administrator Guide. Manager Single Sign-On: To enable single sign-on to Manager, so you do not need to enter your user name and password. Single sign-on to Manager is supported by the Windows sign-in method only. For information, see Choose a Method to Sign In to Manager on page Latitude Geographics Group Ltd. All Rights Reserved.

88 8.7 Configure Windows Features To enable Windows Authentication using the Post Installer: 1. In the Post Installer, click Configure Windows Features in the side panel. 2. Select the Windows Authentication check box. If the check box is selected and grayed out, Windows Authentication is already installed and enabled. 3. Click Finish. You have now enabled Windows Authentication. 83

89 Geocortex Essentials 4.5.Installation Guide 9 Manual Site Migration Site migration refers to copying a site from one instance of Essentials to another. This section provides instructions for manually migrating a site. In general, you do not need to migrate sites manually when you upgrade Essentials, the installer automatically migrates your sites from the old installation to the new installation. Site migration is done on the server where the configuration files reside. In a multi-server system with redundant REST APIs, this is the server that hosts the network share. See Deployment on page 9 for information. To migrate a site manually: 1. In the file system, navigate to the Sites folder of the Essentials instance that contains the site that you want to migrate. 2. Copy the folder for the site you want to migrate to the Sites folder of the other Essentials instance. 3. Copy any additional configuration files that the site references to the equivalent location in the other Essentials instance. For example, if the site references workflows, print templates, or report templates that are not in the folder that you copied in step 2, copy these additional files to the equivalent location in the other Essentials instance. You have now migrated the site. 10 Back Up and Restore Your Essentials Installation We recommend that you schedule regular backups of the important data in your Essentials installation. Ideally, backups are a regular, automated process. To restore an old Essentials installation from a backup, you will require the following: Your Essentials installation's important data. See Back Up Essentials Data below. Your important viewer data. See Back Up HTML5 Viewer Data below. A copy of the Essentials installer that matches the version of the backup. If you no longer have access to the Essentials installer required, you can download previous versions of Essentials from the Geocortex Support Center Back Up Essentials Data For a typical Essentials installation with the generic name Default, you may want to backup the folders at the following locations: Latitude Geographics Group Ltd. All Rights Reserved.

90 10.2 Back Up HTML5 Viewer Data Sites Folder: The location of your installation's site data. C:\Program Files (x86)\latitude Geographics\Geocortex Essentials\Default\REST Elements\Sites Geocortex Core Data: The location where log files and other Core components are stored. C:\Program Files\Latitude Geographics\Geocortex Core\Data IIS Virtual Directory: The virtual directory where your Geocortex and viewer folders are located. C:\inetpub\wwwroot Essentials Web.config: Customizes the requirements of your Essentials installation. C:\Program Files (x86)\latitude Geographics\Geocortex Essentials\Default\REST Elements\REST\Web.config Make note of any changes that have been made to the Essentials Web.config file, because these changes can be lost during an upgrade or reinstall. However, it is not a good idea to replace this file with a copy when restoring from a backup Back Up HTML5 Viewer Data The configuration files for a typical installation of an HTML5 viewer can be found in the following folder: C:\inetpub\wwwroot\Html5Viewer Note that the name of the folder, Html5Viewer, may be different if you renamed a viewer or have multiple viewers. You may have made changes to the following files that require restoration after an upgrade: Proxy Configuration: Configures custom proxy rules for your viewer. C:\inetpub\wwwroot\Html5Viewer\proxy.config Index: The default host file for a viewer. C:\inetpub\wwwroot\Html5Viewer\index.html Your changes to the proxy.config and index.html files can be lost during an upgrade or reinstall. However, it is not a good idea to replace these files with copies when restoring from a backup Steps to Restore Geocortex Essentials Data from a Backup The following procedure outlines how to restore Geocortex Essentials data from a backup for a typical installation. If you renamed or relocated folders and files while setting up Essentials, your file names and locations may be different. To restore Geocortex Essentials data from a backup: 1. Install the version of Essentials that matches the version of the backup. 2. After Geocortex Essentials is installed, run the Post-Installation Configuration application. 3. Stop the Geocortex Core service from your Windows Services list. 85

91 Geocortex Essentials 4.5.Installation Guide 4. Delete the Core Data folder at the following location: C:\Program Files\Latitude Geographics\Geocortex Core\Data 5. Replace the Data folder with your backup Data folder. 6. Restart the Geocortex Core service from your Windows Services list. 7. Copy the contents of your backed up Sites folder to the new installation's Sites folder at the following location: C:\Program Files (x86)\latitude Geographics\Geocortex Essentials\Default\REST Elements\Sites 8. Copy the contents of the backed up IIS Virtual Directory (the wwwroot folder) to the IIS Virtual Directory for the new Geocortex Essentials server installation: C:\inetpub\wwwroot\ 9. Make any required changes to in the REST Web.config file at the following location: C:\Program Files (x86)\latitude Geographics\Geocortex Essentials\Default\REST Elements\REST\Web.config 10. Open Essentials Manager and check your sites and viewers to ensure they are working and configured correctly Schedule Virtual Machine Backups If your Essentials server is a virtual machine, you can schedule complete machine snapshots that you can roll back to if issues with your sites arise. See your virtual machine software's documentation for information Latitude Geographics Group Ltd. All Rights Reserved.

92 Appendix A: Geocortex Core Ports and Firewall Access Appendix A: Geocortex Core Ports and Firewall Access Geocortex Core provides software services that Geocortex applications like Essentials use. For example, Geocortex Core has a distributed database that Essentials Security uses for the Security Store. The services provided by Geocortex Core make it possible to build scalable components for Geocortex software. Instant Search is one such component. A.1 Default Ports Used by Geocortex Core By default, Geocortex Core's services use the TCP network ports listed in the table below. These ports must not be used by any other application on the server, or restricted in any way. You should not expose these ports to the Internet they are only used internally. Default TCP Network Ports to Reserve for Geocortex Core Service Ports Blob Store 7000, 7198, 9042, 17000, 17199, and BootStrapper 7278 Cache 6379 Data Store 9200 and 9300 Message Queue , 5672, and Printing 4731 Web Service Proxy A.2 Change the Data Store's Port By default, the Data Store uses port 9200 to provide HTTP access to your data. Many organizations prefer to change this port for security reasons. Follow the instructions below to change the port. Note that the Data Store also uses port 9300, but port 9300 uses a native protocol that web browsers cannot use, instead of HTTP. If you need to change other ports besides the Data Store's port 9200, contact Geocortex Support for help. 87

93 Geocortex Essentials 4.5.Installation Guide To change the Data Store's default port 9200: Step 1: Change the Port Number 1. On the Geocortex Core server, run a text editor or XML editor as an administrator. 2. Edit the Elasticsearch role.config file. If Geocortex Core is installed in the default location, the role.config file is here: C:\Program Files\Latitude Geographics\Geocortex Core\NSRoot\Geocortex\Core\Roles\ElasticSearch\[version]\role.config 3. Find the following line: <StartupSetting Key="WatcherPort" Value="9200" /> 4. Change the Value attribute to the port that you want to use, for example: <StartupSetting Key="WatcherPort" Value="9206" /> 5. Save the file. 6. Close the file. Step 2: Update the Firewall Rule The instructions below are for Windows Firewall. If you are using some other firewall, update the inbound rule for the firewall you are using. 1. Open Windows Control Panel on the Geocortex Core server. 2. Click Windows Firewall. 3. In the side panel, click Advanced settings. 4. In the side panel, click Inbound Rules. 5. In the Name column, find the Geocortex Core Document Store rule that uses Local Port Right-click the rule and select Properties. 7. On the Protocols and Ports tab, change the Local port to the port number that you want to use. Use a port is not used by another application. 8. Click OK. Step 3: Restart the Geocortex Core Server 1. Restart the Geocortex Core server. This makes the updated firewall rule take effect Latitude Geographics Group Ltd. All Rights Reserved.

94 A.3 Firewall Access for Geocortex Core A.3 Firewall Access for Geocortex Core Geocortex Core requires access through the firewall. By default, Geocortex Core uses Windows Firewall with the inbound rules shown in the screen capture below. The rules that Geocortex Core needs are created automatically during installation you do not need to do any firewall configuration if you use the default setup. Inbound firewall rules required by Geocortex Core 2.4 programs, showing the default port numbers By default, the Geocortex Data Store uses port 9200 to access your Data Store data. Many organizations prefer to change this port for security reasons. To change this port in Windows Firewall, follow the instructions in Change the Data Store's Port on page 87. If you use some other firewall besides Windows Firewall, you must configure the firewall with inbound rules similar to the ones shown in the screen capture. Each rule allows access to one program that Geocortex Core uses. Additional settings for the rules are: Action: Allow Override: No All Other Settings: Any To see the entire rules, view them in Windows Firewall. To view the Windows Firewall's inbound rules: 1. Open Windows Control Panel. 2. Click Windows Firewall. 3. In the side panel, click Advanced settings. 4. In the side panel, click Inbound Rules. 89