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

Plug-in considerations when you are migrating from WebSphere Application Server Version 5.1.x to Version 7.0: In WebSphere Application Server Version 7.0, the plug-in configuration file has a one-to-one relationship with a Web server.
  • The plug-in configuration file (plugin-cfg.xml) generated after successful migration from Version 5.1.x to Version 7.0 is topology centric—that is, it includes all of 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.

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

      Read the "Setting up a local Web server" article or the "Setting up a remote Web server" article in the information center for more information.

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

      Read the "Communicating with Web servers" and "Web server plug-in configuration properties" articles in the information center for more information.

Migrating from WebSphere Application Server Version 6.x: This information is only applicable if you migrated from WebSphere® Application Server Version 6.x; it is not applicable if you migrated from Version 5.1.x.
  • Only Web servers defined on managed nodes are migrated to WebSphere Application Server Version 7.0.
  • If you are migrating a Web server and plug-ins from WebSphere Application Server Version 6.x to Version 7.0 and the Web server is defined on an unmanaged node, you must manually create the Web server and application mapping.
    Complete one of the following actions to manually create the Web server definition:
    • Use the administration console wizard.

      When running the wizard, select the Mapping ALL option to generate mappings to all applications that are installed during the Web server creation process.

    • 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.




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:48:53 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-zos&topic=tins_migWebserver
File name: tins_migWebserver.html