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

Configuring a Web server for a non-default profile

This topic describes installing a Web server plug-in and configuring an application server that is not the default profile.

Before you begin

If you intend to create a Web server definition for an application server that is not the default profile, you must force the Plug-ins installation wizard to configure a profile that is not the default profile.

This procedure assumes that you have installed the Web server on one machine and the WebSphere Application Server product on a separate machine. This procedure also works when the Web server and the application server profile are on the same machine. In such a case, select the Remote installation type when installing the plug-ins so that the Plug-ins installation wizard creates the configuration script for the application server.

Why and when to perform this task

This procedure describes how to create a Web server definition for an application server that is not the default profile. This procedure describes selecting a remote installation scenario and issuing a command for the configuration script that points the command to a profile that you select.

The ordinary behavior of the configuration script is to work on the default profile on the machine where the script runs. This procedure describes how to redirect the script to configure a profile that is not the default.

Steps for this task

  1. Type a value for the location of the plugin-cfg.xml file.

    For a federated node, the deployment manager creates the file in the app_server_root/profiles/Dmgr01/config/cells/ cell_name /nodes/ app_server_node_name /servers/ web_server_name /plugin-cfg.xml file path.

    For a stand-alone application server node, the application server creates the file in the profile_root /config/cells/ cell_name /nodes/ web_server_name_node/servers/ web_server_name /plugin-cfg.xml file path.

    Specify the location in the field so that the Web server can access the file when the Web server and the application server are on the same machine. Accept the default value if the Web server and the application server are on separate machines.

    The location of the plugin-cfg.xml file is used in the Web server configuration file. If you cannot enter the location correctly at this point, you can edit the Web server configuration file manually to correct the location so that the location points to the plugin-cfg.xml file in the non-default application server profile. On a remote installation, the default location is within the plug-ins installation root directory. Propagation copies the current file from the application server machine to the Web server machine.

  2. Identify the host name or IP address of the application server machine, then click Next.
  3. Examine the summary panel. Click Next when you are finished.

    The panel notifies you that you have manual steps to perform to complete the installation and configuration. The type of Web server, the nickname of the Web server, and the location of the plugin-cfg.xml file displays on the panel.

    The Plug-ins installation wizard creates the configureweb_server_name script in the plugins_root/bin/ directory.

    The Plug-ins installation wizard also creates a default plugin-cfg.xml file in the plugins_root/config/web_server_name directory.

  4. Copy the configureweb_server_name.sh script on Linux and UNIX systems or the configureweb_server_name.bat script on Windows systems to the app_server_root/bin directory on the application server machine.

    For example, on a Linux system with an IBM HTTP Server named webserver1 in the default location, copy /opt/IBM/WebServer/Plugins/bin/configurewebserver1.sh to the /opt/IBM/WebSphere/AppServer/bin directory on the application server machine.

    If one platform is a Linux or UNIX system and the other is a Windows platform, copy the script from the crossPlatformScripts directory. For example:
  5. Start the application server.
    Use the startServer command, for example:
  6. Start the nodeagent process if the application server is federated.
    Use the startNode command, for example:
  7. Start the deployment manager if the application server is federated.
    Use the startManager command, for example:
  8. Stop the Web server if it is running.
  9. Edit the script using a flat file editor, such as Kate on SLES.
    1. Insert the -profile.name parameter into the command string within the script:
      wsadmin -profile.name profile_name_of_the_non-default_profile -f configureWebserverDefinition.jacl ...
      
    2. Save the script and close the editor.
  10. Run the script on the application server machine to create a Web server definition for the non-default profile.

    Open a command window to run the script that you copied to Machine A.

    As soon as the Web server definition is created, the application server creates a plugin-cfg.xml file for the Web server. For example, the file on a Linux system might have the following file path: profile_root/config/cells/cellname/nodes/webserver1_node/servers/webserver1/plugin-cfg.xml

  11. From the administrative console of the deployment manager, click System administration > Save Changes to Master Repository > Synchronize changes with Nodes > Save.

Result

This procedure results in the installation of the Web server plug-ins for WebSphere Application Server on a Web server machine. After modification, the resulting script creates a Web server definition for an application server that is not the default profile. The Plug-ins installation wizard also configures the Web server to support the application server.

If you can see the Snoop servlet through the Web server, you have successfully configured the Web server and the application server.

What to do next

After configuring a Web server and creating a Web server definition, you can deploy applications and serve them through the Web server. See Fast paths for WebSphere Application Server to get started deploying applications.




Related tasks
Installing Web server plug-ins
Editing Web server configuration files

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

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