WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Configuring a Web server and an application server profile on the same machine

This topic describes installing a Web server plug-in that WebSphere Application Server provides to communicate with a particular brand of Web server. This procedure describes installing the Web server and its Web server plug-in for WebSphere Application Server and the application server on the same machine.

Before you begin

This procedure configures the application server profile that is the default profile on the machine. A one-to-one relationship exists between a Web server and the application server.

Application Server with optional Web server on one machine

The set of steps leading up to the next diagram show how to configure a stand-alone application server. The set of steps after the next diagram show how to configure an application server that is federated into a deployment manager cell.

Why and when to perform this task

The wizard performs three steps to properly configure a Web server for Version 6. The wizard performs the steps in the following order:
  1. The wizard installs the unique binary plug-in module for the supported Web server after collecting the following information:
    • The type of Web server
    • The location of the configuration file for the Web server that the wizard configures
    • The plug-ins installation root directory for the Web server plug-in modules that the wizard installs
    • The installation root directory of the WebSphere Application Server product, where the wizard creates a Web server definition
  2. The wizard prompts you for the location of the configuration file or files for the Web server. You must browse for and select the correct file.

    The wizard edits the configuration file or files for a Web server by creating directives that point to the location of the binary plug-in module and the plug-in configuration file.

    The name of the binary plug-in module varies per Web server type. The plug-in configuration file is always the plugin-cfg.xml file.

  3. The wizard creates a Web server definition in the configuration of the application server unless one already exists.

    You can use the administrative console to manage the Web server configuration. For example, when you install an application on the application server, you can also choose to install it on the Web server definition. If so, the updated plugin-cfg.xml file shows that the new application is available. When the Web server reads the updated plug-in configuration file, the Web server becomes aware of the new application that it can serve to Web clients.

    If you choose not to install the new application on the Web server definition, the application is not added to the plug-in configuration file. The Web server is not aware of the application and cannot serve it to Web clients.

Use the following procedure to install the Web server plug-in, configure the Web server, and create a Web server definition in the default application server profile.

