Managing Web App Mappings

Create web app categories and web app mappings that you can link to a specific category.

Accessing Web App Mappings

  1. Log into the SOTI XSight web console as administrator.

  2. From the main menu, select Operational Intelligence.

    Select Operational Intelligence
  3. Open the main menu again.

  4. Select Manage Web App Mappings.

    Select Manage App Mappings

Manage Web App Categories Tab

SOTI XSight automatically installs a list of categories and URLs. You cannot delete the Default category.

The Web App Categories tab

Adding a Category

You can add new categories by selecting the Add New Category button (see red box in screenshot above). The category name must be unique.

Adding a new Category

Editing a Category

You can rename a category by selecting its name and entering a new name.

Deleting a Category

You can delete any category except the Default category. When you delete a category, any web apps associated with it are re-mapped to the default app category.

To delete a category, selecting the Delete button beside the category's name.

Deleting a category

Manage the Web App Mappings Tab

Use the Mappings tab to select and categorize the applications that SOTI XSight tracks.

Toggle Collect Data on if you want SOTI XSight to track usage behavior for the web app.

The Mappings tab

The following functions are available on the Web App Mapping tab:

Control Description
Search Search the Web App Mappings by Web App Name
Category Filter Filter apps by category
Delete Delete selected Web App Mappings
Save Saves all changes to the database

Creating a New Mapping

To create a new mapping, select the Add New Mapping button (see red box in screenshot above). Enter the Web App Name, Web App Category, Path or Collect Data. ToggleCollect Data on to collect information about the web app.

Adding a new mapping

Editing a Mapping

You can edit a mapping's name and its category. To edit a mapping, select a row and edit the Web App Name, Web App Category, Path or Collect Data fields.

Deleting a Web App Mapping

Select one or more rows in Web App Mappings tab and select the Delete Selected button in the bottom left of the panel.

Formatting Path Matching Criteria

Format: <Protocol><Host Name><Port><Resource Path>

Protocol

This indicates the protocol used to access the resource. When providing a path in web app mappings, this field is optional. If no scheme is provided, the protocol is not be considered when matching the paths. In the protocol field, choose from the following values:
  • http://
  • https://
  • file://

Host Name

Users must provide a domain or a IP address, not both. The IP address must be in IPv4 format.

The domain is mandatory if an IP address is not provided. This section is made up of two or more sections separated by dots. Each section in the domain must be an alphanumeric string or an asterisk wildcard. See the section Using the Asterisk Wildcard below for more information.

  • An example of a valid domain name without an asterisk wildcard: www.soti.net

    • Matches: https://www.soti.net and http://www.soti.net

  • An example of a valid domain name field with an asterisk wildcard: *.soti.net

    • Matches: https://pulse.soti.net and https://www.soti.net

Port

This is an optional field that can be used to match paths to non-standard protocol ports. This has to be a colon followed by a number between 0 and 64738.

  • An example of a valid port number: :8080

Resource Path

This is an optional field. Each part of this section is separated by a forward slash '/'. Each section of the resource path must be one or more characters or be represented by an asterisk. See the section Using the Asterisk Wildcard below for more information.

  • Example of a path without asterisk: www.soti.net/products/soti-xsight

    • Matches: https://www.soti.net/products/soti-xsight and http://www.soti.net/products/soti-xsight

  • Example of a path with an asterisk: www.soti.net/products/*/

    • Matches: www.soti.net/products/soti-xsight and www.soti.net/products/soti-mobicontrol
    • Does not match: www.soti.net/products/soti-xsight/example-subpath

  • Example of a path with an asterisk to match all subpaths: www.soti.net/products/*

    • Matches: www.soti.net/products/soti-xsight, www.soti.net/products/soti-mobicontrol and www.soti.net/products/soti-xsight/example-subpath
    • Does not match: www.soti.net/products

Using the Asterisk Wildcard

Asterisks match an entire level of a domain or path. They cannot be used in combination with other characters or wildcards to define a level in the domain or the path.

Note: When the path matching criteria ends with a /*, the last asterisk matches any characters.

Examples of invalid of use of the asterisk:

  • www.soti.net/**

    • Invalid because there are more than one asterisk next to each other

  • www.soti.net/pro*/soti-xsight

    • Invalid because the asterisk cannot be used in combination with other characters to define a level in the domain or resource path

Examples of valid uses of the asterisk:

  • www.soti.net/products/*

    • This matches any subpath of www.soti.net/products/
    • Matches: www.soti.net/products/soti-xsight, www.soti.net/products/soti-mobicontrol and www.soti.net/products/soti-xsight/example-subpath
    • Does not match: www.soti.net/products

  • www.soti.net/products/*/

    • Matches any subpath that’s one level deep of www.soti.net/products/
    • Matches: www.soti.net/products/soti-xsight and www.soti.net/products/soti-mobicontrol
    • Does not match: www.soti.net/products/soti-xsight/example-subpath

  • https://*.soti.net/*

    • Matches any subpath of any subdomain one level higher than soti.net that’s connected using the https protocol
    • Matches: https://pulse.soti.net/support/soti-xsight, https://discussions.soti.net/category/soti-mobicontrol/2c28b187-70e4-4936-9csc-a76000715619 and https://www.soti.net/products/soti-mobicontrol
    • Does not match: https://pulse.soti.net