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.

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:

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.

For the best performance, install the WebUI service on a dedicated machine. Running BigFix services and the WebUI database on a single machine will slow response times.

Optimizing User Permissions

In the WebUI, if non-master operators have similar permissions, WebUI is able to take advantage of that fact and use shared values for caching (see section on Caching).

Specifically, if non-master operators have identical permissions with regards to:

Visible sites
Visible Computers
Assigned Roles

Non-master operators are able to share caches. Thus, to optimize WebUI performance, best practice is that the deployments must have groups of non-master operators that have their permissions defined via groups and roles. Try to avoid assigning individual operators, individual site or computer permissions. Also, try to avoid having content be assigned to individual operator sites as much as possible.