Application Settings

When you select the Custom Apps as the application type, you'll define traffic destinations by IP address range, domain name, and protocol. This approach is useful for internal services, specific IP ranges, and unique protocols used in your network.

Consider using variables to represent values. If you see the VAR label next to a field heading, you can enter variables in that field to match destinations without having to enter specific values.

It's a good practice to create an application with a less specific address. For example, you might have a data center with a 10.0.0.0/8 prefix. A more specific address can be contained within this prefix for more specific path selection.

The following table provides examples.

Applications represent the endpoints users are trying to reach—these can be IPs, domain names, or URLs. URL patterns help define these destinations more flexibly. The Juniper Mist cloud provides a list of URL categories based on types (example: shopping, sports) and grouped by severity (all, standard, strict). You can use the URL categories to define an application. Additional sub-categories offer even more granular filtering for application creation. You can select a single or multiple URL categories for an application.

For example: You can create an application and name it "social media" and select URL categories as Social Networking or Instant Messaging. Then you can create policies to block or restrict access during work hours.

When adding an application, you can use the URL Categories type to define destinations by categories such as entertainment, shopping, and sports.

For example, create an application called Social Media and select URL categories Social Networking and Instant Messaging. Later, on the Application Policies page, create policies to block or restrict access to these URLs during work hours.

Figure 1: URL Category Examples

When defining applications, you can enter custom URLs for services not covered by predefined applications.

You can enter:

• Exact domain names. example.com

• Wildcard domains using an asterisk. Example: *.example.com

  With this approach, you can group related services under one application. For example, *.google.com includes Gmail, Drive, Meet, and other Google sites.

• Use a comma separator to specify multiple URLs.

• You can specify up to 15 URL patterns for an application.

• Only the * wildcard is supported.

• You can view the supported patterns by hovering the mouse over the tooltip icon. Note that you can use the https://abc.com pattern only for SRX Series devices.

  Figure 2: Custom URLs

Under Advanced Settings, specify the Traffic Type. Keep Default for general traffic, select a preset traffic type, or select Custom.

• If you select a preset traffic type, you'll see the values for settings such as failover (SSR only), latency, jitter, and loss.

  Note:

  For Apps and URL Categories, you can only select a specific traffic type after you select the Override Settings check box.

• If you select Custom as the traffic type, also select a Traffic Class, and then adjust the preset values as described in the following table.