在完成更改之后，您要确保重新激活同步化功能。
Be sure to re-enable synchronization after you complete the changes.
随着代码库的不断增大，这些测试将使开发人员能够很有把握地完成更改。
As the code base grows, these tests allow developers to integrate changes with confidence.
完成更改之后，删除登录、用户配置文件或任何启动脚本中对ulimit命令的引用。
Once the changes have been made, remove references to the ulimit command in the login, user profiles or any startup scripts.
在完成更改后，执行mksecldap命令对AIX5LLDAP客户端进行配置。
Execute the mksecldap command to configure the AIX 5L LDAP client after the change.
当应用程序完成更改时，DataGraph 被传递回ContentAPI服务之一，中介器将处理更改摘要。
When applications are finished making changes, the DataGraph is passed back to one of the Content API services, and the mediators process the change summary.
完成更改并重新部署小部件之后，用户将在Homepage的小部件的头部栏上看到编辑图标，如图8 所示。
When you make this change and redeploy the widget, users see an edit icon in the header bar of the widget in the Home page as shown in Figure 8.
当您完成更改以后，选择CreateArtifactTemplate操作，当需要输入名字时，输入您想要升级的模板的名字。
When you're finished making changes, select the Create Artifact Template action and, when prompted for the name, enter the same name as the template that you want to update.
至此，业务分析人员2已完成了请求的更改。
At this point, Business Analyst 2 has completed the requested changes.
之前的步骤需要花费大量时间来完成，而且只能更改一个用户和组的UID 和GID。
The previous steps took time to complete, and you only changed the UID and GID for a single user and group.
完成的更改集。
潜在的消息格式更改是通过相关SDO接口完成的。
Potential message format changes are done using the relevant SDO interfaces.
评审接下来就是参与者所做的更改完成了评审的生命周期。
The review follows a lifecycle that changes as participants complete the review.
在将构件导入工具包时，将自动完成产品迁移所需的更改。
Changes needed for product migration will be done automatically when the artifacts are imported into the toolkit.
项目通常不会过多更改，因此这通常可以离线完成。
Items usually don't change much, so this often can be computed offline.
更改参数能够被完成只是因为它适用于数据库节点。
Changing parameters is done just as it is for the database node.
确保安装过程成功完成(图53)，并保存更改。
Make sure that the install process completes successfully (Figure 53), and save your changes.
甚至有两个“撤销”选项：撤销上次更改（跳至刚好未完成的记录）和撤销所有更改（如果您对某些内容完全改变主意）。
There are even two "undo" options: undo the last change, which will bring you to the record that was just undone, and undo all changes (if you have completely changed your mind about something).
通过此行为，可以启动灾难数据中心，但无需首先完成安装更改的实施。
This behavior will enable you to bring up your disaster data center without requiring that you first complete the rollout of the install change.
至此，业务分析人员2已完成所需的更改。
At this point, Business Analyst 2 has completed making the required changes.
应用程序操作(如代码或配置更改)需要在分析完成之后进行。
Appropriate actions (such as code or configuration changes) need to be taken after the analysis is complete.
做出更改并完成们测试——一定要使源代码树与部署树保持同步！
Make changes and test them out — just be sure to keep your source tree in sync with your deployment tree!
完成这些密码更改要花费不少时间，而且是重复性的。
Going through these password changes takes time and is very repetitive.
这个时间段从开始安装更改时开始，到安装更改完成时结束。
This time period starts when you being your install change. It ends when the install change is complete.
您在布局更改时要完成的就是修改XSL文件，而不必重构程序。
What you need to do when the layout changes is to modify the XSL files without rebuilding the program.
完成向导步骤后，保存更改。
现在您已经完成了配置更改，必须把 PLUTO_HOME/webapps/pluto目录打包成名为 pluto-portal-1.1.0.war 的 WAR文件。
Now that you've completed the configuration changes, you must package the PLUTO_HOME/webapps/pluto directory into a WAR file named pluto-portal-1.1.0.war.
保存更改，完成库的创建。
Save changes to complete the library creation. The new library will be listed, as shown in Figure 3.
在做出每个更改时，您可以单击它并选择ChangeApplied以指示您已完成该更改，或选择Change Ignored以指示您发现该更改与业务不相关。
As you make each change, you can click it and select change Applied to indicate you completed it, or change Ignored to indicate that you found the change not to be business relevant.
完成上述更改后编译您的servlet，若需要请重启servlet引擎。
Compile your servlet with these changes, and restart your servlet engine if you need to.
完成导入(Ctrl +Shift +o)并保存更改(Ctrl +s)。
Fix the imports (Ctrl + Shift + o) and save the changes (Ctrl + s).
应用推荐