Setting up a local Web server

This topic describes how to install the Web server and the Web server plug-in on the machine where you installed WebSphere Application Server.

Before you begin

When creating a Web server definition using the WebSphere Application Server administrative console, by default, no applications are mapped for the Web server. To map applications, select your application in the WebSphere Application Server administrative console and map the application to an application server and Web server of your choice.

If the Web server that you are setting up is an IBM HTTP Server, and you plan to manage that Web server through a node agent that is running as a non-root user, you must make sure that you adhere to the following requirements:
  • The user ID that you designate as the user ID that owns the IBM HTTP Server directories and files, is the same user ID under which the non-root node agent is running. You cannot run an IBM HTTP Server as a root user if the node agent that is managing that IBM HTTP Server is running as non-root node agent because a node agent process that is running as a non-root user cannot spawn off an IBM HTTP Server that is running as a root user.
  • The value you specify for the listener port value must be greater than 1024. An IBM HTTP Server that is running under a non-root user ID does not start if the port number for its listener port is 1024 or less.
You can ensure that the non-root node agent and the IBM HTTP Server are using the same user ID if you specify the user ID that you used to install the product as the user ID for the IBM HTTP Server when you install the IBM HTTP Server. However, if, you decide to run the node agent as a non-root user after you install the IBM HTTP Server, and Web server plug-in, you can take the following actions to enable both the node agent and the IBM HTTP Server to run as non-root users:
  1. Change the user ID for WebSphere Application Server to a non-root user ID.
  2. Configure the run-as setting for the .
  3. Use the administrative console to create a new IBM HTTP Web server, unless an already defined IBM HTTP Server has the required properties.
  4. Change the ownership of the IBM HTTP Server directory and files to the non-root user ID under which the non-root node agent is running.

About this task

You can define a locally-installed Web server on an unmanaged or managed node. If the Web server is defined on an unmanaged node, the administrative functions are handled through the IBM HTTP Server administration server. If the Web server is defined on a managed node, the administrative functions of the Web server are handled through the WebSphere Application Server node agent, which is beneficial.
[AIX HP-UX Linux Solaris Windows] Important: Web servers that are not provided with the WebSphere Application Server product do not provide an administration server. Web servers that do not provide an administration server must reside on a managed node to facilitate plug-in administration functions and generation and propagation of the plugin-cfg.xml file.
[z/OS] Important: IBM HTTP Servers that run on z/OS do not provide the administration server. Web servers that do not provide the administration server must reside on a managed node to facilitate plug-in administration functions and generation and propagation of the plugin-cfg.xml file.

The following steps create a Web server definition in the default profile.

Procedure

  1. Install your WebSphere Application Server product.
  2. Install IBM HTTP Server or another supported Web server.
  3. [AIX HP-UX Linux Solaris Windows] [z/OS] Install the binary plug-in module using the Plug-ins installation wizard.

    The Web server definition is automatically created and configured during the installation of the plug-ins.

  4. Complete the setup by creating the Web server definition using the WebSphere Application Server administrative console, or run the plug-in configuration script. The creation of this object is exclusive of the Web server installation.
    Select one of the following options:
    • Using the administrative console.

      Create a Web server definition on an existing application server or unmanaged node using the wizard:

      1. Click Servers > Web servers > New and use the Create new Web server entry wizard to create the Web server definition.
      2. Select the appropriate node.
      3. Select a template. Select a system template or a user-defined template for the Web server you want to create.
      4. Enter the Web server properties:
        • Type: The Web server vendor type
        • Port: The existing Web server port (default: 80)
        • Installation path: The Web server installation path. This field is required for IBM HTTP Server only.
        • Service name (Windows operating systems): The Windows operating system service name of the Web server.

          The default is IBMHTTPServer6.0.

        • Use secure protocol: Use the HTTPS protocol to communicate with the Web server. The default is HTTP.
        • Plug-in installation location: The directory path in which the plug-in is installed.
      5. Confirm the creation of the new Web server and click Finish.
    • Running the plug-in configuration script.

      If you install the plug-in, save the plug-in configuration script to run after you create a managed node, otherwise an error occurs. Wait until the script runs successfully and creates the Web server definition on the managed node and node synchronization occurs before starting the Web server.

      Adding the node starts the node agent process. If the node agent is not running, start the node.
      Tip: If you want the Web server to handle requests for an application for multiple managed nodes, install the application on each managed node and on the Web server definition. The script already contains all of the information that you must gather when using the administrative console option.

      [AIX HP-UX Linux Solaris Windows] See startNode command for more information.

What to do next

You can configure non-IBM HTTP Server Web servers as a remote Web server on unmanaged nodes, or as a local Web server on managed nodes. For a non-IBM HTTP Server Web server on a managed node, the following functions are supported:
The following functions are not supported on a managed node for a non-IBM Web server.
  • Starting and stopping the Web server.
  • Viewing and editing the configuration file.
  • Viewing the Web server logs.
For a non-IBM HTTP Server Web Server on an unmanaged node, you can generate plug-in configuration, based on WebSphere Application Server repository changes. The following functions are not supported on an unmanaged node for a non-IBM HTTP Server Web server:
  • Starting and stopping the Web server.
  • Viewing and editing the configuration file.
  • Viewing the Web server logs.
  • Propagation of the Web server plugin-cfg.xml file.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 11:08:29 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-mp&topic=tihs_localsetup
File name: tihs_localsetup.html