启动迁移向导。
This starts the Migration Wizard.
这将启动迁移向导。
There are two ways to access the Migration Wizard.
有两种方式访问迁移向导。
The migration wizard tool is used to perform the migration.
使用迁移向导工具执行迁移。
The migration wizard can be found on the FirstSteps panel.
迁移向导可以在FirstSteps面板上找到。
When using the migration wizard, these log files are created.
当使用迁移向导时，将创建下面的日志文件。
Figure 26 shows the new options available in the FDL2BPEL migration wizard.
图26显示了FDL2BPEL迁移向导中可用的新选项。
All the processes are reduced to a few clicks in the migration wizard.
所有的流程都减少到几次点击在迁移向导。
Figure 5 shows the "Add local client views" page in the J2EE Migration wizard.
图5在J2EEMigration向导中显示了“图5 .添加本地客户端视图”页。
Begin the migration wizard by selecting migration wizard, as shown in Figure 2.
通过选择“Migration wizard”开始使用迁移向导，如图2所示。
Click the green arrow icon to bring up the Migration Wizard as shown in Figure 1.
单击绿色箭头图标以启动迁移向导，如图1所示。
The migration wizard calls these tools when it is used to migrate the previous release.
当使用迁移向导来迁移先前版本时，该迁移向导将调用这些工具。
This tool can be run by itself from the command line or as part of the Migration wizard.
此工具可以从命令行自行运行，也可以作为迁移向导的一部分运行。
There is now a migration wizard that guides users through a migration after V6 is installed.
现在，安装V6以后，会有一个迁移向导指导用户迁移。
While working with the Migration Wizard, turn off the project auto-building in Integration Developer.
在使用迁移向导时，关闭IntegrationDeveloper中的项目自动构建选项。
Use either the migration wizard or the migration command line tools to migrate the node to the V6 profile.
使用迁移向导或迁移命令行工具将节点迁移到V6配置文件。
The migration wizard only updates your deployment descriptors, not the code in your EJB implementations.
移植向导仅更新了您的部署描述符，而没有更新ejb实现中的代码。
This tool can be found in the firststeps directory under each profile and can be used to launch the Migration wizard.
可以在每个概要的firststeps目录下找到此工具，并且可以用于启动迁移向导。
However the AJDT development team has smoothed out this process as much as possible by introducing a migration wizard, as shown in Figure 10.
但是AJDT开发团队已经通过引入迁移向导使这一过程尽可能的顺利，如图10所示。
The migration wizard is new for V6 and replaces the migration panels that were a part of the Application Server Installer in previous versions.
迁移向导是V6 中的一个新内容，它取代了先前版本中作为ApplicationServer安装程序的一部分的迁移面板。
We expect that real world migration projects will make use of the migration Wizard, but it will also involve a fair amount of manual migration tasks.
我们希望实际的迁移项目使用迁移向导，但是它也会涉及到大量的手动迁移工作。
You should now have a high level understanding of the changes involved in migrating to WebSphere Application Server V6, such as the migration wizard.
现在，您应该对向WebSphereApplicationServerv 6迁移中涉及到的改变(如迁移向导)有了大概的了解。
When migrating from a V4 multi-node configuration, the migration wizard cannot be used to migrate the deployment manager, this step must be completed manually.
当从v4多节点配置迁移时，不能用迁移向导来迁移部署管理器，这一步必须手动完成。
The Migration Wizard creates a new "Business Integration Module" project, imports all the existing Application Developer artifacts, and converts the source artifacts.
迁移向导将创建一个新的“业务集成模块”项目，导入所有现有的Application Developer构件，并转换源构件。
We show you how to import the project into Integration Developer using the Migration Wizard, re-wire the components, and get it ready for deployment on Process Server.
我们向您展示了如何使用迁移向导将项目导入到IntegrationDeveloper，如何重新连接组件，以及如何为在Process Server部署做好准备。
To reduce complexity, the WebSphere Commerce migration wizard was created to provide users with an easy to understand interface to guide them through the migration process.
为降低复杂性，所创建的WebSphereCommerce迁移向导为用户提供了理解界面的便利途径，以指导他们完成迁移过程。
The migration Wizard automatically migrates all BPEL files and BPEL WSDL extensions for you, then you must perform a set of manual migration steps to complete the migration.
迁移向导将为您自动迁移所有BPEL文件和BPELWSDL扩展，然后您必须执行一组手动迁移步骤以完成这一迁移。
Therefore, because some or all of the user objects and mailboxes already exist, Migration Wizard run in default mode (instead of clone mode) the next time you start it.
因此，由于部分或全部用户对象和邮箱已存在，因此当您下次启动迁移向导时，它将以默认模式(而不是克隆模式)运行。
Whether you are performing a manual migration or using the migration wizard, you should always review the log files for any errors or warnings that might require some kind of action.
无论您是在执行手动迁移还是使用迁移向导，都应该始终阅读日志文件以了解可能需要某些操作的错误或警告。
I would ask you to try some sample code in the migration wizard to ensure that it is working properly, and take an additional look at your application to eliminate any potential issues.
我建议您可以在移植向导中尝试实例代码以确保其是否正常工作，并且查看您的应用程序以减少潜在的问题。
应用推荐