Recommended environment/security configurations - HxGN EAM - 11.07.01 - Feature Briefs - Hexagon

HxGN EAM Mobile for Transit Configuring GIS Map View

Search by Category
Feature Briefs
HxGN EAM Version

It’s worth noting that due to the number of potential server/service configurations, not all configurations have been tested. The following are requirements for the current release:

  • The customer’s GIS feature data should be hosted by ArcGIS Portal i.e. self-hosted solution.

  • Basemap data may be hosted by ArcGIS Portal or ArcGIS Online (hosted by ESRI).

  • Individual ArcGIS Portal user accounts must be setup for each mobile app user.

  • The use of secured feature servers is supported. They must be token-based and hosted by an ArcGIS server and federated with the customer’s Portal.

  • Portal security for its users will be honored by the mobile application.

While HxGN EAM does NOT explicitly lock out or prevent other specific environmental configurations (for example, hosting customer’s feature data via ArcGIS Online), the most common configuration uses ArcGIS Portal as follows:

Map Servers host the Tiled Basemap Service. In the ArcGIS Portal environment, Map Servers can either be self-hosted in the customer’s Portal or administrators can configure their Portal content to include a link to the Tiled Basemap Services offered (and hosted) by ArcGIS Online. When the Map Server is self-hosted, the server should not have security enabled or it should be enabled via Token based authentication and federated with their ArcGIS Portal. When using one of the Tiled Basemap Services offered (and hosted) by ArcGIS Online, please see the section of this document titled ‘Preparing the Basemap Service’ for configuration details.

Feature Servers host the customer’s feature data through ArcGIS Portal. Each EAM Mobile Transit app user will need a corresponding user account setup in ArcGIS Portal. Currently, these accounts are used to license the use of the ArcGIS Runtime iOS SDK and to configure content users are authorized to access and/or edit. Level 1 type (lite) users should be used for mobile users that will NOT be creating or editing data on the device, while Level 2 type (basic) users should be used if the user will be creating and/or editing data.

As recommended above, feature and basemap service should be hosted on a portal; however, this is NOT a requirement. Portal is only required by the Mobile Transit app to verify that the mobile SDK license is valid. Therefore, each mobile user must have a valid user on ESRI’s hosted portal (i.e. ArcGIS Online) or on the customer’s portal. The feature and basemap service can both be published to ArcGIS server and consumed by Mobile Transit in this scenario.

The use of secured feature servers is supported. The security type must be token-based and the ArcGIS server hosting the feature service must be federated with the portal, if a portal is being used. The following link provides more details on federating ArcGIS server with Portal