Migrating Web server configurations

You can migrate a Web server from supporting an earlier version of WebSphere Application Server to support the current version.

About this task [z/OS]

Migrating from WebSphere Application Server Version 5.x: This information is only applicable if you migrated from WebSphere Application Server Version 5.x; it is not applicable if you migrated from Version 6.0.x.
  • The plug-in configuration file (plugin-cfg.xml) generated after successful migration from Version 5.x to Version 6.1 is topology centric—that is, it includes all the applications within a cell. You can manage this cell-wide plug-in configuration file from the Version 6.1 administrative console, by using the GenPluginCfg command, or by using the Plug-in Config Generator MBean.

    Be aware that regenerating the plug-in configuration can overwrite manual configuration changes that you might want to preserve.

  • The application-centric generation of the plugin-cfg.xml file is supported using the Version 6.x administrative console. Being application centric means that the plugin-cfg.xml file generated in the administration console has a granularity that allows each application to be mapped to its specific Web or application server.
  • To set up the administrative console so that you can use it to manage the Web server plug-in configuration, you must first create a default Web server configuration and then use the administrative console to add the plug-in properties from your migrated plugin-cfg.xml file to this Web server configuration.
    1. Create a default Web server configuration.
    2. Add the plug-in properties from your migrated plugin-cfg.xml file to this Web server configuration.
Migrating from WebSphere Application Server Version 6.0.x: This information is only applicable if you migrated from WebSphere Application Server Version 6.0.x; it is not applicable if you migrated from Version 5.x.
  • If you are migrating a Web server and plug-ins from WebSphere Application Server Version 6.0.x to Version 6.1, the configureWebserverDefinition.jacl script does not update all of the information related to the Web server. You must recreate the Version 6.0.x Web server definition for Version 6.1.

    The configureWebserverDefinition.jacl script updates all of the information related to the Web server plug-in such as the locations of the plug-in installation root, log file, configuration file, and key store on the Web-server machine. However, the script does not update other properties related to the Web server if the Web server definition already exists.

  • To recreate the Web server definition, perform the following actions:
    1. Delete the existing Version 6.1 Web server definition by performing one of the following actions:
      • Use the following wsadmin commands:
        $AdminTask deleteServer { -serverName webserver1 -nodeName WebserverHostName-node_node } 
        $AdminTask removeUnmanagedNode { -nodeName WebserverHostName-node_node } 
        $AdminConfig save
      • Use the administrative console to perform the following actions:
        1. From the administrative console, click Servers > Web servers.
        2. Select the Web server that you want to delete, and click Delete.
    2. Create a new Version 6.1 Web server definition using the configureweb_server_name script generated by the plug-in installer.

