Frequently Asked Questions (FAQs)

Most modern web browsers like: Chrome, Firefox, Safari, Edge, and IE11+. For optimal performance, the product team recommends using the application in the most up to date versions of these.

Since App Manager is an HTML, JavaScript, and CSS web application any operating system with a modern web browser can run App Manager – even tablets, phones, and other devices.

Yes, the application requests/transactions can be encrypted by running over HTTPS (SSL).

App Manager can be “replicated” to multiple application servers and function in a load balanced environment. See Scalability and Performance for more details.

Yes, every service endpoint and functionality in all our applications have an assigned privilege. Roles can be created dynamically and privileges can be assigned to, or removed from, any role. See the Roles, Role Privileges, and User Roles sections for information on configuring authenticated user roles.

Yes, the Google tracking code can be entered into App Manager. See the Installed Applications topic under "Tracking ID" for instructions on how to configure this feature.

All Google Maps JavaScript API applications are subject to the limitations of Google's Terms of Service. Therefore to use any imbedded Google Map tools within the applications, you will need to adhere to Google's Terms of Service - this typically means you need to purchase an enterprise license. To learn more, please visit Google Maps' Get a Key/Authentication page. Once you have that you can enter it in the General Server Settings, along with your Client ID, Signature, and/or Channel.

Yes, please see the Configuration Store topic for more information as well as step-by-step migration instructions.

All of Rizing Geospatial's products provide safeguards to help prevent SQL injection attacks by making use of paramaterized SQL queries within the .NET framework. While there are safeguards in place to prevent SQL injection attacks, within Rizing Geospatial's products, the recommended data access architecture is intended to provide the greatest defense mechanism. Securing data access via connection account privileges and application user/role/privilege assignment is critical to mitigating the risk of unintended server and database access. This is particularly important due to the fact that some functionality in Rizing Geospatial's products do require some level of dynamic SQL input. It is critical that only authenticated and trusted users have access to this functionality. All database connections to the transactional data should be configured to use a read-only connection. See "Data Flow and Connections" for more details.

It depends on the type of release. Rizing uses the Major.Minor.Patch semantic versioning (for example, version 5.0.0 is a major release, version 5.1.0 is a minor release, and 5.1.1 is a patch release). Minor or patch releases can be installed in any order. For major releases, reference the Release Notes for the recommended installation instructions, which may include a specified order. It is best to install the all of latest products at the same time. and we strongly recommend making a backup of the site/TDS configuration before you begin.

Enhancements and bug fixes are provided in each release, so keeping your application updated to the most recent version ensures the best performance of the applications.

1. Navigate to Programs in your computer.
2. Click Uninstall for the application you want to uninstall.
3. Click Uninstall or Yes on the confirmation popup.
4. A confirmation prompts will open. Click OK to confirm.

See "To uninstall the application" under the Updating an Existing Installation heading in the Getting Started topic for more information.

Yes, please see the Installing TDS to a new Website in IIS topic which will walk you through the process of uninstalling and backing up TDS, creating a new TDS website in IIS and migrating data from the previous install.

IIS has many configurations and modules that can interfere with the HTTP requests from TDS applications to the TDS services. Typically, the default IIS configuration provides the necessary setup to allow for the required HTTP traffic to route through IIS and to the TDS web services (API). However, if certain requests (typically HTTP PUT or DELETE) are not being properly routed to the TDS API, the following steps can be used to troubleshoot the configuration issue.

Option 1 - Check and Remove WebDAV

1. Open Programs and Features on your computer.
2. Select the Turn Windows features on or off option.
3. Continue through the Add/Remove Roles wizard until you get to the option to edit IIS features.
4. Uncheck the following option found under Internet Information Services > World Wide Web Services > Common HTTP Features
   • WebDAV Information Services
5. If the option is not checked, proceed to Option 2 below.
6. Click OK.
7. Test the application to see if it resolved the issue.

   Note: You may need to restart the server for the change to take effect.

Option 2 - Add additional verbs to default IIS configuration

1. Navigate to the IIS applicationHost.config file.
   • Typically located at C:\Windows\System32\inetsrv\config
2. Edit the applicationHost.config file in a text editor.
3. Navigate to the system.webServer > security > requestFiltering > verbs tag.
4. Ensure that PUT and DELETE are listed.

   Note: If the allowUnlisted="true" property is set on the verbs tag then it is not necessary to specify “PUT” and “DELETE” explicitly.

   Tip: If you do not want to apply this setting globally to IIS you can make this configuration specifically for the TDS application or website. https://docs.microsoft.com/en-us/iis/configuration/system.webserver/security/requestfiltering/verbs/add

5. Test the application to see if it resolved the issue.

   Note: You may need to recycle the app pool or restart IIS.

Rizing Geospatial is committed to ensuring accessibility for people with disabilities. Due to the nature of some of our products not all accessibility rules are relevant or obtainable. Please see our WCAG and 508 Compliance topic for further details on how we are continually working to improve the user experience for everyone and apply the relevant accessibility standards across all our web applications.

Yes, all of Rizing Geospatial's applications support Esri's branch versioning. Branch Versioning means the application will query the versions thru the map service, not the database. So, when adding a data source for the applications to use that has branch versioning, you will need to check the Data source uses ArcGIS Branch Versioning option, then enter the Map Services Account Username and Map Services Account Password in Application Settings.

In order for Rizing Geospatial's applications to load properly, the Associated Service URL of the data source configured in TDS needs to be at a minimum a Viewer User Type in Portal and have the map services used by the Data Source shared with it. The easiest way to do that is to add the user to the group that the map service is shared with, if the map services are not shared to the Organization.

You can have both types of versioning in a single database: traditional and branch. Traditional versions are managed within the database. Branch versions are managed from the feature service. Only one type of versioning can be used with a Data Source. If there is a need to pull branch versioned data and traditional versioned data from the same database, for example in a Segment Analyzer template, two different Data Sources will need to be used: one configured with just the database connection and map service and one configured with the map service and the Data source uses ArcGIS Branch Versioning option checked.