You can migrate a Web server from supporting an earlier version of WebSphere Application Server to support the current version.
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.
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.
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\"
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.
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.
Be aware that regenerating the plug-in configuration can overwrite manual configuration changes that you might want to preserve.
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.
$AdminTask deleteServer { -serverName webserver1 -nodeName WebserverHostName-node_node } $AdminTask removeUnmanagedNode { -nodeName WebserverHostName-node_node } $AdminConfig save
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. Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof. |