Scenario three: Compose and store XML documents in DB2 pureXML
方案三：在DB2pureXML 中构建并存储XML文档
Scenario Three: you cook all your own meals, but you feel no desire to get rid of your favorite foods in order to go vegetarian.
场景三：你自己吃自己做，但是你并不必为了吃素而放弃你喜欢的其它食物。
This paper proposes the typical scenario three network integration capability plan model based on the capability estimate and the indoor audio model.
本文根据容量估算和室内分布系统话务模型提出了典型场景下的三网融合容量规划模型。
The scenario demonstrates the need to both scale and migrate. In both cases three standards play an important role.
这个情景给出了需要扩充和迁移的例子，两种情况下三个标准都起到了重要的作用。
A typical access control and authorization scenario includes three main entities — a subject, a resource, and an action — and their attributes.
典型的访问控制和授权场景包括三个主要实体：主体、资源和动作以及它们的属性。
The point-to-point scenario detailed in this section USES three applications, as shown in Figure 2.
在这个部分中详细描述的点到点场景使用了三个应用程序，如图2所示。
In this article, explore a scenario that implements three widgets that enable a customer service rep to help a user who is trying to complete and submit an online form.
在本文中，我们将探索这样一个场景：实现三个小部件，以支持一个客户服务代表来帮助一个用户，该用户正在尝试完成并提交一个在线表单。
The scenario lets you make two rapid changes and add three components to the original business application.
该场景可以让您做出两项快速修改，并向初始业务应用程序添加三个组件。
Listing 1 contains a SQLHOSTS file for each of the three servers being used for this sample scenario.
清单1包含了一个SQLHOSTS文件，用于本样例场景中使用的三个服务器中的每一个服务器。
Let's take a scenario of a company that has three departments, namely sales, marketing, and finance.
让我们假设有这样一个公司的场景，其中包含三个部门，即销售部门、市场部门和财务部门。
You have successfully tested the migrated application in three different ways, preparing you for a full end-to-end scenario in your environment.
您已经通过三种不同方式成功测试了迁移的应用程序，这就在环境中为您准备了一个完整的端到端场景。
The blue curve shows the evolution of the unperturbed sea-ice extent for the A1B scenario, with the gray shading showing the ensemble spread of three model runs.
蓝色曲线表示A 1 B方案中未受干扰的海冰范围，灰色阴影表示三个模型紧张的整体差幅。
Scenario: You wish to change the name of this three partition database from PRODUCTS to OLDPROD.
场景：希望将这个三分区数据库的名称从 PRODUCTS 改为 OLDPROD。
To develop and deploy the bank scenario that spans into all three application tiers, you need to make the following choices in those tiers.
为了开发和部署跨越所有三个应用程序层的银行场景，需要为这些层中的以下组件选择软件。
For this scenario, select all three layers, click the Add layers icon and close the Catalog window.
对于本场景，选择所有三个层，单击addLayers图标，然后关闭Catalog窗口。
The business scenario used in this article assumes that the IBM Corporation has three different enterprise systems that have a representation of customer.
本文使用的业务场景假设IBMCorporation有三个不同的企业系统，而这些企业系统分别具有自己的客户表示形式。
First, you define three XML Schema Definition (XSD) complex types (as shown in Listing 1) for the scenario described in the previous article of this series.
首先，您需要为本系列文章的上一篇文章中介绍的场景定义三种XML模式定义(XSD)复杂类型(如清单1所示)。
The business scenario assumes that the IBM Corporation has three different enterprise systems that have a representation of customer.
本文的业务场景假设IBMCorporation有三个不同的企业系统，这三个系统都有各自的客户表示形式。
In Figure 6, under Processes in the left tree view, there are three BPELs for each scenario now, and each BPEL only contains the logic for this scenario itself.
在图6中，左侧树视图的Processes下方，有三个BPEL用于各个场景，并且BPEL只包含场景本身的逻辑。
To run this scenario, we set up a Domino cluster with three servers with the following configuration
为了运行这个场景，我们设置了一个具有3 个服务器的Domino集群，其配置如下
Let's create a business scenario that assumes IBM has three different enterprise systems with a representation of the customer.
我们创建一个业务场景，假设IBM有3个不同的企业系统和一个客户代表。
For this sample scenario, three storage areas are created with the names fs1, fs2, and fs3.
对于这个样例场景，有3个存储区域被创建，它们的名称分别为fs1、fs2和fs3。
Take, for instance, the scenario where there are three Web servers feeding two application servers (these can be clones within the same ServerGroup). The formula, then, becomes.
例如，请考虑有三台Web服务器为两台应用程序服务器(它们可以是相同的ServerGroup中的克隆)提供输入的情景。
Let's simulate this scenario, assuming that objects stay six months in DASD, three years in external storage, and seven years in tapes.
让我们来模拟一下这个场景，假设对象在DASD中存储6个月，在外部存储中存储3年，在磁带中存储7年。
This scenario uses Version 8.2 client (c1) and three databases (dbase1, dbase2, dbase3, which belong to instances inst1, inst2, inst3, respectively).
该场景使用 V8.2客户机（c1）和三个数据库（dbase1、dbase2 和dbase3，分别属于实例inst1、inst2和 inst3）。
This merge scenario is the reverse of the operation usually associated with the classic parallel development three-way merge pattern.
该合并方案是倒转通常与经典的平行开发三方合并模式相关联的操作。
This three-part article series answers that question by walking you through an end-to-end development scenario.
这个分三部分的文章系列将带领您研究一个端到端开发场景，以此回答这个问题。
In this scenario, the three-guest configuration has the same number of JVMs as the six-guest configuration.
在这种情况下，三客户机的配置与六客户机的配置具有相同的jvm数。
Although the integration points were described as three separate scenarios, a typical problem-isolation scenario would seamlessly blend all these scenarios together in various combinations.
尽管这里通过三个单独的场景介绍集成点，但是典型的问题隔离过程往往以各种组合方式把这三个场景无缝地融合在一起。
Although the integration points were described as three separate scenarios, a typical problem-isolation scenario would seamlessly blend all these scenarios together in various combinations.
尽管这里通过三个单独的场景介绍集成点，但是典型的问题隔离过程往往以各种组合方式把这三个场景无缝地融合在一起。
应用推荐