Installation Procedure

Use this procedure to install the WebUI on BigFix Platform versions 9.5.5, or later.

The WebUI Installation Fixlets default to SQL Server on Windows systems and DB2 on Red Hat Enterprise Linux systems. Allow adequate time for the WebUI service to start following the installation; index construction and other process need to complete before you can use the WebUI.

Before you start:

  • Review the WebUI deployment and hardware requirements, and verify that your environment is ready. For example, if the database account permissions are not correct, the WebUI will not start correctly.
  • Complete the BigFix Platform installation to V10. For more information, see the BigFix Installation Guide.
  1. On the BES Support site, locate the Install BigFix WebUI Service Fixlet that is relevant for your root server version. For example, if you are running Platform Version 10, use the Fixlet Install BigFix WebUI Service (Version 10).
  2. Have the host name or IP address of server where the WebUI will be installed ready.
    • The default installation directories for the WebUI are:
      • Windows machines:
        C:\Program Files (x86)\BigFix Enterprise\BES WebUI
      • Red Hat Linux machines:
        /var/opt/BESWebUI and /opt/BESWebUI
  3. If you are not using the defaults, have the WebUI target drive and directory ready.
    • On Windows systems, the specified targets are created automatically.
    • On Red Hat Linux systems:
      1. Create the target drive and directory.
      2. Symlink the default directory to the target directory.
  4. Have your database information ready. Routine database credential changes can cause the WebUI initialization to fail, so the account used to access the WebUI database should be used exclusively for that purpose.
    • User name
    • Password
    • Host name or IP address of the BigFix database server
    • SQL Server users:
      • If you are connecting to the SQL Server database with a Windows credential, enter the NetBIOS domain name in the Specify Database Username field.
      • If you are connecting to SQL Server with an SQL credential, the Specify Database Username field shows by default sa.
    • MSSQL users can connect to a named database instance. Enter the instance name in the Specify SQL Server Named Instance field using the syntax DATABASE\INSTANCE, where:
      • DATABASE = a DNS resolvable name or IP address.
      • INSTANCE = a valid database instance on which BFEnterprise (the BigFix database) is installed.
    • If you change the account password after installing the WebUI, run the Deploy/Update WebUI Database Configuration Fixlet. The same Fixlet can also be used to repair a credential-based initialization failure.
    • IBM DB2 users:
      • Specify the DB2 database username.
      • Ensure that the DB2 configuration parameter extended_row_sz is set to ENABLED. Starting from DB2 10.5, this parameter is ENABLED by default; but, it can be manually set to DISABLED or can be DISABLED, if DB2 has been upgraded from version 10.1 or earlier. It must be ENABLED for all Linux Server installations; otherwise, the WebUI cannot start successfully.
  5. Verify that the WebUI ports are available on the target machine where the WebUI will be installed, or make note of the ports you want to use. Port 52315 on the root server is used to allow communication between the root server and the WebUI. All network firewalls between the two machines must allow use of port 52315 as well.
    • The default HTTP redirect port is 80.
    • The default HTTPS port is 443.
  6. If you are installing the WebUI on a remote server and configuring WebUI to work with SAML, set the _WebUI_AppServer_Hostname key of the BigFix server computer to the host name of the computer where the WebUI is installed.
  7. Deploy the Fixlet.

Image of the WebUI Installation Fixlet for V10

Image of the WebUI Installation Fixlet for V10

Post installation notes:

  • If the Fixlet fails, revoke the certificates that it generates and sends to the target machine.
  • If you have encryption enabled for your MSSQL server, you will need to apply the client setting _WebUIAppEnv_MSSQL_CXN_ENCRYPT = 1 on the remote WebUI server.
  • If WebUI is installed on a Linux machine, to display all localized messages correctly, on the machine where WebUI is installed, create the client setting _WebUIAppEnv_LANG and set the preferred language; for example, ja_JP.UTF-8 for Japanese.
  • If the Fixlet is successful, port 52315 on the root server is used to allow communication between the root server and the WebUI. All network firewalls between the two machines must also allow use of port 52315.
  • Start, stop, and restart the WebUI process on a remote machine using services.msc on Windows, or through the terminal in Red Hat Linux. If stopped, the Fixlet 2562 - BES WebUI Service not Started can also be used to start the WebUI.