Home
WebUI Administration Guide
Read this guide for information about installing and administering the WebUI.
Performance
This chapter provides an introduction to some tools for managing performance problems you might encounter with the WebUI. For a detailed discussion of BigFix and WebUI performance topics and tools, including planning, monitoring, and maintenance, see the BigFix Capacity Planning Guide.
Caching
Caching is used to improve WebUI response times. Cached data is processed, stored, and refreshed at a specific interval.

WebUI Administration Guide
Read this guide for information about installing and administering the WebUI.
- Introduction
  This guide is intended for BigFix Master Operators and those who administer an BigFix deployment. If you are looking for information about using the WebUI, see the BigFix WebUI User's Guide.
- Deployment Requirements
  This guide contains information and procedures for installing the WebUI on BigFix Platform V10.0.0 or later. The WebUI is supported on BigFix Platform V10.0.0 and later versions.
- WebUI Installation
  Use these procedures to install or upgrade the WebUI on BigFix Platform version 10 or later. Before you start the procedure:
- Remove the WebUI Service
  Use this procedure to remove the WebUI from BigFix Platform.
- Provisioning Users
  Use permission settings in the WebUI and the BigFix Console to control access to the WebUI and its functions.
- Managing Application Updates
  You can manage application updates through Application Update Manager.
- Editing Dashboards
  Use the WebUI’s editing tools to customize the WebUI Overview and Executive Overview dashboards.
- Performance
  This chapter provides an introduction to some tools for managing performance problems you might encounter with the WebUI. For a detailed discussion of BigFix and WebUI performance topics and tools, including planning, monitoring, and maintenance, see the BigFix Capacity Planning Guide.
  - Operator Performance
    Use these techniques to minimize operator-related delays.
  - Environment Upgrades
    The BigFix Capacity Planning Guide provides guidelines for CPU allocation, CPU scaling, virtualization and many other aspects of system planning and maintenance to ensure the resources allocated to the WebUI are balanced and healthy. For example, use system monitoring to determine whether system stress is due to operator workloads, or inadequate resource allocation.
  - Database Management
    Database maintenance is critical to WebUI health. See the BigFix Capacity Planning Guide for information and tools specific to your platform.
  - Caching
    Caching is used to improve WebUI response times. Cached data is processed, stored, and refreshed at a specific interval.
- Log Locations
  All WebUI logs are stored in one default location. Logs are stored on the WebUI Server in the following locations (unless changed by the server setting _WebUI_Logging_LogPath).
- WebUI Server Settings
  Create or modify server settings on your WebUI server to control advanced aspects of the WebUI. These settings are for advanced users only and can be used to help troubleshoot problems or adjust behaviors to optimize performance.
- SAML 2.0
  BigFix supports SAML 2.0. SAML authentication is an application login mechanism that uses a configured Identity Provider (IdP) to authenticate users.
- Troubleshooting
  Read this section for information about any known issues using the WebUI application.
- WebUI and Distributed Server Architecture (DSA)
  Understand how to work with WebUI in Distributed Server Architecture (DSA).
- Supported Patch Sites
  A subset of BigFix patch sites is supported in the WebUI.
- Support
  For more information about this product, see the following resources:

Caching

Caching is used to improve WebUI response times. Cached data is processed, stored, and refreshed at a specific interval.

(While most WebUI data appears in real time, a few WebUI counters, such as the number of applicable devices, require complex calculations.) Processing time goes up as device counts go up, and large deployments can be affected. The cached values are:

Applicable Patch count on the Device list
Applicable Device count on:
- the Patch list
- the Software Package list
- the Custom Content list
- Document Overviews for individual patch, software, and custom content.
Open Deployment count on:
- the Content list
- the Custom Content list
- the Patch list
Deployment information on the device list

_WebUIAppEnv_SP_QUEUE_CONCURRENT The setting _WebUIAppEnv_SP_QUEUE_CONCURRENT also affects WebUI caching. It limits the number of stored procedures that run simultaneously per App in the background that update cache values while users are browsing the WebUI. The default value is 5.

Cached values are flagged. For example, the relevant patch count on the Device list may display a message, Last updated 4 minutes ago. Click here to see the most up-to-date data. Refreshing the browser retrieves the latest data from the cache.

The default refresh interval is 10 minutes. This interval, also called the cache Time To Live (TTL) value, determines how often cache results are invalidated. Ten minutes is considered a good trade-off between cache freshness and response time impact.

To change the interval, use the client setting _WebUIAppEnv_CACHE_TTL. Modifying the TTL value requires significant understanding of system load and operator concurrency, and is only recommended for administrators willing to monitor and tune the configuration. Enter the wanted interval period in seconds. The default interval is 600; the minimum interval is 180 (3 minutes).

Increase the interval to establish longer periods between cache refreshes. Customers with large deployments and lots of activity can lengthen the interval for fewer refreshes and lower impact on system resources. Activities that change applicable counts will consume more resources. These include:

Increasing the number of devices reporting in to BigFix.
Intensive patching activities, for example, on Patch Tuesday.