The following sections describe the steps to build the database synchronization scenario.
以下各部分将描述构建数据库同步场景的步骤。
The database synchronization scenario is a good example where you can put both the inbound and outbound capabilities of the JDBC adapter to use.
数据库同步场景是一个很好的示例，其中您可以放置要使用的JDBC适配器的入站和出站功能。
However, in that case we wouldn't have had a simple scenario to show you the basic workings of the synchronization wizard.
但如果这样做，我们就没有一个简单场景来向您展示同步向导的基本运作方式。
The following scenario is a more realistic one that provides insight into how to approach synchronization when you have both model changes and implementation changes, some of which may be in conflict.
接下来的场景更接近于现实情况，它深入探析如何在既有模型更改又有实现更改时实现同步，有些更改可能会有不一致。
The first obvious scenario is synchronization of libraries and content between OEM and Suppliers.
首当其冲的是在OEM和供应方之间的库和内容的同步。
In this scenario, the logo update and synchronization should be a parent to the user without the manual intervention of a WebSphere administrator.
在这个场景中，徽标的更新和同步对于用户来说应该是透明的，无需WebSphere管理员进行人工干预。
For example, because a hung thread might occur when a wait leak, excessive synchronization, or a deadlock scenario takes place, the hung thread problem consists of three scenarios.
例如，在出现等待leak、过量同步或死锁时会发生hung线程，因此hung线程问题包含这三种场景。
For example, because a hung thread might occur when a wait leak, excessive synchronization, or a deadlock scenario takes place, the hung thread problem consists of three scenarios.
例如，在出现等待leak、过量同步或死锁时会发生hung线程，因此hung线程问题包含这三种场景。
应用推荐