Install Hubble Web Server

This section will guide you through the steps necessary to setup a Hubble Web Server. If you have decided to use more than one web server, you will need to repeat these steps for each of them.

Before Deployment Day

Listed below are the actions that should be performed before the deployment date.

Prerequisites

You will need to provide the Web Server’s host machines based on a Windows Server 2016, Windows Server 2019 or Windows Server 2022 platform. For Standard and Platform versions 25.3 and above, Windows Server 2022 and 2025 are required.

The following sections will detail their configuration requirements. Note that these requirements will be tested by the Hubble Web Server installer and the installation will not proceed until the requirements are all met.

Elevated Permissions

Administrator privileges/elevated permissions are required for the user installing Hubble Web on the Windows web server machine as the deployment package, which installs Chef and deploys installation files, requires permission from an Administrator or Administrator user to install on a machine.

Elevated permissions are also required to run the batch file (run.bat, located within the Chef directory), as Chef will check during the configuration of Hubble Web whether or not the correct Windows features are installed, and this check (and any required installs), requires Administrator level permissions.

Anti-Virus/Anti-Malware Software

Any installed and running anti-virus/anti-malware software will need to be temporarily disabled before installing Chef via the deployment package and then configuring Chef via the batch file. The reason for this is that during the checks of installed Windows features, any automatic scan being performed by the anti-virus/anti-malware software will slow down theses checks and the configuration of Hubble Web due to the amount memory being used by the process.

Once configuration is complete and Hubble Web is installed on the windows web server, the anti-virus/ anti-malware software can be enabled again and if necessary a scan of the machine can then be performed to make sure nothing untoward is present.

Add Roles and Features

Following are the Roles and Features that need to be installed as a minimum before Hubble Web can be installed on the Windows machine:

Server Roles

Web Server (IIS)
- Web Server
- Common HTTP Features
  - Default Document
  - Directory Browsing
  - HTTP Errors
  - Static Content
- Health and Diagnostics
  - HTTP Logging
  - Request Monitor
- Performance
  - Static Content Compression
  - Dynamic Content Compression
- Security
  - Request Filtering
- Application Development
  - .NET Extensibility 3.5
  - .NET Extensibility 4.8
  - ASP.NET 3.5
  - ASP.NET 4.8
  - CGI
  - ISAPI Extensions
  - ISAPI Filters
- Management Tools
  - IIS Management Console
  - Management Service

Features

.NET Framework 3.5 Features
- .NET Framework 3.5 (includes .NET 2.0 and 3.0)
.NET Framework 4.8 Features
- .NET Framework 4.8 (pre-installed in Windows Server)
ASP.NET 4.5
Windows PowerShell
- Windows PowerShell 4.0 (pre-installed in Windows Server)
- Windows PowerShell 2.0 Engine (may not be available depending on the windows server version)
- Windows PowerShell ISE

When installing the above Windows features, it is likely that the web server feature will not have been installed yet, meaning that the Server Roles features will require configuration in the Add Roles and Features Wizard, as follows:

In the Add Roles and FeaturesWizard, when you enter the Features part of the Wizard, the screen below is displayed.
Install the IIS Management Console by leaving the Include management tools (if applicable)
checkbox ticked. Then click on Add Features.

The screen below is then displayed (note that the Web Server Role (IIS) heading will have been added to the list of parts of the wizard on the left of the screen under Features). Click Role Services.

The screen then displays the list of role services. Check the checkboxes for the required role services. The minimum required services are listed at the beginning of this topic.
Once all roles and features are selected, install them (either through download from Microsoft or from provided windows files).

Internet Access

Internet access may be required when installing the Windows features above, if they require downloading from Microsoft, or when installing Windows updates. If a proxy is required to access the internet, this will need be configured on the web server. Once Hubble deployment has finished, internet access can be removed again.

Windows Updates

After the minimum Microsoft components and minimum roles and features have been installed as described above, all Windows updates will need to be installed, as updates to the .NET Framework are required, including .NET Framework 4.8.

Minimum Microsoft Components Required

As well as the Roles and Features required, an additional Microsoft Component needs to be installed before Hubble Web can be accessed successfully. After all the available Windows updates are installed, please check whether the following is installed, and install it manually if not:

