Configuring Indoor Maps

Complete the following tasks in TRIRIGA® to configure indoor maps.

Enabling latitude and longitude

Set the GIS Latitude and GIS Longitude for the building on the building form.

Procedure

Open the General tab and enter the latitude and longitude values in the Primary Address section.
Field Description
GIS Latitude (triGisLatitudeNU) Obtain the latitude by searching for the address and looking at the URL. You might have to tweak the link to get to the preferred position.
GIS Longitude (triGisLongitudeNU) Obtain the longitude by searching for the address and looking at the URL. You might have to tweak the link to get to the preferred position.

Enabling buildings

TRIRIGA must be populated with data for each building that has TRIRIGA Indoor Maps defined for them within Esri ArcGIS.

Before you begin

Procedure

On the record for buildings, open the Esri Maps tab and update it with the details in the following table.
Field Description
Esri Map ID (triEsriMapIdTX) Web map that must be loaded from the ArcGIS server. Obtain this ID from the Esri ArcGIS Portal, see Obtaining the Esri IDs and Network URL for this value. For example, 403b6012276b4339af152e9c3319a4b1.
Esri Building ID (triEsriBuildingID) ID that identifies this building on ArcGIS. Obtain this ID from the Esri ArcGIS Portal, see Obtaining the Esri IDs and Network URL for this value. For example, NC_CHARLOTTE_ONE.
Esri Building Default Zoom The zoom level that is appropriate for the defined building. This value varies with the footprint of the building, but 20 is commonly sufficient for most buildings.
Esri Building Default Rotation The rotation that is appropriate for the defined building. This value defaults to 0, which corresponds to North on the screen. However, depending on the shape of the building you might want to rotate it for convenience.
Esri Portal URL (triEsriPortalUrl) The URL of the Esri ArcGIS Server, https://{hostname}:{port}/{context_root}/portal. The URL is determined during the Esri ArcGIS installation, see Setting up Esri. For example, https://host.domain/portal.
Note: If your Esri URLs are longer than 150 characters, you must manually extend the field size for triEsriPortalUrlTX field, see Increasing the size of URL fields for Esri Maps.
Esri Network URL (triEsriNetworkUrl) The URL of the Esri ArcGIS indoor navigation service for this facility. Obtain this ID from the Esri ArcGIS Portal, see Obtaining the Esri IDs and Network URL for this value.
Note: If your Esri URLs are longer than 150 characters, you must manually extend the field size for triEsriNetworkUrl field, see Increasing the size of URL fields for Esri Maps.

Enabling floors

TRIRIGA must be populated with data for each building that has TRIRIGA Indoor Maps defined for them within Esri ArcGIS.

Procedure

On the record for floors, open the Esri Maps tab and enter the value that identifies the floor on ArcGIS in the Esri Floor ID field.
Field Description
Esri Floor ID (triEsriFloorID) See Obtaining the Esri IDs and Network URL for this value. (Ex. NC_CHARLOTTE_ONE.1)

Increasing the size of URL fields for Esri Maps

By default, the EsriNetworkUrlTX and triEsriPortalUrl fields are 150 characters. If your URLs are longer, complete the following steps to increase the default sizes for URL field sizes in the Esri Maps tab. Update the BO and the form and publish your changes.

Procedure

  1. Go to Tools > >Builder Tools > Data Modeler.
  2. On the object browser, open BO Location-> > triBuilding.
  3. Revise the BO.
  4. Select the field that you want to change, update the Size field, and save.
    For example, EsriNetworkUrlTX or EsriPortalUrlTX.
  5. Publish the BO.
  6. Go to Tools > >Builder Tools > Form Builder.
  7. Select Module Location.
  8. Revise the tribuilding form.
  9. Open the form, expand triEsriMaps, and select the Esri Maps section.
  10. Find each field that you updated and apply the same value to the maximum size for that field.
  11. Publish the form.

Configuring the proxy server

To set up your proxy server between TRIRIGA and the Esri server, update the tokenfetcher.config file with the relevant settings.

Before you begin

