Example routing scenarios for BlackBerry Dynamics traffic

The following scenarios are examples of common configurations:

Scenario

BlackBerry Dynamics connectivity profile

Web proxy configuration for BlackBerry Proxy

App-specific settings

Route traffic to specific servers or domains through BlackBerry Proxy.

Appropriate for scenarios where some internal app servers must be accessible to BlackBerry Dynamics apps, but general traffic to public servers can remain direct.
  • Default allowed domain route type: Direct
  • Allowed domains: Add the internal domains to route through the BlackBerry Proxy and select a cluster.
  • Additional servers: If needed, add specific server names and select a cluster.

No configuration necessary.

No configuration necessary.

Route all traffic through the BlackBerry Proxy and then through a web proxy server.

Appropriate for organizations that require all traffic from work apps to be routed internally.

Default allowed domain route type: BlackBerry Proxy cluster

Use a manual web proxy server configuration or a PAC file.

No configuration necessary.

Route some traffic internally for most apps but configure a proxy server specifically for web browsing using BlackBerry Access.

Appropriate for organizations that require traffic for apps to be routed internally, but require browser traffic to be routed through a web proxy server.
  • Default allowed domain route type: Direct
  • Allowed domains: Add the internal domains to route through the BlackBerry Proxy and select a cluster.
  • Additional servers: If needed, add specific server names and select a cluster.

If BlackBerry Proxy servers don't have direct access to the Internet, or if a proxy is required for BlackBerry Dynamics NOC connections, configure a web proxy server as needed.

In the app configuration for BlackBerry Access, select Enable Web Proxy and Use Proxy Auto Configuration.