Steps for this task

  1. Stop the stand-alone application server before installing the Web server plug-ins. For example, assuming that the profile name is default, use one of the following commands.
    • [AIX] /usr/ IBM/ WebSphere/ AppServer/ profiles/ default/ bin/ stopServer.sh server1
    • [Linux][UNIX] /opt/ IBM/ WebSphere/ AppServer/ profiles/ default/ bin/ stopServer.sh server1
    • [Windows] C:\ Program Files\ IBM\ WebSphere\ AppServer\ profiles\ default\ bin\ stopServer.sh server1
  2. Select Application Server machine (local) and click Next.
  3. Specify the location for the plugin-cfg.xml file and click Next.

    This is a critical selection.

    See Plug-ins configuration for a description of the logic that determines what path is configured by default. The following possibilities exist for the default location of the plug-in configuration file. The wizard determines the characteristics of the application server to determine the best path for the file:
    • An application server that has an existing Web server definition has the following path:
      plugins_root/plugin-cfg.xml/config/
         web_server_name/plugin-cfg.xml
    • A stand-alone application server that does not have a Web server definition has the following path:
      profile_root
      /config/cells/cell_name/nodes/
      web_server_name_node/servers/
      web_server_name/plugin-cfg.xml

    You can accept the default value if the application server does not have a Web server definition.

    Using an existing Web server definition

    If the application server has a Web server definition, the wizard cannot create a new Web server definition within the application server configuration. However, the wizard can reconfigure the Web server. Click Browse and select the existing plugin-cfg.xml file in the application server configuration.

    To find the plug-in configuration file in a stand-alone application server, follow this file path:
    profile_root
       /config/cells/cell_name/nodes/
       web_server_name_node/servers/
       web_server_name/plugin-cfg.xml

    If the existing web_server_name is different than the nickname that you gave the Web server in the wizard, click Back to return to the naming panel for the Web server and change the name to match the existing Web server definition name.

    If you cannot find an existing plugin-cfg.xml file after all, you must install the temporary plugin-cfg.xml file. In such a case, type the path to the plug-ins installation root directory so that the wizard can install the temporary plug-in configuration file:
    plugins_root/config/
        web_server_name/plugin-cfg.xml
  4. Click Next after verifying the characteristics of the plug-ins installation or click Back to make changes.

    Once created, a Web server definition on a stand-alone application server node cannot be removed except through scripting. (See Uninstalling the Web server plug-ins for WebSphere Application Server for the procedure.)

    You can, however, reuse the same definition for a different type of Web server. Run the Plug-ins installation wizard to configure a new Web server in that situation. The Plug-ins installation wizard configures the new Web server to use the existing plugin-cfg.xml file.

  5. Click Next on the pre-installation summary panel to begin the installation or click Back to change any characteristics of the installation. The wizard begins installing the plug-ins and configuring the Web server and the application server.

    The wizard shows an installation status panel as it installs the plug-ins.

    The wizard displays the Installation summary panel at the completion of the installation.

  6. Verify the success of the installation on the Installation summary panel and click Finish to exit the wizard.

    If a problem occurs and the installation is unsuccessful, examine the logs in the plugins_root/logs directory. Correct any problems and reinstall.

  7. Configure a Web server and a distributed application server profile on the same machine.

    The rest of these steps describe how to configure an application server that is federated into a deployment manager cell.

    The following topology is considered a local distributed topology because it involves a cell:

    Application Server with optional Web server on one machine

    This part of the procedure assumes that you have already installed the Network Deployment product on both machines. Also assumed is that you have already configured a deployment manager profile on Machine A and an application server profile on Machine B.

    If you are planning to add the application server node into a deployment manager cell but have not done so yet, start the deployment manager and federate the node before installing the plug-in. You cannot add an application server with a Web server definition into the deployment manager cell.

    A Web server definition on a federated application server is installed on the same managed node as the application server. There is one node, but with two server processes, the application server and the Web server definition.

    If you are installing the plug-ins for use with a federated application server, start the deployment manager. Verify that the node agent process on the managed node is also running. Both the deployment manager and the node agent must be running to successfully configure a managed node.

  8. Install IBM HTTP Server or another supported Web server on Machine B.

    See Installing IBM HTTP Server or refer to the product documentation for your Web server for more information.

  9. Launch the Plug-ins installation wizard on the machine with the Web server.
  10. Clear the check box for the roadmap or select the check box to view the roadmap, then click Next.
  11. Read the license agreement and accept the agreement it if you agree to its terms, then click Next.
  12. If your system does not pass the prerequisites check, stop the installation, correct any problems, and restart the installation. If your system passes the prerequisites check, click Next.
  13. Select the type of Web server that you are configuring, then click Next.
  14. Select Application Server machine (local) and click Next.
  15. Accept the default location for the installation root directory for the plug-ins, then click Next.
  16. Click Browse on the Application Server installation location panel to browse for the location of the Application Server profile, if necessary. Click Next when the installation root directory is correct.
  17. Click Browse to select the configuration file for your Web server, verify that the Web server port is correct, and then click Next.
  18. Specify a nickname for the Web server, then click Next.
  19. Specify the location for the plugin-cfg.xml file and click Next.
    This is a critical selection. A federated application server that does not have a Web server definition has the following path:
    profile_root
    /config/cells/cell_name/nodes/
    node_name_of_AppServer/servers/
       web_server_name/plugin-cfg.xml
    An application server that has an existing Web server definition has the following path:
    plugins_root/config/
       web_server_name/plugin-cfg.xml

    See Plug-ins configuration for a description of the logic that determines what path is configured by default.

  20. Click Next after verifying the characteristics of the plug-ins installation or click Back to make changes.

    You can use the administrative console of the deployment manger to delete an existing Web server or to create new ones. Federated nodes can have more than one Web server definition.

  21. Click Next on the pre-installation summary panel to begin the installation or click Back to change any characteristics of the installation.

    The wizard begins installing the plug-ins and configuring the Web server and the application server.

    The wizard shows an installation status panel as it installs the plug-ins.

    The wizard displays the Installation summary panel at the completion of the installation.

  22. Verify the success of the installation on the Installation summary panel and click Finish to exit the wizard.
  23. Complete the installation by creating the Web server definition.

    You can use the administrative console of the deployment manager to create the Web server definition on a federated node. Or, you can run the configuration script that the Plug-ins installation wizard created.

    The script already contains all of the information that you must gather when using the administrative console option.

    Select one of the following options:
    • Using the administrative console

      Click Servers > Web servers > New and use the Create new Web server entry wizard to create the Web server definition.

    • Running the configuration script
      Issue the appropriate command from a command window:

      If you have enabled security or changed the default JMX connector type, edit the script and include the appropriate parameters on the wsadmin command.

  24. From the administrative console of the deployment manager, click System administration > Save Changes to Master Repository > Synchronize changes with Nodes > Save.
  25. Source the Domino Web server script if necessary.
  26. Start the snoop servlet.

    See the snoop procedure for the stand-alone application server for the full procedure.

Result

The Plug-ins installation wizard creates a Web server definition within the application server profile unless one already exists.

The Plug-ins installation wizard configures the Web server to use the profile_root/plugin-cfg.xml file.

The application server regenerates the Web server plug-in configuration file, plugin-cfg.xml whenever an event occurs that affects the file. Such events include the addition or removal of an application, server, or virtual host. The stand-alone application server regenerates the file in the following location:
profile_root
   /config/cells/cell_name/nodes/
   web_server_name_node/servers/
   web_server_name/plugin-cfg.xml
On a federated node, the creation or removal of clusters and cluster members also causes file regeneration. The deployment manager regenerates the file for a federated application server in the following location:
profile_root
   /config/cells/cell_name/nodes/
   node_name_of_AppServer/servers/
   web_server_name/plugin-cfg.xml

What to do next

You can start a stand-alone application server and the Web server immediately after installing of the binary plug-in for the local Web server. Open the administrative console of the application server after you start the server and save the changed configuration.

After installing the binary plug-in for the local Web server, you can start a federated application server and the Web server after running the configuration script that completes the installation. Open the administrative console of the deployment manager. Wait for node synchronization to occur. Save the changed configuration that includes the new Web server definition.

See Selecting a Web server topology diagram and roadmap for an overview of the installation procedure.

See Plug-ins configuration for information about the location of the plug-in configuration file.

See Web server configuration for information about the files involved in configuring a Web server.

See Editing Web server configuration files for information about how the Plug-ins installation wizard configures supported Web servers.

See Installing Web server plug-ins for information about other installation scenarios for installing Web server plug-ins.




Related concepts
Plug-ins configuration
Web server configuration

Related tasks
Installing Web server plug-ins

Task topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_webplugins_local.html

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