97 lines
7.2 KiB
HTML
97 lines
7.2 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>The WASPostUpgrade script</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h3><a name="qshmigpost"></a>The WASPostUpgrade script</h3>
|
||
|
|
|
||
|
|
|
||
|
|
<p>The <strong>WASPostUpgrade</strong> command is a migration tool for migrating the configuration and applications of previous versions to a WebSphere Application Server - Express application server node. The script is located in the /QIBM/ProdData/WebASE51/ASE/bin directory.</p>
|
||
|
|
|
||
|
|
<p>The WASPostUpgrade tool installs all migrated applications into the /QIBM/UserData/WebASE51/ASE/<em>instance</em>/installedApps directory, where <em>instance</em> is the name of the instance to which you are migrating. The tool includes applications from the installedApps directory and other directories from the previous version.</p>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
<p><strong>Authority</strong></p>
|
||
|
|
<p>To run this script, your user profile must have *ALLOBJ authority.</p>
|
||
|
|
|
||
|
|
<p><strong>Syntax</strong></p>
|
||
|
|
<p>The syntax of the WASPostUpgrade script is:</p>
|
||
|
|
|
||
|
|
<pre>WASPostUpgrade <em>backupDirectory</em> -instance <em>instance</em>
|
||
|
|
[ -cellName <em>cell_name</em> ] [ -nodeName <em>node_name</em> ]
|
||
|
|
[ -webModuleAdditionalClasspath <em>classpath</em> ]
|
||
|
|
[ -documentRootLimit <em>number</em> ]
|
||
|
|
[ -substitute"<em>key1</em>=<em>value1</em>[;<em>key2</em>=<em>value2</em>;[...]]" ]
|
||
|
|
[ -portBlock <em>port_starting_number</em> ] [ -backupConfig < true | false > ]
|
||
|
|
[ -replacePorts < true | false > ] [ [ -traceString <em>trace_spec</em>
|
||
|
|
[ -traceFile <em>file_name</em> ] ]</pre>
|
||
|
|
|
||
|
|
<p><strong>Parameters</strong></p>
|
||
|
|
<p>The parameters of the WASPostUpgrade script are:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><p><strong><em>backupDirectory</em></strong>
|
||
|
|
<br>This is a required parameter. The value <em>backupDirectory</em> specifies the name of the directory in which the WASPreUpgrade tool stores the saved configuration and files, and from which the WASPostUpgrade tool reads the configuration and files.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>-instance</strong>
|
||
|
|
<br>This is a required parameter. The value <em>instance</em> specifies the name of the WebSphere Application Server - Express instance to which the script migrates your configuration.</p></li>
|
||
|
|
|
||
|
|
|
||
|
|
<li><p><strong>-cellName</strong>
|
||
|
|
<br>This is an optional parameter. The value <em>cell_name</em> specifies the cell name that the script updates. If you do not specify this parameter, the script reads the configuration to determine the cell name. If only one cell name is found, the script updates that cell. If no cell name is found, or if more than one cell name is found, the script returns an error.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>-nodeName</strong>
|
||
|
|
<br>This is an optional parameter. The value <em>node_name</em> specifies the node name that the script updates. If you do not specify this parameter, the script reads the configuration to determine the node name. If only one node name is found, the script updates that cell. If no node name is found, or if more than one node name is found, the script returns an error.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>-webModuleAdditionalClasspath</strong>
|
||
|
|
<br>This is an optional parameter. The value <em>classpath</em> specifies the path or the path and file names of specific directories or files that you do not want copied into the Web archive (WAR) file that the script processes. Instead, the script adds the paths and files to the Web Module extension (ibm-web-ext.xmi) additionalClassPath attribute. If you want to specify multiple values for this parameter, separate them with a colon (:).</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>-documentRootLimit</strong>
|
||
|
|
<br>This is an optional parameter. The value <em>number</em> specifies the number of files that the script copies from the document-root field of your Web application. The default value is 300.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>-substitute</strong>
|
||
|
|
<br>This is an optional argument. This parameter specifies values for security variables to substitute. (for example, <tt>-substitute "NODE_NAME=admin_node;APP_SERVER=default_server"</tt>).</p>
|
||
|
|
<p>In the input XML data file, each key appears as $key$ for substitution. This argument replaces all occurrences of $NODE_NAME$ and $APP_SERVER$ with admin_node and default_server, respectively, in the input XML file.</p>
|
||
|
|
<p>If the substitution string contains semicolons, use $semiColon$ to separate it from the ";" delimiter.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>-portBlock</strong>
|
||
|
|
<br>This is an optional parameter. The value <em>port_starting_number</em> specifies the first of a block of 10-15 consecutive port numbers that zare not in use on the iSeries server where the migration is being performed. It is recommended that you always specify the -portBlock parameter if you do not want your instance's ports to conflict with the default instance's ports.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>-backupConfig</strong>
|
||
|
|
<br>This is an optional parameter. Valid values for this parameter are true and false. The default value is true. If true is specified, then the existing Version 5.1 configuration is saved before any changes are made by the WASPortUpgrade tool.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>-replacePorts</strong>
|
||
|
|
<br>This is an optional parameter. Valid values for this parameter are true and false. The default value is false. If true is specified, all virtual host alias port settings are replaced during migration. If migrating from Version 5.0.x, virtual host and transport settings in the Version 5.1 instance are replaced by the settings from the Version 5.0.x instance.</p></p></li>
|
||
|
|
|
||
|
|
<li><p><strong>-traceString</strong>
|
||
|
|
<br>This is an optional parameter. The value <em>trace_spec</em> specifies the trace information that you want to collect. To gather all trace information, specify <tt>"*=all=enabled"</tt> (with quotation marks). The default is to not gather trace information. If you specify this parameter, you must also specify the -traceFile parameter.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>-traceFile</strong>
|
||
|
|
<br>This is an optional parameter. The value <em>trace_file</em> specifies the name of the output file for trace information. If you specify the -traceString parameter but do not specify the -traceFile parameter, the script does not generate a trace file.</p></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p><strong>Logging</strong></p>
|
||
|
|
<p>The WASPostUpgrade tool displays status to the screen while running. It also saves a more extensive set of logging information in the WASPostUpgrade.log file. This file is located in the /QIBM/UserData/WebASE51/ASE/<em>instance</em>/logs directory, where <em>instance</em> is the name of the instance that you are migrating to.</p>
|
||
|
|
|
||
|
|
<p><strong>Examples</strong></p>
|
||
|
|
|
||
|
|
<p><strong>Migrate from WebSphere Application Server Version 3.5.x Standard Edition</strong></p>
|
||
|
|
|
||
|
|
<p>This example illustrates how to migrate from WebSphere Application Server Version 3.5.x, Advanced Edition. The WASPreUpgrade script created the backup directory named /home/was35_instancename/WAS35Std. The WASPostUpgrade script reads the configuration from this directory to migrate to WebSphere Application Server - Express.</p>
|
||
|
|
|
||
|
|
<pre>WASPostUpgrade /home/was35_instancename/WAS35Std</pre>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|