Migrate to a new WebSphere Application Server

Migrate to a new WebSphere Application Server - Express instance

Tools for migrating administrative configurations are provided for Versions 3.5 and later. This support enables Version 3.5.6 Standard Edition (or later) to be upgraded to WebSphere Application Server - Express.

If multiple application servers exist in your Version 3.5.x environment, you have these options:

The migration tools merge applications from multiple application servers of a Version 3.5.x instance into a single EAR file containing multiple Web modules, one Web module for each application server to be migrated. The EAR file is deployed as a single application within the WebSphere Application Server - Express instance.
If you do not want your applications merged into a single EAR file and run in the same application server, you need to separate them into different Version 3.5.x instances prior to running the migration tools. Each instance should have a single application server containing the desired Web application or applications. You then migrate each Version 3.5.x instance to a corresponding WebSphere Application Server - Express instance.
Use the WebSphere Development Studio Client environment to build an EAR file for each 3.5.x application you have and deploy each EAR file into a single Express instance. This option does not use the migration tools shipped with WebSphere Application Server - Express.

A summary of the product migration process is as follows.

Create a WebSphere Application Server - Express instance.
Start the Version 3.5 instance that is being migrated.
Save the Version 3.5 configuration.
Restore the Version 3.5 configuration into a WebSphere Application Server - Express instance.
Start the WebSphere Application Server - Express instance.

Create a WebSphere Application Server - Express instance

See Create a new application server in the Administration topic for details on how to create a WebSphere Application Server - Express instance.

Start the Version 3.5 instance that is being migrated

Perform the following steps to start the WebSphere Application Server Version 3.5 instance:

Enter the following command from an CL command line:
```
STRQSH
```
This starts the Qshell environment so that you can run WebSphere Application Server scripts.
Run the strwasinst script with the following parameters:
```
/QIBM/ProdData/WebASAdv/bin/strwasinst -instance 3.5.xInstanceName
```
where 3.5.xInstanceName is the name of the Version 3.5.x instance that is being migrated. You must wait for the administrative server to start successfully before continuing.

Save the Version 3.5 configuration

If you have servlets in the Version 3.5.x default_app Web Application, the WasPreUpgrade migration tool does not migrate them. If you wish to have these servlets migrated, you must change the default_app name before calling WasPreUpgrade. See Issues concerning the migration of JSPs and Servlets in the Application Development topic for more information.

Perform the following steps to save the Version 3.5 configuration:

Enter the following command from an CL command line:
```
STRQSH
```
This starts the Qshell environment so that you can run WebSphere Application Server scripts.
Run the WebSphere Application Server - Express WasPreUpgrade script as shown below:
```
/QIBM/ProdData/WebASE/ASE5/bin/WASPreUpgrade    
/backup/myBackupDirectory  
/QIBM/UserData/WebAsAdv/3.5.xInstanceName   
adminNodeName
-nameServiceHost adminNodeName 
-nameServicePort port_number
```
where:
- /backup/myBackupDirectory (required parameter) is the fully qualified path to the integrated file system directory where the WasPreUpgrade migration tool stores the saved configuration and files. The directory is created if it does not already exist. Additionally,the tool writes a log file called WasPreUpgrade.log that chronicles the steps taken by WasPreUpgrade.
- /QIBM/UserData/WebAsAdv/3.5.xInstanceName (required parameter) is the fully qualified path of the Version 3.5.x administrative instance being migrated.
- adminNodeName (required parameter) is the name of the administration node for the Version 3.5.x instance. Generally, this is the iSeries host name from CFGTCP option 12. The WASPreupgrade tool invokes the Version 3.5 XMLConfig tool using this parameter.
- The -nameServiceHost and -nameServicePort parameters are also passed to XMLConfig. They are needed to override the default host name and port number used by XMLConfig and are required parameters when the Version 3.5.x instance being migrated is not the default instance. The value for -nameServiceHost is the TCP/IP host name of the iSeries server. The value for the -nameServicePort is the bootstrap port for the Version 3.5.x administrative server. The default bootstrap port is 900.
For a full explanation of the WasPreUpgrade migration tool and parameters, see The WASPreUpgrade script.

Restore the Version 3.5 configuration into a WebSphere Application Server - Express instance

Perform the following steps to restore the Version 3.5 configuration into a WebSphere Application Server - Express instance:

Enter the following command from an CL command line:
```
STRQSH
```
This starts the Qshell environment so that you can run WebSphere Application Server scripts.
Run the WasPostUpgrade script with the following parameters:
```
/QIBM/ProdData/WebASE/ASE5/bin/WASPostUpgrade
backupDirectoryName
[-instance 5_instance_name]
[-portBlock port_starting_number]
```
The first argument is required. Supported arguments include:
- backupDirectory
  Required 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. The WASPreUpgrade tool creates this directory if it does not already exist.
- -portBlock
  This is an optional parameter. The value portblock specifies the first number of a block of port numbers that your instance uses. Specify the first port in a group of unused ports on your iSeries server. You can use the Work with TCP/IP Network Status (NETSTAT *CNN) command to display a list of port numbers that are currently being used. This parameter is case sensitive.
  
  Note: Although this is an optional parameter, it is recommended that you always specify the parameter (or the specific port parameters, described below) if you do not want your instance's ports to conflict with the default instance's ports.
For the -portBlock parameter, the script checks instances of WebSphere Application Server - Express. The script is not able to detect port usage by other applications, including previous versions of WebSphere Application Server.

For a full explanation of the WasPostUpgrade migration tool and parameters, see The WASPostUpgrade script.

Start the WebSphere Application Server - Express instance

Perform the following steps to start the WebSphere Application Server - Express instance:

Enter the following command from an CL command line to start the QASE5 subsystem if it is not already started:
```
STRSBS QASE5/QASE5
```
Enter the following command from an CL command line:
```
STRQSH
```
This starts the Qshell environment so that you can run WebSphere Application Server scripts.
Run the startServer script with the following parameters:
```
/QIBM/ProdData/WebASE/ASE5/bin/startServer
-instance 50InstanceName 50ApplicationServerName
```
where 50InstanceName is the name of the WebSphere Application Server - Express instance created in an earlier step, and 50ApplicationServerName is the name of the WebSphere Application Server - Express application server created in an earlier step.