Use the migration tools to migrate from a WebSphere® Application Server Versão 7.0 ou posterior stand-alone application server profile to a Versão 9.0 stand-alone application
server.
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
See Overview of migration, coexistence, and interoperability and Migration considerations.
Tip: Before migrating a WebSphere Application Server Versão 7.0 ou posterior stand-alone application server, 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.
For more information, see backupConfig command. 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.
About this task
If your scenario includes migrating a WebSphere Application Server
Versão 7.0 ou posterior configuration on one machine to Versão 9.0 on another machine, use the alternate procedure
described in Migrating to a Versão 9.0 stand-alone application server on a remote machine.
Para Usuários de Transição: Anteriormente, os seguintes produtos precisavam de ferramentas de migração separadas, mas
agora são migrados como parte dos procedimentos de migração padrão:
- WebSphere Extended Deployment Compute Grid ou
Feature Pack for Modern Batch
- WebSphere Virtual Enterprise ou
Intelligent Management
Para obter informações adicionais sobre essas mudanças, consulte
O que há de novo para migração.
trns
For help, read Troubleshooting migration.
Procedure
Choose from one of the following options to migrate your configuration, and then verify your
migration.
- Migrate from WebSphere Application Server
Versão 7.0 ou posterior to Versão 9.0
using the migration wizard.
- Stop all of the WebSphere Application Server
Versão 7.0 ou posterior application servers that are running on the
node.
Use the stopServer command from the
app_server_root/bin directory. See stopServer
command for more information.
![[Linux]](../images/linux.gif)
For example, issue the following commands to stop server1 and
server2:
./stopServer.sh server1
./stopServer.sh server2
If security is enabled, specify the -user and -password parameters on the
stopServer command.
You can migrate a WebSphere Application Server
Versão 7.0 ou posterior node without stopping it; however, you must stop
the node before you can start the Versão 9.0 node that you are
installing. It is not necessary to have the node running to migrate its configuration. The migration
tools can retrieve all the configuration data while the node is stopped.
- Install WebSphere Application Server
Versão 9.0.
See Installing and configuring your application serving environment for more
information.
- Optional: Use the Profile Management tool or the manageprofiles command to create a
WebSphere Application Server
Versão 9.0 profile.
See Managing profiles using the graphical user interface or manageprofiles
command for more information.
- Use the Migration wizard to transfer configuration settings from Versão 7.0 ou posterior to the Versão 9.0
stand-alone application server.
This step transfers applications and configuration information for the Versão 7.0 ou posterior server resources, security, variables, and virtual
hosts to the Versão 9.0 stand-alone application server. All
stored information is in XML files in the
app_server_root/config/cells directory of each product.
The Migration wizard uses the WASPreUpgrade command and WASPostUpgrade command to migrate the data and applications from Versão 7.0 ou posterior to Versão 9.0.
The
WASPreUpgrade tool saves selected files from the install and profile
directories to a backup directory that you specify on a wizard panel. Migration saves files from the
following directories to the backup directory:
- bin
- classes
- config
- installableApps
- installedApps (or an alternate directory specified by the user)
- properties
Later, the Migration wizard uses the WASPostUpgrade tool to copy the
environment in the backup directory to the Versão 9.0
stand-alone application server installation.
- Migrate from WebSphere Application Server Versão 7.0 ou posterior to Versão 9.0 using
the command-line migration tools.
- Stop all of the WebSphere Application Server Versão 7.0 ou posterior application servers that are running on the node.
Use
the stopServer command from the app_server_root/bin directory.
See stopServer command for more information.
![[Linux]](../images/linux.gif)
For example, issue the following commands to stop
server1 and server2 on the Linux operating system:
./stopServer.sh server1
./stopServer.sh server2
If security is enabled,
specify the -user and -password parameters on the stopServer command.
You
can migrate a WebSphere Application Server Versão 7.0 ou posterior node without stopping it; however, you must stop the
node before you can start the Versão 9.0 node that you are
installing. It is not necessary to have the node running to migrate
its configuration. The migration tools can retrieve all the configuration
data while the node is stopped.
- Install WebSphere Application Server Versão 9.0.
See Installing
and configuring your application serving environment for more
information.
- Use the Profile Management tool or the manageprofiles command
to create a WebSphere Application Server Versão 9.0 profile.
See Managing
profiles using the graphical user interface or manageprofiles
command for more information.
- Run the WASPreUpgrade command, specifying
the migration backup directory name and the existing WebSphere Application Server directory name.
Read Comando WASPreUpgrade for more
information.
The
WASPreUpgrade tool saves
selected files from the
/bin directory to a backup
directory you specify on a wizard panel. Migration saves files from
the following directories to the backup directory:
- classes
- config
- installableApps
- installedApps (or an alternate directory
specified by the user)
- properties
- Run the WASPostUpgrade command, specifying
the migration backup directory.
See Comando WASPostUpgrade for more information.
The WASPostUpgrade tool
copies the environment in the backup directory to the WebSphere Application Server Versão 9.0 stand-alone application
server installation.
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.
- 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.
For Compute Grid or Feature Pack for Modern Batch applications, also verify that the job
scheduler was migrated correctly and that you can dispatch jobs to the servers that host your batch
applications.
To verify the job scheduler migration, restart the application server where the job scheduler is
configured. After the server restarts, access the job management console through a web browser.
To verify that the servers that host your batch applications work correctly:
- Verify that the batch applications on the migrated server are started. Examine the server logs
for any errors.
- Verify that you can dispatch batch jobs to the migrated server by submitting a job from the
migrated job scheduler server. You can submit the job by using the Job Management Console, the
WSGrid utility, the EJB interface, or the web services interface.