If the WebSphere Application Server Version 3.x plug-in for your web server
uses Open Servlet Engine (OSE) transport,
you must switch to HTTP transport
when migrating to WebSphere Application Server Version 4.0.
There are two ways to migrate from OSE transport
to HTTP transport.
The following instructions are specific to the Web server being supported and
assume that you can successfully migrate existing Web applications:
All-at-once plug-in migration is the easier
of the two methods.
Make sure that the Web server installation
is at the supported level.
If you are unsure what level of
Web server product is supported, see
the Related information.
Make sure that
you have the correct plug-ins installed on the Web server machine.
If the Web server and application server are installed on the same machine
and you selected the appropriate Web server during application server installation,
further updates are probably not necessary.
Otherwise, run the application server installation program
on the Web server machine and
select Custom installation.
Then select only the Web server plug-ins for installation.
This installs the plug-ins needed to run and
makes the necessary configuration changes for the supported Web servers.
Migrate the machines from Version 3.x to Version 4.0.
Regenerate the plug-in configuration file.
If the Web server and application server are running on the same machine,
further changes to the plug-in configuration file are probably not necessary.
Otherwise,
make sure that the hostname attribute for the transports
is set to the host name or IP address on which the application server is running.
Move the plugin-cfg.xml file to the correct location
in the Web server installation.
When migrating one machine at a time
It is possible to run the Version 3.5.x OSE plug-in and
the Version 4.0 HTTP plug-in in the same Web server installation.
This enables you to keep a cluster of Version 3.5.x machines and
a cluster of Version 4.0 machines as you
migrate machines one at a time from Version 3.5.x to Version 4.0.
The instructions for incremental migration vary by
Web server product and by platform.
In all cases, however, the URI
for a machine must be unique in the routing rules for the plug-in.
For example, you cannot have /servlet/* defined in both the OSE properties file and
the HTTP configuration file.
If there is duplication, operating behavior will be erratic.
On Windows, make sure that the directory that contains
the plugin_common.dll file has been added to the system path.
(Otherwise, the Web server plug-ins will not load.)
It might be necessary to reboot the computer
after you have updated this environment variable.
Plug-in migration has been tested with the following
Web server products:
Move the appropriate files
from the bin directory of a Version 4.0 application server installation.
On Windows platforms, move mod_ibm_app_server_http.dll and plugin_common.dll
On UNIX platforms, move mod_ibm_app_server_http.so(sl)
To the httpd.conf file, add the lines
for configuring the Version 4.0 Web server plug-in (/http/webservers.html).
Regenerate the plug-in configuration file on the application server machine
after you have the machine migrated.
Be sure the hostname attributes of the transports
are set to the host name or IP address
of the machine on which the application server is running.
Move the plug-in configuration file into the Web server installation
so that it is in the location specified by the WebSpherePluginConfig directive
in the httpd.conf file.
Restart the Web server;
you should be able to access applications that run
on both Version 3.5.x and Version 4.0 application server clusters.
As you migrate more machines over to Version 4.0,
you must regenerate the Web server plug-in configuration
after migration and
move the plug-in configuration file to the Web server installation.
You should also remove the machine from the OSE files
by either manually editing them or removing the machine
from the Version 3.5.x instances and then regenerating the OSE property files.
Migration for Sun ONE (iPlanet) Web Server
Move the appropriate files
from the bin directory of a Version 4.0 application server installation.
In Windows, move ns41_http.dll and plugin_common.dll
In Linux and UNIX, move libns41_http.so(sl)
To the obj.conf file (Version 4.1 of Sun ONE Web Server) or
to the magnus.conf file
(Version 6.0 of Sun ONE Web Server), add the lines
for configuring the Version 4.0 Web server plug-in (/http/webservers.html).
Regenerate the plug-in configuration file on the application server machine
after you have the machine migrated.
Be sure the hostname attributes of the transports
are set to the host name or IP address
of the machine on which the application server is running.
Move the plug-in configuration file into the Web server installation
so that it is in the location specified by the bootstrap.properties variable
for the Init directive in the obj.conf (V4.1) or magnus.conf (V6.0) file.
Restart the Web server;
you should be able to access applications that run
on both Version 3.5.x and Version 4.0 application server clusters.
As you migrate more machines over to Version 4.0,
you must regenerate the Web server plug-in configuration
after migration and
move the plug-in configuration file to the Web server installation.
You should also remove the machine from the OSE files
by either manually editing them or removing the machine
from the Version 3.5.x instances and then regenerating the OSE property files.
Migration for Lotus Domino
Make sure that the registry is set correctly.
If you have not previously installed the Version 4.0 application server
on the Web server machine,
add a key called 4.0
to WebSphere Application Server and
then add the Plugin Config variable to the key for the Web server plug-in to load.
The complete instructions for this can be found in the instructions
for manually configuring the Web server plug-in (/http/webservers.html).
Move the appropriate files
from the bin directory of a Version 4.0 application server installation.
In Windows, move domino5_http.dll and plugin_common.dll
In Unix, move libdomino5_http.a(so,sl)
Follow the steps for manually configuring
the Version 4.0 Web server plug-in (/http/webservers.html).
Regenerate the plug-in configuration file on the application server machine
after you have the machine migrated.
Be sure the hostname attributes of the transports
are set to the host name or IP address
of the machine on which the application server is running.
Move the plug-in configuration file into the Web server installation
so that it is in the location specified by the Plugin Config variable
that you added to the registry.
Restart the Web server;
you should be able to access applications that run
on both Version 3.5.x and Version 4.0 application server clusters.
As you migrate more machines over to Version 4.0,
you must regenerate the Web server plug-in configuration
after migration and
move the plug-in configuration file to the Web server installation.
You should also remove the machine from the OSE files
by either manually editing them or removing the machine
from the Version 3.5.x instances and then regenerating the OSE property files.
Migration for Microsoft IIS
Make sure that the registry is set correctly.
If you have not previously installed the Version 4.0 application server
on the Web server machine,
add a key called 4.0
to WebSphere Application Server and
then add the Plugin Config variable to the key for the Web server plug-in to load.
The complete instructions for this can be found in the instructions
for manually configuring the Web server plug-in (/http/webservers.html).
Move the files iisWASPlugin_http.dll and plugin_common.dll
from the bin directory of a Version 4.0 application server installation.
Follow the steps for manually configuring
the Version 4.0 Web server plug-in (/http/webservers.html).
Regenerate the plug-in configuration file on the application server machine
after you have the machine migrated.
Be sure the hostname attributes of the transports
are set to the host name or IP address
of the machine on which the application server is running.
Move the plug-in configuration file into the Web server installation
so that it is in the location specified by the Plugin Config variable
that you added to the registry.
Restart the Web server;
you should be able to access applications that run
on both Version 3.5.x and Version 4.0 application server clusters.
As you migrate more machines over to Version 4.0,
you must regenerate the Web server plug-in configuration
after migration and
move the plug-in configuration file to the Web server installation.
You should also remove the machine from the OSE files
by either manually editing them or removing the machine
from the Version 3.5.x instances and then regenerating the OSE property files.