Migrating web server configurations

You can migrate a web server so that it supports the latest version of WebSphere® Application Server.

Before you begin

Supported configurations Supported configurations:

This topic is about configuration migration, such as migrating deployment managers and federated nodes in a network deployment environment. The Application Migration Toolkit for WebSphere Application Server provides support for migrating applications from previous versions of WebSphere Application Server to the latest product version. For information about migrating applications, read more about the Application Migration Toolkit.

sptcfg

Procedure

  1. Configure an HTTP server instance.

    Read the "Configuring an HTTP server instance" article in the information center for more information.

    There are two options from which to choose:
    • Create a new HTTP server instance to be used by the WebSphere Application Server Version 8.0 profile.

      This method allows WebSphere Application Server Version 6.x, 7.x, and Version 8.0 profiles to continue operating correctly.

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

      This method changes the HTTP instance configuration to work with the WebSphere Application Server Version 8.0 profile and makes the WebSphere Application Server Version 6.x or 7.x profile no longer usable.

  2. Configure the virtual host for the WebSphere Application Server Version 8.0 profile.

    Read the "Configuring virtual hosts" article in the information center for more information.

    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.

  3. Configure communication with web servers.

    Read the "Communicating with web servers" article in the information center for more information.

    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 8.0 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 8.0 profile, read the section on J2EE security in Configuration mapping during product-configuration migration.

What to do next

Migrating from WebSphere Application Server Version 6.x or 7.x:
  • Only web servers defined on managed nodes are migrated to WebSphere Application Server Version 8.0.
  • If you are migrating a web server and plug-ins from WebSphere Application Server Version 6.x or 7.x to Version 8.0 and the web server is defined on an unmanaged node, the web server creation and application mapping must be done manually.
    To create the web server definition manually, perform one of the following actions:
    • Use the administration console wizard.

      To generate mapping to all applications that are installed at web server creation, use the mapping ALL option in the wizard.

    • Use the wsadmin command.
      $AdminTask createWebServer -interactive 
      and reply ALL to the mapping applications prompt.
    • Use the configureWebserverDefintion.jacl script.

      This script maps all installed applications to the web server. The 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 stores on the web server system. However, the script does not update other properties related to the web server if the web server definition already exists.

    • The Web server might have migrated with the application server. After migrating, Verify that your web server is functioning correctly. If not, delete the web server definition and follow the instructions in this topic to redefine it.



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 of Use | Feedback

Last updatedLast updated: Sep 20, 2011 1:06:20 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-express-iseries&topic=tins_migWebserver
File name: tins_migWebserver.html