Procedure

  1. [AIX HP-UX Linux Solaris Windows] Install the IBM HTTP Server Version 6.x and its plug-in or a plug-in for another supported Web server.
    Install the HTTP Server and its plug-in on a different machine with the following procedure:
    1. Insert the product disk into the machine.
    2. Close the launchpad if it starts automatically.
    3. Change directories to the IHS directory on the product disk.
    4. Install the IBM HTTP Server.
      Run the appropriate installation script for your platform.
      • [AIX] [HP-UX] [Linux] [Solaris] InstallIHS.sh
      • [Windows] InstallIHS.bat
      This script installs the plug-in that you need and makes the necessary configuration changes for the supported Web server.

    IBM HTTP Server Version 6.1 can coexist with earlier versions, or you can upgrade earlier versions to Version 6.1. Upgrading relieves you from having to uninstall and reinstall the HTTP server. Install Version 6.1 into the same directory structure as the earlier version to upgrade that version. If you install the HTTP Server into a different directory, Version 6.1 coexists with the previous version. By default, the administration server and the Web Server use the same ports as the previous version, which causes a conflict. However, you can change the port assignments on the port assignment panel of the WebSphere Application Server Installation wizard or the Profile Management tool.

    • Change the port number assignments for the new installation if you install into a separate directory. You can change port numbers on the coexistence panel. You can back track through the Installation wizard and change the port settings if you have not already done so. Or, you can change the port settings after installation in the httpd.conf file in the HTTP Server directory.

    • Update the IBM HTTP Server httpd.conf configuration entries to remove entries for earlier WebSphere Application Server versions if you install into the same directory as an earlier version.

      Versions 5.x, 6.0.x, and 6.1 of WebSphere Application Server use the same HTTP transport plug-in binary module. If the Web server configuration file contains WebSphere Application Server Version 5.x or 6.0.x plug-in information, you must manually remove it. Otherwise when the HTTP Server attempts to start the second Version 6.1 plug-in binary module, there is an error. The error indicates that the module is already loaded.

      The configuration file might contain duplicate entries for accessing WebSphere Application Server samples. Remove any aliases for previous versions and retain the Version 6.1 entries:
      Version 5.x installation:
      Alias /WSsamples "c:\Program Files\WebSphere\AppServer\WSsamples"
      Alias /IBMWebAS/ "c:\Program Files\WebSphere\AppServer\web\"
      
      Version 6.0.x installation:
      Alias /WSsamples "c:\Program Files\WebSphere\AppServer\WSsamples"
      Alias /IBMWebAS/ "c:\Program Files\WebSphere\AppServer\web\"
      
      Version 6.1 installation:
      Alias /WSsamples "c:\Program Files\WebSphere\AppServer\WSsamples"
      Alias /IBMWebAS/ "c:\Program Files\WebSphere\AppServer\web\"
      
  2. [AIX HP-UX Linux Solaris Windows] Migrate plug-ins to work with WebSphere Application Server Version 6.1.
    Starting with WebSphere Application Server Version 6.0, the following are true:
    • Web servers can be represented in the administrative console.
    • The Web server plug-in configuration file (plugin-cfg.xml) is associated with every Web server definition instead of one cell-wide plug-in configuration file.
    • The settings in the generated plug-in configuration file are based on the list of applications that are deployed on the hosting Web server.

    Use the following steps to generate a Web server plug-in configuration file that is based on topology. This method was used for generated plug-in configuration files in previous releases.

    1. Use the GenPluginCfg command to generate the plug-in configuration file.
    2. Manually propagate the generated plug-in configuration file from the machine on which the WebSphere Application Server resides to the remote Web server.
    3. Use the Plug-ins installation wizard to configure the Web server. Instead of using the default plug-in configuration file location, specify the new location of the plug-in configuration file that was propagated in the previous step.

    You should migrate to the application-centric approach that uses the Plug-ins installation wizard. The Plug-ins installation wizard generates scripts that can be used to create the Web server definition for that Web server and to map all of the applications that are currently deployed to the newly created Web server definition.

  3. [iSeries] Configure an HTTP server instance.
    There are two options from which to choose:
    • Create a new HTTP server instance to be used by the WebSphere Application Server Version 6.1 profile.

      This method allows WebSphere Application Server Version 5.x or 6.0.x and Version 6.1 profiles to continue operating correctly.

    • Update the HTTP server instance configuration for the WebSphere Application Server Version 5.x or 6.0.x profile that is being migrated.

      This method changes the HTTP instance configuration to work with the WebSphere Application Server Version 6.1 profile and makes the WebSphere Application Server Version 5.x or 6.0.x profile no longer usable.

  4. [iSeries] Configure the virtual host for the WebSphere Application Server Version 6.1 profile.

    This step ensures that both the host and HTTP transport port number exist in the virtual host list.

    If you created a new HTTP server in the previous step or if you used the -portBlock parameter when performing the migration, the virtual host will not contain the correct port for communication with your HTTP server. You need to add a host alias for the port used by your HTTP server.

  5. [iSeries] Configure communication with Web servers.

    This step regenerates the plug-in configuration file, plugin-cfg.xml. It needs to be done after any configuration changes have been made.

    Additional configuration is required if Secure Sockets Layer (SSL) is enabled on a plug-in transport. In addition to copying the .kdb file to the Version 6.1 profile, you must edit the plug-in to specify the .kdb file required for the plug-in to use the transport.

    For more information on copying the .kbd files to the Version 6.1 profile, see the section on J2EE security in Configuration mapping during product-configuration migration.

