(Optional) - Installing Web Reports Standalone

If you run a fresh install of Web Reports V9.5.2 or later, the HTTPS configuration is automatically enabled on port 8083.

After the installation completes successfully, you can switch to the HTTP configuration by changing the value of the _WebReports_HTTPServer_UseSSLFlag setting to 0. For more information, see Customizing HTTPS on Web Reports.

To install the BigFix Web Reports in your production environment, perform the following steps:

  1. From the shell where you extract the server package, move to the installation directory, ServerInstaller_9.5.xxx-rhe6.x86_64 and enter the following command:
    ./install.sh 
  2. Install the Production type by entering 2, because the Evaluation type does not allow to install the components separately:
    Select the type of installation
    [1]  Evaluation: Request a free evaluation license from HCL Corp. 
    This license allows you to install a fully functional copy of the 
    Endpoint Manager on up to 30 clients, for a period of 30 days.
    [2]  Production: Install using a production license or an authorization 
    for a production license.
    Choose one of the options above or press <Enter> to accept the default value: [1]
  3. After reading the License Agreement, enter 1 to accept it and continue.
    Note: If you have already installed the BigFix server, the License Agreement is not displayed.
  4. Select 3 if you want to install the Web Reports component only:
    Select the BigFix features that you want to install:
    [1]  All components (server, client, Web Reports and WebUI)
    [2]  Server and client only 
    [3]  Web Reports only 
    [4]  WebUI and client only 
    [5]  Server, WebUI and client only 
    [6]  Web Reports, WebUI and client only 
    [7]  Server, Web Reports and client only 
    Choose one of the options above or press <Enter> to accept the default value: [1]
  5. To use a local database, enter 1:
    Select the database:
    [1]  Use a local database
    [2]  Use a remote database
    Choose one of the options above or press  <Enter>  to accept the default: [1]
    The local database name is BESREPOR.
    Note:

    To use a remote database for BigFix Web Reports, you must perform the following steps:

    1. Install the Web Reports DB2® server on the remote workstation.
    2. Install a DB2® client on the workstation from where you run the BigFix Server installation
    3. Connect the DB2® server to the DB2® client installed on the workstation from where you run the installation, that is, the port of the DB2® database (default 50000) must be reachable by the workstation where the installation is running.
    4. Provide the following information in the installation procedure:
      1. The remote DB2 node
      2. The DB2 port number
      3. The user name of the local DB2 instance owner for the remote DB2 client and the remote DB2 server.
        Important: Before entering the user names of the DB2 instance owners ensure that the related DB2 instances are up and running. The DB2 instance names used to install the BES Root Server cannot contain the following special characters: blanks, tabs \t, returns \n and ; & | " ' < >
  6. Enter the location where the Web Reports server stores its files:
    Choose the WebReports server's root folder:
    Specify the location for the WebReports server's root folder or 
    press  <Enter>  to accept the default: /var/opt/BESWebReportsServer 
  7. Enter the Web Reports server port number:
    • If you are installing BigFix Version 9.5.2, the default value is 8083 and the HTTPS configuration is automatically enabled:
      Choose the WebReports server's port number:
      Specify the port number or press  <Enter>  to accept the default: 8083
      
    • If you are installing BigFix Version 9.5, the default value is 8080:
      Choose the WebReports server's port number:
      Specify the port number or press  <Enter>  to accept the default: 8080
      
  8. If you are installing BigFix V9.5 or later, you can specify a name of the DB2 instance used by BigFix different from the name of the DB2 user.
    DB2 instance name
    The DB2 instance used by the BigFix requires specific configuration 
    for performance optimization. It is therefore suggested that you use 
    a dedicated DB2 instance. 
    Specify the name of the DB2 instance that you want to use or press <Enter> 
    to accept the default value: db2inst1
  9. Enter the user name for the DB2® Local Administrative user. The default is db2inst1.
    DB2 local administrative user
    Specify the user name of the local DB2 instance owner that you want to use 
    or press <Enter> to accept the default value: db2inst1
  10. Enter the DB2® Local Administrative user password.
    DB2 local administrative user password:
    Specify the password of the local DB2 administrative user:
    
    Enter the password again for verification:
  11. Enter 1 to configure the specified DB2 instance.
    DB2 instance configuration
    The specified DB2 instance can be configured to optimize the BigFix performance. 
    Be aware that the configuration settings will be applied to all databases that belong 
    to the selected DB2 instance.
    [1]  Configure the specified DB2 instance.
    [2]  Skip the DB2 instance configuration.
    Choose one of the options above or press <Enter> to accept the default value: [1]
    
  12. If the local firewall is running, enter 2 to perform the configuration later:.
    Firewall configuration
    The firewall of the operating system is active on the local server. 
    To enable the communication using the specified ports you can:
    [1]  Configure the firewall now
    [2]  Configure the firewall later
    Choose one of the options above or press <Enter> to accept the default value: [2]
    
  13. Specify the masthead file (default is /etc/opt/BESServer/actionsite.afxm):
    Deployment masthead
    Specify the masthead file (masthead.afxm or actionsite.afxm) for your deployment 
    or press <Enter> to accept the default value: /etc/opt/BESServer/actionsite.afxm
    
  14. Specify the DNS name or IP address of the machine on which to install Web Reports. This name is saved in your license and will be used by clients to identify the BigFix server. It cannot be changed after a license is created.
    WebReports server DNS name
    Enter the DNS name of your BigFix WebReports server 
    or press <Enter> to accept the default: 'hostname'
  15. Starting from V9.5.3, you can specify the user name you want to use to install the Web Reports component. You can choose either the root user, as in versions earlier than V9.5.3, or another existing user.
    Use root user for WebReports
    If you specify true, WebReports service will run with root privileges.
    [1]  True
    [2]  False
    Choose one of the options above or press <Enter> to accept the default value: [2]
    If you choose option 2, you can specify a non-root user. This user does not need to have any particular rights or to belong to a group with particular rights to be used as a Web Reports installation user:
    WebReports non-root user name
    Specify the name of the non-root user for WebReports (the user must already exists).
    Note: If you are upgrading from an earlier version, the Web Reports service user remains the same as before the upgrade.
  16. Enter the port number for the DB2 connection to create the DB2 instance:
    ####################
    DB2 Connection:
    Specify the DB2 Port Number or press <Enter>  to accept the default: 50000
The installation runs:
Info: Creating the database for the WebReports Component, please wait ...
Info: The database for the WebReports component was created successfully.
Info: The rpm './repos/BESWebReportsServer-9.5.94-rhel.x86_64.rpm' was installed 
successfully.
Info: Configuring the database for the WebReports component, please wait ...
Info: The database for the WebReports component was configured successfully.
Info: A WebReports administrator was created successfully.
Info: The service 'BESWebReportsServer' started successfully.
The installation of 'BigFix' completed successfully.
The BigFix Web Reports installation is now complete.

You can see installation errors in the BESinstall.log and the BESAdmin command line traces in the BESAdminDebugOut.txt files under the /var/log directory.