WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: Not specified

Setting up a remote Web server

This section describes how to create a Web server definition in the administrative console when the Web server and the Web server plug-in for WebSphere Application Server are on one machine and the application server is on another.

Why and when to perform this task

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

Steps for this task

  1. Install your WebSphere Application Server product. See Installing the product and additional software.
  2. Install IBM HTTP Server or another supported Web server. See Installing IBM HTTP Server.
  3. Install the binary plug-in module using the Plug-ins installation wizard. See Installing Web server plug-ins. 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. You can use the WebSphere Application Server administrative console or run the Plug-in configuration script:
    • Using the administrative console:
      1. Click System Administration > Nodes > Add Node to create an unmanaged node in which to define a Web server in the topology. Refer to Managing nodes.
      2. Click Servers > Web servers > New to launch the Create new Web server entry wizard. You will create the new Web server definition using this wizard. The wizard values are as follows:
        1. Select appropriate node
        2. Enter Web server properties:
          • Type: The Web server vendor type.
          • Port: The existing Web server port. The default is 80.
          • Installation Path: The Web server installation path. This field is required field for IBM HTTP Server only.
          • WINDOWS Service Name: 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 where the plug-in is installed.
        If you create the Web server on a remote/unmanaged node, you will also be prompted for the remote Web server properties. The properties for the IBM HTTP Server administration server follow:
        • Port: The administration server port. The default is 8008.
        • User ID: The User ID created using the htpasswd script.
        • Password: The password that corresponds to the user ID created with the htpasswd script.
        • Use secure protocol: Use the HTTPS protocol to communicate with the administration server. The default is HTTP.
      3. Select a template. Select a system template or a user-defined template for the Web server you want to create.
      4. Confirmation of Web server creation
  5. Run the setupadm script on Linux and UNIX platforms. You can find the setupadm script in the IHS_install_root>/bin directory. The administration server requires read and write access to configuration files and authentication files to perform Web server configuration data administration. The administration server has to execute adminctl restart as root to perform successful restarts of IBM HTTP Server. In addition to the Web server files, you must manually change the permissions to the targeted plug-in configuration files.
    The setupadm script prompts you for the following input:
    • User ID - The user ID that you use to log on to the administration server. The script creates this user ID.
    • Group name - The administration server accesses the configuration files and authentication files through group file permissions. The script creates the specified group through this script.
    • Directory - The directory where you can find configuration files and authentication files.
    • File name - The following file groups and file permissions change:
      • Single file name
      • File name with wildcard
      • All (default) - All of the files in the specific directory
    • Processing - The setupadm script changes the group and file permissions of the configuration files and authentication files.
  6. Run the htpasswd script on Linux, UNIX and Windows platforms. The administration server is installed with authentication enabled and a blank admin.passwd password file . The administration server will not accept a connection without a valid user ID and password. This is done to protect the IBM HTTP Server configuration file from unauthorized access.
    Launch the htpasswd utility that is shipped with the administration server. This utility creates and updates the files used to store user names and password for basic authentication. Locate htpasswd in the bin directory.
    • On Windows operating systems: htpasswd -cm <install_dir>\conf\admin.passwd [login name]
    • On Linux and UNIX platforms: ./htpasswd -cm <install_dir>/conf/admin.passwd [login name]
    where <install_dir> is the IBM HTTP Server installation directory and [login name] is the user ID that you use to log into the administration server.
Task topic    

Terms of Use | Feedback

Last updated: Mar 17, 2005 4:28:29 AM CST
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tihs_remotesetup.html

© Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)