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

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




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 12:02:36 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-zos&topic=tins_migWebserver
File name: tins_migWebserver.html