Set up an Autonomous DEM Application Test

From the Prisma Access app on the hub, select
Autonomous DEM
Applications
.
To enable the tests for a Mobile User group,
Click
Add new App Test
.
Click the
Applications Tests
tab.
Under
Source
, select
Custom
from the
Mobile Users
dropdown.

Click in the
Search Mobile Users and Groups
text box.
Select the check box(es) for one or more users and/or user group(s) on which you want to enable the test.
Follow the instructions from step 3 onwards below.
Click
Add new App Test
or, click an app name to view the Health link that corresponds to a specific application in the application list.

Name
the new app test.
You have the option to run application tests only for Mobile Users or only for Remote Sites or for both.
Mobile Users:
Define the Source Users that you want to run this app test. By default, all licensed ADEM users are assigned to run the test. If you want to limit this app test to specific users, click
Mobile Users
under
Source
and select
Custom
and click in the
Search Mobile Users and Groups
text box, then select the users and/or groups you want to run the test.
Remote Networks:
Select the remote site. By default, all remote site licenses are selected. You can also choose to run the tests on all remote sites or only particular remote sites. Define Advanced Options as needed. By default ADEM sets the Network Test Options and Web Test Options based on the applications you selected. However, you can customize these options if needed in your environment.
Identify the application you want to test as the
Target
. If you selected an application from the applications list, the application name is automatically populated. Otherwise, begin typing the Application name to see a list of applications from which to select. If you don’t see the application you want to create a test for, you can create a custom application in your Prisma Access environment using Panorama or the Cloud Management App. Once you have created the custom application and successfully committed, you will see your app under the
Applications
dropdown menu on the
New App Test
page in ADEM.
To edit an app test, click
Applications
Application Tests
tab and click on the application test name that you want to edit. On the
Edit App Test
page, click
Add/Edit Target
under the
Target
section and add the domain URL or the IP address for the target and click
Save
. The test starts running.

Be sure to configure each test with one unique application for which you provide one domain name.
After you create the tests, you can view a summary of all the tests created in the
Applications
Application Test
tab.
The tests get a priority assigned to them in the order that they were created. For example, the first test you create gets a priority order 1. The next test you create gets priority order 2 and so on. The tests are pushed to the mobile users and remote site according to the priority they are assigned. If the remote site devices have available capacity for the test, the test will be enabled. Otherwise, the remote site gets moved to the
Excluded Remote Sites
for the test.
Even though the tests are assigned to both Mobile Users and Remote Sites, the priority in which the tests are pushed to the device is important particularly to the remote sites, since each device in a remote site is capable of running a different number of tests depending on the device size. So, if you have created a test, for example Test A which has a priority of 8, and attached it to multiple remote sites all of which can run Test A, if one of those sites, for example San Jose, has reached its limit on how many tests it can run, Test A will not be pushed to the site. That remote site (San Jose) will get moved under the
Excluded Remote Sites
column. But if you absolutely must run the Test A, you can change the priority of Test A from 8 to a higher location in the table, for example to the top of the list by clicking on the dots to the left of the check box and dragging and dropping it to the top of the list. Alternatively, you can select its check box and click the up arrow at the bottom of the page. You will see its priority change only after you click
Save
. Now Test A will get a higher priority and will be pushed to the San Jose remote site before the remaining tests that follow Test A in the table. This would mean though that the San Jose remote site will now be excluded in the configuration push from some other lower priority test (lower priority compared to Test A) that is pushed to it.
For a list of devices and the maximum number of tests they are capable of running, refer to the table in Get Started for Remote Networks.

Select the check box to the left of the test to
Delete
,
Enable
, or
Disable
a test. Once you disable a test, that test will not be executed any more until you enable it again.