WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results

Configuring multiple Web servers for different profiles

This topic describes installing multiple Web server plug-ins and configuring them for the Application Server in profiles that you specify.

Before you begin

When multiple profiles exist, the plug-ins installer configures only the default profile. You need the configureweb_server_name script to configure a non-default profile. See Plug-ins configuration for a description of the flow of logic that determines how the installer selects the profile to configure.

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.

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.

This procedure assumes that you have installed the Web server and the WebSphere Application Server on the same machine, but you must 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.

About this task

This procedure describes how to create multiple Web server definitions 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.

Procedure

  1. Log on to the operating system.
    [AIX] [HP-UX] [Linux] [Solaris] In addition, select a umask that would allow the owner to read/write to the files, and allow others to access them according to the prevailing system policy. For root, a umask of 022 is recommended. For non-root users a umask of 002 or 022 could be used, depending on whether or not the users share the group. To verify the umask setting, issue the following command:
    umask
    To set the umask setting to 022, issue the following command:
    umask 022
    [Windows] When installing on a Windows system, a Windows service is automatically created to autostart the application server if your installer user account has the following advanced user rights:
    • Act as part of the operating system
    • Log on as a service
    For example, on some Windows systems, click Administrative Tools > Local Security Policy > User Rights Assignments to set the advanced options. See your Windows documentation for more information.

    [Windows] If you plan to run the application server as a Windows service, do not install from a user ID that contains spaces. A user ID with spaces cannot be validated. Such a user ID is not allowed to continue the installation. To work around this problem, install with a user ID that does not contain spaces.

  2. Launch the Plug-ins installation wizard on the machine with the Web server.

    Select the Plug-ins installation wizard from the launchpad or change directories to the plugin directory on the product disc or in the downloaded installation image and issue the install command.

  3. Clear the check box for the roadmap or select the check box to view the roadmap, then click Next.

    If you are unsure of which installation scenario to follow, display the roadmap instead. Print and keep the roadmap as a handy overview of the installation steps.

    Press Ctrl-P to print the roadmap if the Web browser navigation controls and the menu bar are not present on the browser window that displays the Plug-ins roadmap. Press Ctrl-W to close the browser window if the navigation controls and the menu bar do not display. Or close the browser window with the window control in the title bar.

  4. Read the license agreement and accept the agreement it if you agree to its terms. Click Next when you are finished.
  5. 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.

    Look for the appropriate log file for information about missing prerequisites. If you stop the installation, see the temporaryPluginInstallLog.txt file in the temporary directory of the user who installed the plug-ins. For example, the /tmp/temporaryPluginInstallLog.txt file might exist if the root user installed the plug-ins on an operating system such as AIX or Linux.

    See Troubleshooting installation for more information about log files.

  6. Configure the first Web server. For example, call this Web server webserver1.
    1. Select the type of Web server that you are configuring and click Next.

      The Plug-ins installation wizard panel prompts you to identify the Web servers to configure. Actually you can select only one Web server each time you run the Plug-ins installation wizard.

      Stop any Web server while you are configuring it. A step later in the procedure directs you to start the Web server as you begin the snoop servlet test.

      If you select the Web server identification option labeled None, the Web server installs the binary plug-ins but does not configure the Web server.

    2. Select Application Server machine (local) and click Next.
    1. Accept the default location for the installation root directory for the plug-ins. Click Next.

      You can type another new directory or click Browse to select an empty directory. The fully qualified path identifies the plug-ins installation root directory.

      The default location is shown in Directory conventions.

      Restriction: The installation directory cannot contain any unsupported characters. See "Object names: what the name string cannot contain" for more information.

      A possibility exists that the Web server might run on a platform that WebSphere Application Server does not support.

    2. Click Browse to select the configuration file for your Web server, verify that the Web server port is correct, and then click Next when you are finished.

      Select the file and not just the directory of the file. Some Web servers have two configuration files and require you to browse for each file.

      The following list shows configuration files for supported Web servers:
      Apache HTTP Server
      apache_root/config/httpd.conf
      Domino Web Server
      names.nsf and Notes.jar

      The wizard prompts for the notes.jar file. The actual name is Notes.jar.

      The Plug-ins installation wizard verifies that the files exist but the wizard does not validate either file.

      IBM HTTP Server
      IHS_root/conf/httpd.conf
      Microsoft Internet Information Services (IIS)
      The Plug-ins installation wizard can determine the correct files to edit.
      Sun ONE Web Server 6.0 or Sun Java System Web Server, Version 6.1
      obj.conf and magnus.conf

      The wizard displays a naming panel for the nickname of the Web server definition.

    3. Specify a nickname for the Web server. Click Next when you are finished.

      The wizard uses the value to name configuration folders in the plug-ins installation root directory. The wizard also uses the name in the configuration script for the application server to name the Web server definition.

      If the application server profile already has a Web server definition, delete the Web server definition before continuing. Use the following commands to delete the Web server definition:
      $AdminTask deleteServer { -serverName webserver1 -nodeName webserver1_node }
      $AdminTask removeUnmanagedNode { -nodeName webserver1_node }
      $AdminConfig save
      
      In these commands, webserver1 is the Web server name.
    4. 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.

    5. Identify the host name or IP address of the application server machine, then click Next.
    6. 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.

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

      The panel specifies the plug-ins installation root directory, the Web server plug-ins feature, and the disk size of the code that installs when you click Next.

    8. After the wizard installs the code and creates the uninstaller program, examine the post-installation summary panel. Click Next when you are finished to display the Plug-ins installation roadmap.

      The Plug-ins installation wizard installs the binary plug-in module. On a Linux system, for example, the installation creates the plugins_root directory. The plugins_root/config/Web_server_name directory contains the plugin-cfg.xml file.

      The wizard displays the name and location of the configuration script and the plugin-cfg.xml file. The wizard also displays the type of Web server that is configured and the nickname of the Web server.

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

    9. Close the road map and click Finish to exit the wizard.

      Log files from the installation are in the plugins_root/logs/install directory.

  7. Repeat the steps above to create a second Web server. You can call this Web server webserver2.
    Avoid trouble: Ensure that you select a different configuration file, httpd.conf, when you are prompted by the installation.gotcha
    For webserver2, the installation process will:
    • Create webserver2 and the plugin-cfg.xml file in the plugins_root/config/webserver2 directory.
    • Create the configuration script, configurewebserver2, in the plugins_root/bin directory.
  8. Prepare the configuration script for webserver1.
    1. Copy the configurewebserver1 configuration script to the app_server_root/profiles/Deployment_manager directory. The script name should be similar to:
      • [AIX] [HP-UX] [Linux] [Solaris] [z/OS] configurewebserver1.sh
      • [i5/OS] configurewebserver1
      • [Windows] configurewebserver1.bat
    2. Modify the script to reference the profile for the deployment manager. This forces the wsadmin process to connect to the deployment manager instead of the default profile. For example:
      wsadmin.bat -profileName Deployment_manager -user User_ID -password my_Password -f 
         "%WAS_HOME%\bin\configureWebserverDefinition.jacl" webserver1 IHS.. 
  9. Prepare the configuration script for webserver2.
    1. Copy the configurewebserver2 configuration script to the app_server_root/profiles/Deployment_manager directory. The script name should be similar to:
      • [AIX] [HP-UX] [Linux] [Solaris] [z/OS] configurewebserver2.sh
      • [i5/OS] configurewebserver2
      • [Windows] configurewebserver2.bat
    2. Modify the script to reference the profile that you will use for the base profile. This forces the wsadmin process to connect to this profile rather than the default profile. For example:
      wsadmin.bat -profileName profile_name -user User_ID -password my_Password -f 
         "%WAS_HOME%\bin\configureWebserverDefinition.jacl" webserver2 IHS.. 
  10. Start the application server.
    Use the startServer command to start the application server, for example:
  11. Start the nodeagent process if the application server is federated.
    Use the startNode command, for example:
  12. Start the deployment manager if the application server is federated.
    Use the startManager command, for example:
  13. Stop the Web server if it is running.
  14. Run the configurewebserver1 and configurewebserver2 configuration scripts on the application server machine to create the Web server definitions.

    When the Web server definition is created, the application server creates the 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

  15. From the administrative console of the deployment manager, click System administration > Save Changes to Master Repository > Synchronize changes with Nodes > Save.
  16. [AIX] [HP-UX] [Linux] [Solaris] Domino Web server only: Set the WAS_PLUGIN_CONFIG_FILE environment variable.

    On platforms such as AIX or Linux, sourcing a script to the parent shell allows child processes to inherit the exported variables. On Windows systems, run the script as you would run any other command. Sourcing is automatic on Windows systems.

    1. Open a command window.
    2. Change directories to the plug-ins installation root directory.
    3. Issue the appropriate command for the plugins_root/bin/setupPluginCfg.sh script:
      • [AIX] [HP-UX] [Solaris] . plugins_root/bin/setupPluginCfg.sh (Notice the space between the period and the installation root directory.)
      • [Linux] source plugins_root/bin/setupPluginCfg.sh

    The script is also in the lotus_root/notesdata directory on operating systems such as AIX or Linux.

    Issue the appropriate command for the script before starting the Domino Web Server.

  17. Start the Snoop servlet to verify the ability of the Web server to retrieve an application from the Application Server.

    Test your environment by starting your Application Server, your Web server, and using the snoop servlet with an IP address.

    1. Start the Application Server. In a Network Deployment environment, the Snoop servlet is available in the cell only if you included the DefaultApplication when adding the Application Server to the cell. The -includeapps option for the addNode command migrates the DefaultApplication to the cell. If the application is not present, skip this step.
      Change directories to the profile_root/bin directory and run the startServer command:
      • [AIX] [HP-UX] [Linux] [Solaris] ./startServer.sh server1
      • [Windows] startServer server1
    2. Start the IBM HTTP Server or the Web server that you are using.

      Use a command window to change the directory to the IBM HTTP Server installed image, or to the installed image of your Web server. Issue the appropriate command to start the Web server, such as these commands for IBM HTTP Server:

      To start the IBM HTTP Server from the command line:

      Access the apache and apachectl commands in the IBMHttpServer/bin directory.
      • [AIX] [HP-UX] [Linux] [Solaris] ./apachectl start
      • [Windows] apache
    3. Point your browser to http://localhost:9080/snoop to test the internal HTTP transport provided by the Application Server. Point your browser to http://Host_name_of_Web_server_machine/snoop to test the Web server plug-in.

      The HTTP Transport port is 9080 by default and must be unique for every profile. The port is associated with a virtual host named default_host, which is configured to host the installed DefaultApplication and any installed Samples. The snoop servlet is part of the DefaultApplication. Change the port to match your actual HTTP Transport port.

    4. Verify that snoop is running.

      Either Web address should display the Snoop Servlet - Request/Client Information page.

    5. Remote IBM HTTP Server only:

      Verify that the automatic propagation function can work on a remote IBM HTTP Server by using the following steps. This procedure is not necessary for local Web servers.

      1. Create a user=adminUser, password=adminPassword in the IHS_root /conf/admin.passwd file. For example: c:\ws\ihs60\bin\htpasswd -cb c:\ws\ihs60\conf\admin.passwd adminUser adminPassword
      2. Use the administrative console of the deployment manager or the Application Server to enter the User ID and password information that you created for the administrative user of IBM HTTP Server. Go to Servers > Web server > Web_server_definition > Remote Web server administration. Set the following values: admin Port=8008, User Id=adminUser, Password=adminPassword.
      3. Set the correct read/write permissions for the httpd.conf file and the plugin-cfg.xml file. See the IHS_root /logs/admin_error.log file for more information.
      Automatic propagation of the plug-in configuration file requires the IBM HTTP administrative server to be up and running. If you are managing an IBM HTTP Server using the WebSphere Application Server administrative console, the following error might display:
      "Could not connect to IHS Administration server error"
      Perform the following procedure to correct the error:
      1. Verify that the IBM HTTP Server administration server is running.
      2. Verify that the Web server host name and the port that is defined in the WebSphere Application Server administrative console matches the IBM HTTP Server administration host name and port.
      3. Verify that the fire wall is not preventing you from accessing the IBM HTTP Server administration server from the WebSphere Application Server administrative console.
      4. Verify that the user ID and password that is specified in the WebSphere Application Server administrative console under remote managed, is created in the admin.passwd file, using the htpasswd command.
      5. If you are trying to connect securely, verify that you export the IBM HTTP Server administration server keydb personal certificate into the WebSphere Application Server key database as a signer certificate. This key database is specified by the com.ibm.ssl.trustStore directive in the sas.client.props file in the profile where your administrative console is running. This consideration is primarily for self-signed certificates.
      6. If you still have problems, check the IBM HTTP Server admin_error.log file and the WebSphere Application Server logs (trace.log file) to determine the cause of the problem.

Results

This procedure results in the installation of multiple Web server plug-ins for WebSphere Application Server. After modification, the resulting configuration scripts create Web server definitions for an application server for the profiles that you specify. 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.

The installation of the binary plug-in modules results in the creation of the Plugins directory and several subdirectories. The following directories are among those created on a Linux system, for example:
  • plugins_root/uninstall contains the uninstaller program
  • plugins_root/bin contains the binary plug-ins for all supported Web servers
  • plugins_root/logs contains log files
  • plugins_root/properties contains version information
  • plugins_root/roadmap contains the roadmap for the Plug-ins installation wizard

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.




In this information ...


IBM Redbooks, demos, education, and more


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

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/tins_webplugins_multiple.html