IIS URL Rewrite Module - This will not be installed as standard and will need to be installed by downloading the module from:
https://www.iis.net/downloads/microsoft/url-rewrite

Run the Hubble Web Installer

This standard Windows installer includes the prerequisite test script which you should run before deployment.

In order to install Hubble Web, you must log into the Windows server machine as an Administrator or as a user that has Administrator rights.
Copy or download the installation file to Windows server, either into a new directory or in the Downloads directory as required. The file is called:
Hubble_Web_<version number>_<ERP>.exe,

...where <version> will be the current version and <ERP> will be the platform (i.e. JDE or EBS).
Double-click on the installation file to install the relevant files for chef, cookbooks, and to set up the installation for the next step.
During the installation, you will see a command prompt showing the current status of the installation, for example:

You will be prompted to enter the IP address or DNS name of your application server:
You will be prompted to enter either Yes or No to encrypt the password. If no response is provided within 120 seconds, No will be selected as the default option.

Verify the Prerequisites

Open a Windows PowerShell command prompt and navigate to the directory C:\Insight. Run the command:

.\DVT.ps1 pre

Complete the Setup of Hubble Web Server

Note: Install the Application Server and start its services before deploying this part of the web server.

Open C:\chef and run the Run.bat file. After the commands execute, check C:\chef\solo.txt. If successful, logs similar to the following image will appear.

Run the following command:

C:\Insight\DVT.ps1 all C:\chef\run-list.json

You should now be able to access the Hubble Web login page at:

http://<app_server_ip_or_DNS>

Configuring Postgres Authentication After Upgrade

Issue Description

After upgrading Postgres, the Chef installer may fail with the following error:

Authentication method not supported (Received: 10)

This error prevents Hubble from completing deployment.

Root Cause

The error occurs when the Postgres password encryption method is set to scram-sha-256 instead of md5. Hubble requires md5 authentication. After a Postgres upgrade, the encryption method and the pg_hba.conf authentication rules may revert to or remain set to scram-sha-256, which is not supported.

Resolution in Version 25.4 and 26.1

Complete the following steps to configure Postgres authentication correctly and re-run the Chef installer.

Step 1: Enter Postgres as a Superuser

Run the following command on the Linux host:

docker exec -it hubble-hubble_repository-1 psql -U postgres

You should see the following prompt:

postgres=#

Step 2: Set Password Encryption to md5

Run the following command:

ALTER SYSTEM SET password_encryption = 'md5';

To verify the setting was saved, run:

SELECT name, setting FROM pg_settings WHERE name='password_encryption';

Exit the prompt:

\q

Step 3: Ensure pg_hba.conf Uses md5

Check the file by running:

docker exec -it hubble-hubble_repository-1 bash -c "cat \$PGDATA/pg_hba.conf | tail -5"

The output must include:

host all all all md5

If the output shows scram-sha-256 instead of md5, edit the file:

docker exec -it hubble-hubble_repository-1 bash
		vi $PGDATA/pg_hba.conf

Change scram-sha-256 to md5, then save and exit.

Step 4: Restart the Postgres Container

Run the following command to apply the changes:

docker restart hubble-hubble_repository-1

Step 5: Verify Postgres is Running

Run the following command to confirm the container restarted successfully:

docker ps | grep hubble_repository

Step 6: Reset the Hubble User Password

After restarting Postgres, you must reset the Hubble user password to recreate it using md5 encryption. Run the following commands:

docker exec -it hubble-hubble_repository-1 psql -U postgres

ALTER USER hubble WITH PASSWORD 'ddyNYiLgs8w3';

\q

Step 7: Test Login as the Hubble User

Run the following command to confirm the login succeeds:

docker exec -it hubble-hubble_repository-1 psql -h localhost -U hubble -d hubble_repository

Enter the password when prompted. You should see the following prompt:

hubble_repository=>

Step 8: Run the Final Verification Command

Run the following single command to confirm both the password encryption setting and the pg_hba.conf configuration are correct:

docker exec -it hubble-hubble_repository-1 bash -c "psql -U postgres -c 'show password_encryption;' && tail -5 \$PGDATA/pg_hba.conf"

The expected output is:

password_encryption
			--------------------
			md5
		host all all all md5

Required Action

Once the verification command returns the expected output, re-run the Chef installer. The error Authentication method not supported (Received: 10) will be resolved.