What to do next [AIX HP-UX Linux Solaris Windows] [iSeries]

Migrating from WebSphere Application Server Version 5.x: This information is only applicable if you migrated from WebSphere Application Server Version 5.x; it is not applicable if you migrated from Version 6.0.x.
  • The plug-in configuration file (plugin-cfg.xml) generated after successful migration from Version 5.x to Version 6.1 is topology centric—that is, it includes all the applications within a cell. You can manage this cell-wide plug-in configuration file from the Version 6.1 administrative console, by using the GenPluginCfg command, or by using the Plug-in Config Generator MBean.

    Be aware that regenerating the plug-in configuration can overwrite manual configuration changes that you might want to preserve.

  • The application-centric generation of the plugin-cfg.xml file is supported using the Version 6.x administrative console. Being application centric means that the plugin-cfg.xml file generated in the administration console has a granularity that allows each application to be mapped to its specific Web or application server.
  • To set up the administrative console so that you can use it to manage the Web server plug-in configuration, you must first create a default Web server configuration and then use the administrative console to add the plug-in properties from your migrated plugin-cfg.xml file to this Web server configuration.
    • To create a default Web server configuration and then add the plug-in properties from your migrated plugin-cfg.xml file in a Network Deployment configuration, use the Version 6.x administrative console to perform the following tasks:
      1. [AIX HP-UX Linux Solaris Windows] Create a default Web server configuration.
      2. [iSeries] Create a default Web server configuration.
      3. Add the plug-in properties from your migrated plugin-cfg.xml file to this Web server configuration.
    • To create a default Web server configuration and then add the plug-in properties from your migrated plugin-cfg.xml file in a standalone application server configuration, perform the following tasks:
      1. [AIX HP-UX Linux Solaris Windows] Use the Version 6.x Plug-ins installation wizard to create a default Web server configuration.
      2. [iSeries] Create a default Web server configuration.
      3. Use the Version 6.x administrative console to edit the configuration and define the plug-in properties.
Migrating from WebSphere Application Server Version 6.0.x: This information is only applicable if you migrated from WebSphere Application Server Version 6.0.x; it is not applicable if you migrated from Version 5.x.
  • If you are migrating a Web server and plug-ins from WebSphere Application Server Version 6.0.x to Version 6.1, the configureWebserverDefinition.jacl script does not update all of the information related to the Web server. You must recreate the Version 6.0.x Web server definition for Version 6.1.

    The configureWebserverDefinition.jacl script updates all of the information related to the Web server plug-in such as the locations of the plug-in installation root, log file, configuration file, and key store on the Web-server machine. However, the script does not update other properties related to the Web server if the Web server definition already exists.

  • To recreate the Web server definition, perform the following actions:
    1. Delete the existing Version 6.1 Web server definition by performing one of the following actions:
      • Use the following wsadmin commands:
        $AdminTask deleteServer { -serverName webserver1 -nodeName WebserverHostName-node_node } 
        $AdminTask removeUnmanagedNode { -nodeName WebserverHostName-node_node } 
        $AdminConfig save
      • Use the administrative console to perform the following actions:
        1. From the administrative console, click Servers > Web servers.
        2. Select the Web server that you want to delete, and click Delete.
    2. Create a new Version 6.1 Web server definition using the configureweb_server_name script generated by the plug-in installer.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

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

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 2:56:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=tins_migWebserver
File name: tins_migWebserver.html