Use the migration tools to migrate from WebSphere® Application Server
Versão 7.0 ou posterior to a new Versão 9.0 stand-alone application server profile.
Before you begin
Configurações suportadas: Este
artigo trata da migração da configuração de perfil. Para migrar seus aplicativos para a versão mais recente, use o Kit
de Ferramentas de Migração do WebSphere Application Server. Para obter
mais informações, consulte o Kit
de ferramentas de migração no WASdev.
sptcfg
Read Overview of migration, coexistence, and interoperability and Migration considerations.
For resources to help you plan and perform your migration,
visit Knowledge Collection: Migration planning for WebSphere Application Server.
For help, read Troubleshooting migration.
Before following these instructions, perform the actions in Preparing for product-configuration migration.
Tip: Before migrating the previous version WebSphere Application Server stand-alone application server profile, use the
backupConfig command or your own preferred backup utility to back up your
existing configuration if you want to be able to restore it to its previous state after migration.
See backupConfig command for more information. Make sure that you note the exact name
and location of this backed-up configuration.
Rather than specifying individual parameters on migration commands, you can specify the
-properties file_name.properties parameter to input a properties
file. For more information, see Defining your migration through properties.
Procedure
- Create a WebSphere Application Server
Versão 9.0 profile to receive the source configuration.
- Start the Qshell environment so that you can run WebSphere Application Server scripts.
Enter the following command from a command line:
STRQSH
- Run the dspwasinst script to obtain the node name and server name for the
Versão 7.0 ou posterior instance or profile that is to be migrated.
Use the following
parameters:
app_server_root/bin/dspwasinst
-instance 70_profile_name
where
- app_server_root is the location of the source installation
that contains the instance or profile to be migrated
- 70_profile_name is the name of the source instance or
profile that is to be migrated
The name of the node is listed in the
Node section, and the name of the server is listed
in the
Information for server section.
- Run the manageprofiles script.
Use the following
parameters:
app_server_root/bin/manageprofiles
-create
-profileName 90_profile_name
-startingPort starting_port_number
-templatePath app_server_root/profileTemplates/default
-serverName 70_application_server_name
-nodeName 70_node_name
where
For details on the syntax and parameters of the manageprofiles command, see
manageprofiles command.
- Save the configuration from the source WebSphere Application Server
installation.
- Start the Qshell environment so that you can run WebSphere Application Server scripts.
Enter the following command from a command line:
STRQSH
- Run the WASPreUpgrade script.
Use the following parameters:
app_server_root/bin/WASPreUpgrade
backup_directory_name
profile_root
where
For a full explanation of the WASPreUpgrade command and its parameters, read
Comando WASPreUpgrade.
- Restore the WebSphere Application Server source configuration into the
target Versão 9.0 profile.
- Start the Qshell environment so that you can run WebSphere Application Server scripts.
Enter the following command from a command line:
STRQSH
- Run the WASPostUpgrade script.
Use the following
parameters:
app_server_root/bin/WASPostUpgrade
backup_directory_name
-profileName 90_profile_name
[-setPorts useOld | generateNew | port_starting_number]
where
- app_server_root is the location where Versão 9.0 is installed.
- backup_directory_name is the required name of the directory
in which the WASPreUpgrade tool stored the saved configuration and files and from
which the WASPostUpgrade tool reads the configuration and files.
- 90_profile_name is the name of the Versão 9.0 profile to which the script migrates your
configuration.
- -setPorts specifies which port values to use on the IBM® i server where the migration is being performed.
- useOld (default): Use the same ports that the old profile used.
- generateNew: Generate new ports based on the default port assignments.
- port_starting_number: Generate new ports, incrementing from
the specified value.
It is recommended that you always specify the -setPorts parameter to
generateNew or a starting port value if you do not want your profile's ports to
conflict with the default profile's ports.
Note: When migrating a stand-alone
application server from Versão 7.0 ou posterior to Versão 9.0, you can choose a stand-alone application server node
that has already been registered with an administrative agent as the target of the
migration.
For a full explanation of the WASPostUpgrade command and its parameters, read
Comando WASPostUpgrade.
- Verify that your configuration and applications were migrated correctly.
If the configuration was migrated correctly but any applications were not installed, you can run
the WASMigrationAppInstaller command to install only the applications that were
not migrated. For more information, see WASMigrationAppInstaller command.
- Start the WebSphere Application Server
Versão 9.0 profile that received the migrated
configuration.
- Start the QWAS9 subsystem if it is not already started.
Enter the following command from a command line:
STRSBS QWAS9/QWAS9
- Start the Qshell environment so that you can run WebSphere Application Server scripts.
Enter the following command from a command line:
STRQSH
- Run the startServer script.
Use the following
parameters:
app_server_root/bin/startServer
-profileName 90_profile_name
70_server_name
where
- app_server_root is the location where Versão 9.0 is installed
- 90_profile_name is the name of the Versão 9.0 profile created in an earlier step
- 70_server_name is the name of the Versão 7.0 ou posterior application server that was migrated