此场景与v5中的应用程序更新场景相似。
This scenario is similar to the application update scenario in Version 5.
下表总结了几个细粒度更新场景和对应的回收行为。
The table below summarizes several fine-grained update scenarios and the corresponding recycle behavior.
换句话说，这实际上只是上面演示的后期更新场景的一种特殊情况。
In other words, this is really just a special case of the late update scenario demonstrated above.
针对技术更新和后期更新场景指出的所有局限性也适用于往返更新场景。
All of the limitations noted for the technical update and late update scenarios apply to the round-trip scenario.
在后期更新场景中，业务分析人员在已将业务模型导出到WebSphereIntegrationDeveloper以后对业务模型做出更改。
In the late update scenario, the business analyst makes a change to the business model after it has been exported to WebSphere Integration Developer.
本小节将展示这样一个场景：业务分析师想要在 WBM模型中进行一些新的修改，然后将这些更新合并到现有WID模块中。
This section illustrates the scenario where the business analyst would like to make other new changes in WBM model, and merging these updates into the existing WID module.
从场景直接更新类的签名（方法和属性），以使我们不必回到类的说明中添加缺少的方法。
Update class signatures (methods and attributes) directly from scenarios, so that we could add missing methods on the fly without having to revert to the class specification.
某些应用程序需要了解特定时间范围内的数据库更新，以便进行数据复制、场景审计等等。
Some applications need to know database updates for certain time ranges, which may be used for replication of data, auditing scenarios, and so forth.
您更新需求和用例，进入场景(通过用例的路径)，然后到达代码，并做出必要的变更。
You walk through updating requirements and use cases, get introduced to scenarios (a path through a use case), then go to the code and make the necessary changes.
此类场景可能不仅是简单的更新数据库中的记录。
Such scenarios may involve more than simply updating a record in a database.
一个样例场景就是包含定期更新的通知页面的网站的调度爬行器。
A sample scenario is based on a scheduled crawler for a website with regularly updated announcement pages.
一个典型的测试场景中有500个用户，产生705个资源，更新2,287个资源，并且每小时创建5,876个评论。
A typical test scenario run for 500 users will produce 705 resources, update 2,287 resources, and create 5,876 comments per hour.
本场景不需要该更新。
取决于您是否希望更新业务项或逻辑数据模型，中间会合式场景有两种用例。
There are two use cases in the meet-in-the-middle scenario, depending on whether you want to update your business items or logical data models.
如果以后支持更多场景，本文也会相应地更新。
This article will also document further scenarios as they become supported.
在这个场景中，可以使用异构更新在一个数据库操作中更新order和order_items表。
In this scenario, you could use a heterogeneous update to update the ORDER and ORDER_ITEMS table in a single database operation.
对于那些值更新非常频繁，例如金融市场中的股票价格等场景，这种方式能够很大程度上改善性能。
This can significantly improve performance in scenarios where values change very frequently such as stock prices in financial markets.
将下面的场景作为一个示例：用户希望更新Web站点徽标图像文件，并且将原始文件作为.war文件应用程序的一部分进行存档。
Take the following scenario as an example: a user wants to update the Web site logo image file and the original file is archived as part of a.war file application.
利用这个应用程序，我们介绍了业务集成自服务场景的两种用况(use case)：外部顾客注册和内部顾客更新。
With this application, we presented two use cases of a business integration self-service scenario: external customer registration and internal customer update.
这些模板的一些常见用法(叫作rjs模板)为更新多个div、处理表单验证和管理Ajax错误场景。
Some common USES for these templates, called RJS templates, are updating more than one div, handling form validations, and managing Ajax error scenarios.
我们也将讨论零售商所需的缓存失效场景来反映目录更新，并考虑eXtremeScale如何在这些事件中潜在改善用户体验。
We will also discuss the cache invalidation scenarios needed by retailers to reflect catalog updates, and consider how eXtreme Scale potentially improves the end user experience during these events.
虽然，我们已经竭尽全力地对索引更新的发布进行了优化，但还是有几个常见的场景会为Solr带来问题
While every effort has been made to optimize the distribution of index updates, a couple of common scenarios can cause problems for Solr
然后，查看目标场景的action属性，并根据这个属性值更新（设置或相加）本地状态模型中的分数。
The score is updated by looking at the action attribute for the target scene and using this either to set or to add to the score in the local state model.
场景：更新产品数据库
特别要注意，搜索、查看、更新和协作类型的mashup行为是之前描述的初始业务场景的基础。
It is important to note that the search, review, update, and collaborate types of mashup behaviors are the basis for the initial set of business scenarios described previously.
这些命令的适用于将多个相关WebSphere应用程序部署在集群上且一起更新的场景。
The applicable scenario for using these commands is where multiple related WebSphere applications are deployed on a cluster and are updated together.
在这个场景中，Jane尝试更新Maria的姓名，这触发对Jane修改name字段的权限的检查。
In this particular scenario, Jane is attempting to update Maria's name, in which case a check on Jane's authority to modify the name field is launched.
我们仔细检查下面这个场景：一个web页面中的层级数据显示和数据更新。
Let us consider the following scenario of multi-level hierarchical data display and data updating in a web page.
这是一个RTLS硬件提供者提供的实时位置更新的基本场景，作为Maximo 的位置更新交付。
This is the basic scenario of real-time location updates provided by a RTLS hardware provider, delivered as location updates to Maximo.
更新之后，复制localstate序列中的初始场景，然后将ref和title属性设置为适合新场景的值。
Once this has been updated, the initial scene in the local-state's sequence is duplicated, then the ref and title attributes are set as appropriate for the new scene.
应用推荐