Bootstrap FreeKB - IBM WebSphere - Resolve "A WebGroup Virtual Host to handle has not been defined"
IBM WebSphere - Resolve "A WebGroup Virtual Host to handle has not been defined"

Updated:   |  IBM WebSphere articles

Let's say the following is in the HPEL or SystemOut log. This error appears when attempting to navigate to the URL of a WebSphere application, such as https://www.example.com:12345/context_root.

Ensure the application has been deployed to the WebSphere application server.

  1. In the WebSphere admin console, expand Servers > WebSphere application servers.
  2. Select the application server.
  3. Selected Installed application.
  4. Ensure that the application being requested is listed.

 

Ensure you are requesting a valid context root.

  1. In the WebSphere admin console, expand Applications > Application Types.
  2. Select Websphere enterprise applications.
  3. Select your application.
  4. Select Context Root for Web Modules.

In this example, the context root is "/beta", which means that the URL being used should end with "beta", such as https://www.example.com:12345/beta.

 

Determine the virtual host being used by the application.

  1. In the WebSphere admin console, expand Applications > Application Types.
  2. Select Websphere enterprise applications.
  3. Select your application.
  4. Select Virtual hosts, and make note of the virtual host name.

 

Ensure the port has been enabled.

  1. In the WebSphere admin console, expand Environment > Virtual hosts.
  2. Select the virutal host.
  3. Select Host Aliases.
  4. If the port being used by the application is not listed, add the port.

 

Ensure HTTP/HTTPS is enabled.

  1. In the WebSphere admin console, expand Servers > Server Types.
  2. Select Websphere application servers.
  3. Select your application server.
  4. Expand Web Container Settings.
  5. Select Web container.
  6. In the Default virtual hosts drop-down, select the virtual host being used by your application.
  7. Select Web container trnasport chains.
  8. If HttpQueueInboundDefault is not enabled, and you want to use HTTP, enable it.
  9. If HttpQueueInboundDefaultSecure is not enabled, and you want to use HTTPS, enable it.

 

If you've not yet added your admin agent username and password to the web server, add your admin agent username and password.




Did you find this article helpful?

If so, consider buying me a coffee over at Buy Me A Coffee



Comments


Add a Comment


Please enter 3881a0 in the box below so that we can be sure you are a human.