WebSphere

 

Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

 

Set up a Web server with WebSphere Portal Express

 

+

Search Tips   |   Advanced Search

 

Set up your Web server to communicate with IBM WebSphere Portal Express by installing and configuring the Web server plug-in provided on the WebSphere Portal Express Setup disc.

The instructions below do not apply if you plan to use the HTTP server that is natively provided with the i5/OS operating system.

  1. Ensure that the Web server is installed and configured.

  2. If you are using Microsoft IIS users, update the value of the UrlSegmentMaxLength key in the registry.

    Incorrectly editing the registry could severely damage your system, requiring you to reinstall your operating system. Before making changes to the registry, you should back up any critical data.

    1. Open the Registry Editor

      Start | Run regedit

    2. Locate the key...

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters

    3. Create a value named...

      UrlSegmentMaxLength

      ...with a type of DWORD and a value of 0 to indicate an unbounded length.

    4. Ensure that the plugin-cfg.loc file is located in the same directory as the iisWASPlugin_http.dll or IIS will not be able to use the dynamic link library.

    5. Exit the Registry Editor by clicking...

      File | Exit

    6. Restart Windows

  3. IBM Lotus Domino users only:

    Edit the NOTES.INI file on the Web server machine, and ensure that the HTTPEnableConnectorHeaders parameter is set as HTTPEnableConnectorHeaders=1.

  4. After the Web server is successfully installed and running, stop the Web server.

  5. Use the WAS Version 6.1 Plug-ins installation wizard (provided on the WebSphere Portal Express Setup disc) to install and configure the Web server plug-in on the machine where the Web server is located.

    The Plug-ins installation wizard installs the plug-in module, configures the Web server for communication with the application server, and creates a Web server configuration definition in the application server.

    Launch the Plug-ins installation wizard from the WebSphere Portal Express Setup disc (IL-Setup, W-Setup) as follows:

    • Linux:

      cd linux/ia32/extras/plugin
      install

    • Windows:

      cd windows/ia32/extras/plugin
      install.exe

    For additional information, refer to documentation included on the Setup disc:

      linux/ia32/extras/plugin/readme.html
      windows/ia32/extras/plugin/readme.html

    To use Lotus Domino Version 7.0 with WAS, install the Web server plug-in for Domino Server Version 6 which is a part of the Web Server plug-in for WAS Version 6.0.2 and later.

    To use HTTP Server Version 2.0.47.1 with WAS, install the Web server plug-in for HTTP Server Version 6.

    The Web server instructions provided in the WAS documentation typically act on the default profile. If the WebSphere Portal Express application server is not the default application server, follow the instructions for a non-default profile.

    If the Web server definition is not automatically created during the plug-in installation, create this definition manually by running the script...

    configureweb_server_name

    ...on the WAS system or, for a clustered environment, the deployment manager system. Because the configureweb_server_name script not only creates the Web server definitions but also changes the target mappings of all enterprise applications deployed in the cell, synchronize and restart the cluster when running script on a deployment manager system.

    Because security is enabled, update the configureweb_server_name script file before running the script, and ensure that you specify the user ID and password used for authentication in the file. The user ID you specify cannot have an imbedded blank; a user ID containing a blank causes the script to issue an invalid credentials error.

    If using a Lotus Domino server and you receive the following error...

    ws_config_parser: handleLogEnd: Failed to open log file: 'C:\IBM\WebSphere\Plugins\logs\webserver1\http_plugin.log'

    ...create the log file manually and restart the Lotus Domino server.

    See the following files for additional information:

  6. Restart the Web server.

  7. Verify that WebSphere Portal Express is operational with the new Web server configuration.

 

Web Content Management

To access content created by Web Content Management through a server that is configured to use an HTTP port other than the default internal HTTP port (for example, with a Web server), ensure that required substitution variables are set in the configuration for WAS.

  1. Log in to the administrative console for WAS.

    If you are using the Web server in a clustered environment, open the administrative console for the deployment manager machine.

  2. Select...

    Environment | WebSphere Variables

  3. Narrow the scope of the listed variables

    1. Click...

      Browse Nodes

      ...in the Scope field.

    2. Select the node containing your application server.

    3. Click Browse Servers.

    4. Select the application server for WebSphere Portal Express and click OK.

      Remember that server1 is not a cluster member, only the WebSphere Portal Express server will be a cluster member.

    5. Click Apply to update the list of variables.

  4. Update the value of the WCM_HOST variable with the fully qualified host name of the Web server.

  5. Update the value of the WCM_PORT variable with the port number used to access the Web server.

  6. Restart the WebSphere Portal Express server.

 

Parent topic:

Configuring Web servers

 

Related concepts
Web servers and WebSphere Portal Express