Licensing Requirements

Geocortex Printing is licensed software. The license that you choose depends on the number of ArcGIS identities (named users for ArcGIS Online and Portal for ArcGIS) that your organization has.

To obtain a license, contact Customer Service at

Authoring Requirements

Requirements

You require an ArcGIS Identity to create and share Geocortex print templates.

Browser Requirements for Geocortex Print Designer

Geocortex Print Designer runs in a desktop environment. Designer supports the following browsers:

Supported Host Applications

You can use the following applications to host print templates:

Supported Client Browsers

To generate printable maps, the browser should meet the host application's browser requirements:

Requirements for On-Premises Printing

To use local resources in prints, you must use on-premises Printing. The Geocortex Printing cloud servers cannot resolve your server's host name to connect to the server. For more information, see On-Premises Printing vs. Cloud Printing.

If you want to host print templates in 3D Web AppBuilder apps, you must use Web AppBuilder (Developer Edition). On-premises Printing cannot print 3D web scenes from the ArcGIS Enterprise version of Web AppBuilder. See Supported Host Applications.

Supported Versions of Portal for ArcGIS

Geocortex Printing works with Portal for ArcGIS in ArcGIS Enterprise 10.5+.

If Portal for ArcGIS is secured using Windows Integrated Security and anonymous access to the portal is disabled in IIS, you must install the Geocortex Web Adaptor Extensions to allow Geocortex Printing to communicate with Portal for ArcGIS. The Service Account configured in the Post Installer must be an account recognized by IIS on the Portal machine.

You can use Portal for ArcGIS 10.5 to access Print Designer and store print items. However, you cannot host print templates in Web AppBuilder in Portal for ArcGIS 10.5 apps, because version 10.5 did not support custom widgets. Support for custom widgets started in version 10.5.1.

Hardware Requirements for On-Premises Printing Servers

A faster CPU and more memory improve the performance of Geocortex Printing. We recommend that your server surpass the minimum requirements.

Minimum Hardware Requirements for an On-Premises Geocortex Printing Server

Hardware Component



Random Access Memory (RAM)

8 GB

16 GB or higher

Storage Drive (HDD, SSD)

1 GB

5 GB or higher


2-core processor, 2 GHz, x64

4-core processor, 2 GHz or higher, x64

Operating System Requirements for On-Premises Printing Servers

On-premises Printing servers require Windows Server 2012+.

You can use a recent desktop version of Windows, such as Windows 10 or 8.1, for development and basic testing. However, they are not recommended for use in a production environment.

Web Server Requirements for On-Premises Printing Servers

On-premises Printing servers require the Internet Information Services (IIS) feature of the Windows operating system. The Post Installer application automatically enables IIS by enabling the Web Server role, along with the Application Initialization, ASP.NET 4.5, Windows Authentication, and WebSocket Protocol service roles and all of their service role dependencies.

If you uninstall on-premises Printing, all previously enabled IIS features remain enabled.

.NET Requirements for On-Premises Printing Servers

On-premises Printing servers require .NET Framework 4.6.1+.


On-premises Printing does not expose any ports, so you do not need to adjust your firewall settings. Geocortex Printing (including Print Designer) relies on the ports that IIS uses (ports 80 and 443 by default).

Cookie Requirements

Geocortex Printing uses the following first-party, strictly necessary cookies for authentication purposes:

Cross-Origin Resource Sharing (CORS) Requirements

By default, ArcGIS portals (including ArcGIS Online) allow cross-domain requests using CORS. If you configure the Organization | Settings | Security | Allow Origins setting in the portal that you use with Geocortex Printing, then you must add Geocortex Printing as an allowed origin.

The origin to allow depends on your deployment: