Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

App Hosts

 

An App Host is a managed host that is dedicated to running apps. App Hosts provide extra storage, memory, and CPU resources for your apps without impacting the processing capacity of your JSA Console. Apps such as User Behavior Analytics with Machine Learning Analytics require more resources than are currently available on the Console.

The App Host replaces the App Node. Unlike the App Node, JSA manages all updates to the App Host, and you can include the App Host in your high-availability deployments.

Note
  • You can have only one App Host in your deployment.

  • If you have an environment that uses Network Address Translation (NAT), both the Console and the App Host must exist within the same NAT Group.

  • Port 5000 must be open on your Console.

  • For a software installation of an App Host, create a /store partition that uses approximately 80% of the available storage capacity.

App Host specifications

The following table shows the minimum requirements and suggested specifications for an App Host.

Note

If you are using some larger apps, such as Pulse and User Behavior Analytics with Machine Learning, the minimum requirements are insufficient.

CPU cores

4

8 or more

16 or more

Installation Scenarios

If you are installing an App Host and you do not have an App Node in your deployment, see Installing an App Host.

If you have an App Node and you are upgrading to JSA 7.3.2, see Migrating from an App Node to an App Host.

Installing an App Host

You can run apps on an App Host instead of your Console to lessen the processing load on the Console.

  • Ensure that all apps on your system are updated.

  • Resolve any issues with applications in an error state or not displaying properly

  • Schedule a maintenance window for this task and ensure that users do not do any of the following during the migration.

    • Do not install or uninstall apps.

    • Do not do a full deploy.

    • Do not do a restore.

    • Do not delete the App Host.

    • Do not re-IP the Console.

  1. Type root at the login prompt to start the installation wizard. Type password if you are prompted for a password.
  2. Accept the End User License Agreement.
  3. Select App Host Appliance for the appliance type.
  4. For the type of setup, select Normal Setup (default), and set up the time.
  5. Select the Internet Protocol version:
    • Select ipv4 or ipv6.

  6. If you selected ipv6, select manual or auto for the Configuration type.
  7. Select the bonded interface setup, if required.
  8. Select the management interface.
  9. In the wizard, enter a fully qualified domain name in the Hostname field.
  10. In the IP address field, enter a static IP address, or use the assigned IP address.
  11. If you do not have an email server, enter localhost in the Email server name field.
  12. Enter a root password that meets the following criteria:
    • Contains at least 5 characters

    • Contains no spaces

    • Can include the following special characters: @, #, ^, and *.

  13. Click Finish.
  14. Follow the instructions in the installation wizard to complete the installation.

    The installation process might take several minutes.

  15. Add this managed host to your deployment and deploy changes.

Changing Where Apps are Run

Change where apps are run when you add an App Host to your deployment.

Apps are disabled during the transfer process. Apps are enabled when the transfer is complete.

If you don't have enough disk space or memory available on the Console, moving your apps from the App Host to the Console moves only the apps themselves, but not app data. Any app data remains on your App Host, and apps do not start on the Console when the transfer is complete. Apps start again when they are transferred back to the App Host.

  1. Sign in to the JSA user interface.
  2. Click Admin.
  3. On the System and License Management screen, click the Click to change where apps are run link.
  4. 4. Choose where apps are run.
    • Click App Host to transfer apps to the App Host.

    • Click Console to transfer apps to the Console.

    Note

    The more apps and app data you have, the longer the transfer takes.

Migrating from an App Node to an App Host

If you are upgrading to JSA 7.3.2 and you have an App Node in your deployment, you must back up your App Node data before the upgrade. App Nodes are no longer supported.

  • You must contact Juniper Customer Care to ensure that the required entitlements are set up for your migration from App Node to App Host.

  • Ensure that all apps on your system are updated.

  • Resolve any issues with applications in an error state or not displaying properly.

  • Schedule a maintenance window for this task and ensure that users do not do any of the following during the migration.

    • Do not install or uninstall apps.

    • Do not do a full deploy.

    • Do not do a restore.

    • Do not delete the App Host.

    • Do not re-IP the Console.

  1. Use ssh to log in to your system as the root user.
  2. Mount the JSA 7.3.2 SFS on your Console to /media/updates.
  3. Create a backup archive of your App Node data by typing the following command on your Console.

    /media/updates/supplementary_scripts/app_node_data_backup.py

    The script outputs a backup archive on the App Node that is called /store/app-dockervolumes-<date_and_time_stamp>.tgz, and an MD5 checksum. The script also removes the App Node from your deployment.

  4. Make a copy of the backup archive and note the MD5 checksum.
  5. Upgrade your JSA console to 7.3.2.
  6. Install your App Host and add the App Host to your deployment. See Installing an App Host.
  7. Copy the backup archive to the App Host.
  8. Restore your App Node data on the App Host by typing the following command on your Console.

    /opt/qradar/bin/app_node_data_restore.py -a <pphost_IP_address> - f <path_to_archive_on_apphost>

    The script checks the integrity of the archive by confirming the MD5 checksum, and then extracts the archive to the /store/docker/volumes directory.

  9. Sign in to the JSA user interface.
  10. Click Admin.
  11. On the System and License Management screen, click Migrate.
  12. Click Proceed to complete the migration from the App Node to the App Host.Note

    The more apps and app data you have, the longer the transfer takes.

    Your apps are running on the App Host.

Removing an App Host

You can't remove an App Host if you have any apps that are running on it.

  1. Move your apps back to the Console. See Changing Where Apps are Run.Note

    If you don't have enough disk space or memory available on the Console, moving your apps to the Console moves only the apps themselves, but not app data. Any app data remains on your App Host.

  2. Click Admin.
  3. On the System Configuration screen, click System and License Management..
  4. In the Display list, select Systems.
  5. Select your App Host.
  6. On the Deployment Actions menu, click Remove Host.