109 lines
5.9 KiB
HTML
109 lines
5.9 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Step 4: Complete the migration</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h2><A NAME="migcfgafter"></A>Step 4: Complete the migration</h2>
|
||
|
|
|
||
|
|
<p>This topic describes the manual steps that you might need to perform to complete the migration process. These are steps that are not performed automatically by the WebSphere Application Server - Express migration tools.</p>
|
||
|
|
|
||
|
|
<p><strong>Change the HTTP transport after migration</strong>
|
||
|
|
<br>If the -portBlock parameter was not specified in the WASPostUpgrade script, you need to use the WebSphere Application Server - Express administrative console to adjust the ports manually after migration has completed.</p>
|
||
|
|
|
||
|
|
<OL>
|
||
|
|
<LI>Use the WebSphere Application Server - Express administrative console to change the HTTP transport port:
|
||
|
|
<oL type="a">
|
||
|
|
<li>Navigate to <strong>Servers --> Application Servers --> <em>my_server</em></strong> where <em>my_server</em> is the name of the application server that was migrated.</li>
|
||
|
|
<li>Click <strong>Web Container</strong>.</li>
|
||
|
|
<li>Click <strong>HTTP transports</strong>.</li>
|
||
|
|
<li>Click on a host.</li>
|
||
|
|
<li>Adjust the <strong>Port</strong> property by entering a port not currently in use on your iSeries server. Record both the old and new port numbers; they are needed for step 2.</li>
|
||
|
|
<li>Click <strong>OK</strong>. </li>
|
||
|
|
<li>Repeat for each host.</li>
|
||
|
|
</oL></li>
|
||
|
|
|
||
|
|
<LI>Adjust your Virtual hosts to correspond to your HTTP transport.
|
||
|
|
<oL type="a">
|
||
|
|
<li>Click <strong>Environment --> Virtual Hosts</strong>.</li>
|
||
|
|
<li>Select your virtual host.</li>
|
||
|
|
<li>Click <strong>Host Aliases</strong>.</li>
|
||
|
|
<li>Click <strong>New</strong>.</li>
|
||
|
|
<li>Select one of the ports that were changed in step 1.</li>
|
||
|
|
<li>Enter the port that this was changed to in step 1.</li>
|
||
|
|
<li>Click <strong>OK</strong>.</li>
|
||
|
|
<li>Repeat for each port that was changed in step 1.</li>
|
||
|
|
</oL></li>
|
||
|
|
|
||
|
|
<li>Click <strong>Save.</strong></li>
|
||
|
|
<LI>Regenerate your plugin configuration.
|
||
|
|
<oL type="a">
|
||
|
|
<li>Navigate to <strong>Environment --> Update Web Server Plugin</strong>. </li>
|
||
|
|
<li>Click <strong>OK</strong>.</li>
|
||
|
|
</oL></li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
|
||
|
|
<p><strong>Migrate the web server plug-in</strong>
|
||
|
|
<br>If the WebSphere Application Server Version 3.5.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 - Express.</p>
|
||
|
|
|
||
|
|
<p>The following instructions are specific to the Web server being supported and assume that you can successfully migrate existing Web applications:</p>
|
||
|
|
|
||
|
|
<p>Plug-in migration has been tested with the following Web server products:</p>
|
||
|
|
<ul>
|
||
|
|
<li>IBM HTTP Server (original) for iSeries (V4R5)</li>
|
||
|
|
<li>IBM HTTP Server (powered by Apache) for iSeries (V5R1)</li>
|
||
|
|
<li>Lotus Domino HTTP Server</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>Use the following steps to migrate the plug-in configuration:</p>
|
||
|
|
|
||
|
|
<ol>
|
||
|
|
<li><strong>Configure an HTTP server instance</strong>
|
||
|
|
<br>There are two options to chose from:
|
||
|
|
<ul>
|
||
|
|
<li>Create a new HTTP server instance to be used by the WebSphere Application Server - Express instance. This method allows both Websphere Version 3.5.x and WebSphere Application Server - Express instances to continue operating correctly. </li>
|
||
|
|
<li><p>Update the HTTP server instance configuration for the Websphere Version 3.5.x instance that is being migrated. This method changes the HTTP instance configuration to work with the WebSphere Application Server - Express instance and makes the Websphere Version 3.5.x instance no longer usable.</p></li>
|
||
|
|
</ul>
|
||
|
|
<p>For more information, see <a href="../../../rzaie/rzaiegetstarted.htm">Start the HTTP Server Administration interface</a>.</p>
|
||
|
|
</li>
|
||
|
|
|
||
|
|
<li><p><strong>Configure the virtual host
|
||
|
|
for the WebSphere Application Server - Express instance.</strong>
|
||
|
|
<br>This step ensures that both the host and HTTP transport port number exist in the virtual host list. For more information, see <a href="../admin/guimngvhsts.htm">Manage virtual hosts for your application server</a> in the <em>Administration</em> topic.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong><a href="../admin/qshgenplgcfg.htm">Regenerate the Web server plugin configuration</a></strong>
|
||
|
|
<br>This step needs to be done after any configuration changes have been made. </p></li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
<p><strong>Change the ConnectionIOTimeOut properties for the Web container</strong></p>
|
||
|
|
<p>Peformance changes to the WebSphere HTTP plug-ins may result in <strong>InterruptedIOTimeout</strong> exceptions while reading large requests, such as receiving file uploads to a servlet. Increase the <strong>ConnectionIOTimeout</strong> value in the Web Container of your application as follows:</p>
|
||
|
|
<ol>
|
||
|
|
<li>In the topology tree, expand <strong>Servers</strong> and click <strong>Application Servers</strong>. </li>
|
||
|
|
<li>On the <strong>Application Servers</strong> page, click the name of the server that you want to modify. </li>
|
||
|
|
<li>On the server's detail page, click <strong>Web Container</strong>.</li>
|
||
|
|
<li>On the <strong>Web Container</strong> page, click <strong>HTTP Transports</strong>.</li>
|
||
|
|
<li>On the <strong>HTTP Transports</strong> page, click the transport that you want to modify.</li>
|
||
|
|
|
||
|
|
<li>Click <strong>Custom properties</strong>.</li>
|
||
|
|
|
||
|
|
<li>Click <strong>New</strong> and add a property named <strong>ConnectionIOTimeout</strong>. Set the property to the maximum time a servlet or JSP waits for a client to transmit request data.</li>
|
||
|
|
|
||
|
|
<li><p>After you add a virtual host alias, you must restart the application server. See <a href="../admin/guistrtntstapp.htm">Start and test your application server</a> in the <em>Administration</em> topic for more information.</p></li>
|
||
|
|
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</HTML>
|