Migrating Web server configurations

You can migrate an existing Web server and Web server plug-in to support the current version of the product.

About this task

This task includes:
  • Migrating your IBM HTTP Server to Version 7.0
  • Migrating the Websphere Application Server plug-in configuration
  • Migrating/creating your Web server definition

Procedure

  1. Install the IBM® HTTP Server Version 7.0 and its plug-in or a plug-in for another supported Web server.

    Refer to the Migrating from previous releases of IBM HTTP Server topic in the IBM HTTP Server for Websphere Application Server, Version 7.0 Information Center for the steps required to migrate your IBM HTTP Server. That documentation describes how to manually modify the port assignments if you install the IBM HTTP Server into a new directory because you need this new version of the IBM HTTP Server to coexist with a previous version.

    You can also modify the ports on the port assignment or coexistence panel of the WebSphere Application Server Installation wizard, or when you run the Profile Management tool. Read the topic Installing the product and additional software for more information on how to use the wizard and the Profile Management tool.

  2. Migrate plug-ins to work with WebSphere® Application Server Version 7.0.
    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.

      Read the "GenPluginCfg command" article in the information center for more information.

    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.

      Read the Installing Web server plug-ins topic for more information.

    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.

What to do next

The steps to perform next depend on whether you are migrating from Websphere Application Server 5.1.x or 6.x. Web server definitions did not exist for 5.1.x. Therefore, new definitions need to be created for Version 7.0. Web server definitions did exist for 6.x and are migrated if the definitions were created against a managed node.

Migrating from WebSphere Application Server Version 5.1.x:
In Version 6.0 and later, the plug-in configuration file has a one-to-one relationship with a Web (application-centric) server instead of a single global plug-in configuration file (topology-centric or cell-wide).
  • The plug-in configuration file (plugin-cfg.xml) generated after successful migration from Version 5.1.x to Version 7.0 is topology centric. It includes all the applications within a cell. You can manage this cell-wide plug-in configuration file from the Version 7.0 administrative console, by using the GenPluginCfg command, or by using the Plug-in Config Generator MBean. Read the "GenPluginCfg command" article in the information center for more information.

    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 7.0 administrative console. Being application-centric means that the plugin-cfg.xml file generated in the administrative console has a granularity that allows each application to be mapped to a specific Web server and application server combination.
  • 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 definition, and then use the administrative console to add the plug-in properties from your migrated plugin-cfg.xml file to this Web server definition.
    Use the Version 7.0 administrative console to complete the following steps:
    1. Create a Web server definition.

      The topics Setting up a local Web server and Setting up a remote Web server describe how to create a Web server definition.

    2. Add the plug-in properties from your migrated plugin-cfg.xml file to this Web server definition.

      The topics Communicating with Web servers and Web server plug-in configuration properties describe how to add properties to a plugin-cfg.xml file.

Migrating from WebSphere Application Server Version 6.x:

The following actions only apply if you are migrating from WebSphere Application Server Version 6.x, complete the following actions. This information does not apply if you are migrating from Version 5.1.x.

Web server definitions are migrated for managed nodes but not for unmanaged nodes. Nodes controlled by the IBM HTTP Server Administration Server are unmanaged nodes.
  • For a Web server defined on a managed node, the Web server definitions continue to work if the new Web server is installed to the same directory as the previous Web server version. If the Web server is installed to a different directory, the path to the Web server needs to be updated within the definition.
  • For a Web server defined on an unmanaged node, manually complete one of the following actions to create the Web server, and set up the application mappings:
    • While running the administration console wizard, select the Mapping ALL option to generate mappings to all applications that are installed during the Web server creation process.
    • Issue the following wsadmin command, and reply ALL to the mapping applications prompt:
      $AdminTask createWebServer -interactive 
    • Run the configureWebserverDefinition.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.




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: Feb 6, 2014 2:45:31 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-dist&topic=tins_migWebserver
File name: tins_migWebserver.html