Configuring SaaS Express

The following topics are discussed in this section:

• Prerequisites
• Best Practices
• Configuring a Custom SaaS Application Profile
• SaaS Express Configuration Workflow
• Modifying the PBR Policy

Prerequisites

• SaaS Express feature requires Advanced Gateway license. For more information, see HPE Aruba Networking Central Licenses Feature Details.

• SaaS Express is only supported on the Branch Gateway. For more information, see Provisioning Gateways.
• The Branch Gateway must be running AOS-8.4.0.0-1.0.6.0 or a later software version. However, the SaaS Express feature has been evolving over time and all the capabilities described in this guide may not be available on older versions. The content of this guide is based on running SaaS Express with AOS-8.7.0.0-2.3.0.0. For more information on how to upgrade, see Managing Firmware Upgrades.

Best Practices

• Ensure that you assign a site to the gateway before enabling SaaS Express. If you assign the site after enabling SaaS Express, you can view the site in the monitoring dashboard only after two hours.
• Ensure the Deep Packet Inspection (DPI Deep Packet Inspection. DPI is an advanced method of network packet filtering that is used for inspecting data packets exchanged between the devices and systems over a network. DPI functions at the Application layer of the Open Systems Interconnection (OSI) reference model and enables users to identify, categorize, track, reroute, or stop packets passing through a network. ) is enabled on Branch Gateway groups. By default, the DPI is enabled on Branch Gateway groups. For more information, seeUsing Deep Packet Inspection.
• Ensure the uplink interfaces are configured and the wired uplink is functional. For more information, seeUplinks for Branch Gateways.

• Ensure the App Performance Monitoring is enabled on the Branch Gateways. For information about how to enable App Performance Monitoring, see Enabling App Performance Monitoring.