使用可扩展节点部件创建一个定制的模式。
鉴于无限的定制需求，WPSH引入了可扩展节点部件。
Acknowledging the limitless possibilities for customization the WPSH introduced the Extendable nodes part.
详细介绍扩展节点的配置方法和主节点的软件设计方法。
This paper detailedly introduces the expander node configuration method and the master node software design method.
如果希望在可扩展节点部件之间交换值，就需要由用户处理连接。
If you want to exchange values between Extendable nodes parts, the wiring will need to be handled by the user.
对于需要部署管理器主机名的可扩展节点部件的任何脚本包，输入以下语法。
For any script package with an Extendable Nodes part which requires the Deployment Manager hostname, enter the following syntax.
在此示例中，我们创建一个包含可扩展节点部件的定制模式，从而实现此拓扑的基础。
In this example, we create a custom pattern with the Extendable nodes part to achieve the foundation for the topology.
例如，模块可以使用评论或评级加强现有的节点，或者通过扩展节点以全新的形式管理和显示内容，比如视频录制。
For example, a module can augment an existing node with comments or ratings or extend a node to manage and display an entirely new form of content, such as a video reel.
在模式中添加的第一个可扩展节点部件(图6所示的模式编辑器视图中最右边的部件)上需要这个脚本包。
This script package is required on the first Extendable nodes part added to the pattern (the part to the far right in the pattern editor view in Figure 6).
部署在模式中时，可扩展节点部件创建一个虚拟机实例，其中只有WebSphereProcessserver二进制代码。
When deployed in a pattern, the Extendable nodes part creates a virtual machine instance where only the WebSphere Process Server binaries exist.
从右到左，可扩展节点部件将分别变成流程服务器部署管理器、包含代理服务器的定制节点和包含流程服务器配置的定制节点。
From right to left respectively, the Extendable nodes parts become the process server Deployment Manager, Custom node with Proxy server, and Custom node with process server configuration.
给出了一个包含有向回路的与或图的求解算法，以及如何确定被扩展节点的祖先节点的优先数，并通过优先数有效地选取祖先节点的方法也在本文中给出。
Methods for determining the ancestor nodes priority number of the expanded node and selecting effectively the ancestor nodes by means of the priority number are also given.
您可以扩展这一模式，以创建已连节点的整个组。
You can extend this pattern to create an entire group of connected nodes.
接下来，将任何扩展数据应用于这个节点对象。
您将会看到引用属性在扩展任意节点时起到多么重要的作用。
You'll see how referencing property plays an important role when you expand any node.
一个评级模块能扩展任意节点，使之包含等级。
处理节点集的扩展函数编写起来比那些处理简单值的函数更要求技巧，但不是非常困难。
Extension functions that operate on node-sets are trickier to write than ones that operate on simple values, but not excessively so.
在转换或扩展之前，工作区首先将节点升级到版本6。
A workaround is to first upgrade the node to V6 before the conversion or expansion.
同一节点拥有标准和扩展值。
另一方面，不允许XSLT处理程序识别样式表注释或者文本节点中的扩展点。
On the other hand, an XSLT processor is not allowed to recognize extension points in any comment or text node of the stylesheet.
向下扩展就像退回操作，其中没有将主节点置于在线的任务。
Scaling down is like a failback operation without the task of bringing the primary node up.
扩展链接节点以显示罗列在WSIL中的服务。
Expand the link node to display the services listed in the WSIL.
其间，一个模块扩展了所有节点，使之包含评级数据，而另一个模块扩展了所有节点使之包含注释。
Meanwhile, one module extends all nodes to include rating data, and another module extends all nodes to include commentary.
对于此类情况，可以使用ESQL功能扩展映射节点。
In cases such as this it is possible to extend the mapping node using ESQL functions.
现在已经创建了树，您可以扩展获取被请求节点数据的节点了。
Now that the tree is created, you can expand a node that fetches data for the requested node.
迁移不过就是永不退回的故障转移，扩展是永远不将主节点置于离线的故障转移。
Migration is simply a failover that never fails back, and scaling up is a failover in which the primary node never goes offline.
当第三次使用内包节点集时，将在扩展存储它，以内存换取处理时间。
When an intensional node-set is used for the third time, it is stored extensionally, trading memory for processing time.
尽管RDBMS为在传统的客户端-服务器架构中存储数据提供了一个坚实的基础，但它不能轻松地(或便宜地)扩展到多个节点。
While the RDBMS provides a rock-solid foundation for storing data in traditional client-server architectures, it doesn't easily (or cheaply) scale to multiple nodes.
我们将演示如何在脱机情况下划分数据库，以及如何将数据库从ese迁移到DPF逻辑节点(纵向扩展)环境。
We demonstrate how to partition tables and migrate the database from ESE to a DPF logical node (scaling up) environment, offline.
Drupal内容模块通常扩展标准Drupal节点，将补充字段存储在一个单独的表中。
A Drupal content module typically extends the standard Drupal node with supplemental fields stored in a separate table.
WebSphereVirtualEnterprise将自动把应用程序部署到新节点，但是不会对扩展的EAR文件做任何手动修改。
WebSphere Virtual Enterprise would automatically deploy the application to the new node, but any manual changes to the expanded EAR would not be made.
应用推荐