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

Configuring a Web server and a deployment manager profile on the same machine

This procedure describes installing a Web server and its plug-in on a machine where the default profile is a deployment manager.

Before you begin

This procedure configures the deployment manager profile that is the default profile on the machine. A managed node must exist to define a Web server definition, which is always on a managed node. If the deployment manager is the default profile, the Plug-ins installation wizard looks for a managed custom node in the deployment manager configuration. If the deployment manager does not have a managed custom node, the Plug-ins installation wizard looks for a managed application server node. If the deployment manager does not have a managed node, then the Plug-ins installation wizard classifies the installation as a remote installation.


Local distributed installation - dmgr

Start the deployment manager and the node agent for the managed node. The deployment manager and the node must be running to successfully change its configuration.

Why and when to perform this task

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

Steps for this task

  1. Install the WebSphere Application Server Network Deployment product.

    See Installing the product and additional software.

  2. Create a deployment manager profile as the first profile on the machine. See Creating a deployment manager profile.
  3. Install the IBM HTTP Server or another supported Web server.

    See Installing IBM HTTP Server or the product documentation for your Web server.

  4. Select Application Server machine (local) and click Next.
  5. Click Browse on the Application Server installation location panel to browse for the location of the deployment manager, if necessary. Click Next when the installation root directory is correct.

    The fully qualified path identifies the installation root directory for the Network Deployment product core files.

  6. Specify a nickname for the Web server and click Next.

    The wizard uses the value to name configuration folders in the plug-ins installation root directory. The wizard also uses the name within the deployment manager as the name of the Web server definition.

  7. Accept the location for the plugin-cfg.xml file and click Next.

    See Plug-ins configuration for a description of the logic that determines what path is configured by default. The wizard determines the characteristics of the deployment manager to determine the best path for the file.

    When the deployment manager is the default profile, the path is:
    plugins_root/config/
       web_server_name/plugin-cfg.xml

    Accept the default value.

    Important: If there is a managed custom node on the deployment manager machine, the Plug-ins installation wizard uses the following file path:
    profile_root
       /config/cells/cell_name/nodes/
       node_name_of_custom_profile/servers/
       web_server_name/plugin-cfg.xml
    In this case, accept the path and resume the procedure at this point in Configuring a Web server and a custom profile on the same machine.
  8. 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.

  9. 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 deployment manager.

    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.

  10. Complete the installation by creating the Web server definition.

    You must create an application server profile or a custom profile and federate the node before you can use the administrative console of the deployment manager to create a Web server definition. The same is true for running the configuration script that the Plug-ins installation wizard created. You must assign the Web server to a managed node when you create it.

    The managed node must exist before running the Plug-ins installation wizard. Otherwise, the installation is considered a remote installation.

    If you install the plug-in, save the script to run after you create a managed node. Otherwise an error occurs. Before starting the Web server, wait for these actions to occur:
    • The script runs successfully.
    • The script creates the Web server definition on the managed node.
    • Node synchronization occurs.

    Adding the node starts the nodeagent process. If the node agent is not running for some reason, start the node.

    See startNode command for more information.

    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.
    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

      If the node has only a deployment manager profile, then the plug-ins installer reverts to a remote plug-in configuration. You must manually copy the plugins_root/ bin/ configureweb_server_name.sh script or the plugins_root\ bin\ configureweb_server_name.bat script to the app_server_root/bin directory of the deployment manager to run the 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.

Result

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

What to do next

After installing the binary plug-in for the local Web server, you must create a managed node before you can successfully run the configuration script and use the Web server.

See Plug-ins configuration for an overview of the installation procedure.

See Web server configuration for more 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

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_single.html

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