+

Search Tips   |   Advanced Search

Access WebSphere Portal through another HTTP port

By default WebSphere Portal is configured to be accessed through the internal HTTP port in WebSphere Application Server. For example...

    http://hostname.example.com:10039/wps/portal

The default host name and port used by WebSphere Portal are specified by the WpsHostName and WpsHostPort properties in wkplc.properties.

After configuring WebSphere Portal to use an external web server, you access the portal with the web server host name and port (for example, 80). For stand-alone servers or vertical cluster members, we are unable to access the portal with the WebSphere Portal host name and port (for example, 10039). We can access it if there is a corresponding virtual host definition for port 10039 in the WAS configuration.

Many of the WebSphere Portal ConfigEngine tasks rely on the WpsHostName and WpsHostPort properties from wkplc.properties. We must ensure that WebSphere Portal can be accessed with the host name and port specified by these property values. Choose one of the following methods:

  • Modify the WpsHostName and WpsHostPort property values to specify the web server host name and port.

  • Add the appropriate virtual host definition.

To access WebSphere Portal with a host name and port different from the web server, add the required virtual host definition with the WAS console. In a clustered environment, use the dmgr console to complete these steps.

  1. Log on to the WAS console.

  2. Go to Environment > Virtual Hosts.

  3. Select the default_host entry or the entry for the virtual host being used to access the WebSphere Portal application.

  4. Select Host Aliases, and verify whether there is a host name and port entry corresponding to the values used to access WebSphere Portal. If the entry does not exist, select New, and enter the information for the host name and port to use. The following information is the host alias examples:

    • *:10039

  5. Save the changes.

  6. Regenerate the web server plug-in.

  7. For a remote web server, copy the updated plugin-cfg.xml file to the web server in the web server home directory.

  8. If we are running a system under stress and are expecting requests to take longer than the ServerIOTimeout default value, increase this value to avoid sending requests twice.

  9. Recycle the web server, and the portal.

  10. In a clustered environment, resynchronize the nodes and restart the cluster.


Parent Web servers