If you are using a TRIRIGA server on Red Hat OpenShift Container Platform and the IBM TRIRIGA Application Suite GIS Operator, you can get the tokenfetcher.config file information in the arcgis-tas-gis-tririgaproxycfg-secret secret, see Installing the IBM® TRIRIGA Application Suite GIS operator.

Procedure

  1. Set up an Esri user by creating a username and password in the Esri ArcGIS portal for authentication with TRIRIGA.

    For example, username="tririga-maps" and password="tririga-maps-secret".

  2. To get the tokenfetcher.config file from the TRIRIGA dashboard, go to Tools > System Setup > System > Class Loader > EsriIndoorMapsTokenFetcher > tokenfetcher.config, and click Download.
  3. Update the tokenfetcher.config file that is shown in the following example.
    <?xml version="1.0" encoding="utf-8" ?>
    <ProxyConfig allowedReferers="*"
                    logFile="proxy_log.log"
                    logLevel="INFO"
                    mustMatch="true">
      <serverUrls>
            <serverUrl url="https://your-mapping-server.example.com/portal"
                username="$REPLACE_THIS_USERNAME"
                password="$REPLACE_THIS_PASSWORD"
                tokenServiceUri="https://your-mapping-server.example.com/portal/sharing/rest/generateToken"
                rateLimit="600"
                rateLimitPeriod="60"
                matchAll="true">
            </serverUrl>
      </serverUrls>
    </ProxyConfig>

    Replace the username and password with the Esri ArcGIS portal user details.

    The ESRI server, where the Esri map is located, is defined as https://<your-mapping-server.example.com>/portal. If your server has an extra context root, include it before /portal. For example: https://<your-mapping-server.example.com><context-root>/portal.

    The TRIRIGA server requires a secure connection (HTTPS) for the Esri ArcGIS installation. If a self-signed certificate has been used in the ArcGIS installation, or if it has been signed by the DigiCert root certificate authority or a less common certificate authority, then you must allow TRIRIGA to trust the connection the first time you connect, see Configuring Esri security certificates for trusted connections.

  4. Upload the modified tokenfetcher.config file.

Configuring Esri security certificates for trusted connections

Add the Esri certificates to the truststore for your installation. Complete only the steps that apply to your environment.

Before you begin

Note: If you are using a TRIRIGA server on Red Hat OpenShift Container Platform, which is deployed by the IBM TRIRIGA Application Suite Operator, complete the steps in Additional CA certificates instead.

Configure IBM WebSphere Application Server Liberty to add the Esri certificates to the truststore.

If you need to add the root and intermediate certs of the Esri server to the TRIRIGA server, you can use this OpenSSL command to get the certificates.
echo q | openssl s_client -showcerts -connect your-mapping-server.com:443 > your-mapping-server.com.cer

Use the following steps to add the certificates to the truststore and restart the TRIRIGA server.

Procedure

  1. Go to c:\tririga\wlp\bin and see which JRE/JDK is being used by running type run.bat and looking for the JAVA_HOME variable.
  2. Go to c:\program files\java<jre/jdk>\jre\lib\security.
  3. Add the certificates obtained from the OpenSSL command to the trusted certificate authorities file (default password is changeit) with keytool -import -alias esri-certs -file your-mapping-server.com.cer -keystore cacerts.
  4. Check that the certificates were successfully installed in the trusted certificate authorities file with keytool -list -keystore cacerts.
  5. Go to c:\tririga\wlp\bin, stop the server with shutdown.bat, and start the server with run.bat.

Adding the model to a security group

For the UX Locate Perceptive app, nonadmin users must be given access to triLocateMap model.

About this task

You can either create a security group or modify an existing group. The following steps modify the TRIRIGA Request Central - Fundamentals security group to allow users with this group to read, update, create, and delete the triLocateMap model.

Procedure

  1. Log in to TRIRIGA and go to Tools > Administration > Security Manager.
  2. Click TRIRIGA Request Central - Fundamentals security group.
  3. In the displayed window, click Access.
  4. Scroll down, expand Models, and select triLocateMap.
  5. In the Model Access, click Read, Update, Create, and Delete.
  6. Click Save & Close.