用一个停止节点终止分支并释放数据。
与开始节点不同，停止节点是必需的。
并列执行的分支中的停止节点
这两个任务各与一个停止节点直接相连。
在这种情况下，结束和停止节点可以互换使用。
In this case, you could use end and stop nodes interchangeably.
现在停止节点在您能够容易地看到的地方——在开头。
Now the Stop Node is where you can easily see it, at the beginning.
在早期版本中，缺省的停止节点放在关系图的最右边。
In previous versions, the default Stop Node was placed at the far right of the diagram.
场景5将详细讨论结束和停止节点在语义方面的区别。
Scenario 5 goes into more detail on the difference in the semantics of the end and stop node.
由于目前的模拟要求，我们建议您在模型中使用停止节点。
Given the current requirements of the simulation, we recommend you use the stop node in models.
首先创建启动和停止节点代理和应用服务器进程的两个脚本。
First, create a couple of scripts to start and stop the node agent and the application server processes.
对于每个停止节点，将该停止节点与相应的输出标准相关联。
For each stop node, associate the stop node with the appropriate output criteria.
此外，有时很容易忘记已将缺省停止节点放在了关系图的结尾。
In addition, it was sometimes easy to forget you had the default Stop Node at the end of the diagram.
利用增强的验证，包括为模型的结束路径检测缺失的停止节点。
Leverage enhanced validation including the detection of missing stop nodes for ending paths of a model.
如果询问是否要检查所有路径都有停止节点，您可以接受或拒绝。
If asked to check that all paths have stop nodes, you can accept or decline.
图27中的反模式显示的是在并行分支中使用的停止节点的问题。
The anti-pattern in Figure 27 shows the problem of stop nodes used in parallel branches.
在本地流程或循环中，当导出到FileNet时忽略停止节点。
In local processes or loops, stop nodes are ignored when exporting to FileNet.
不要将网关或活动的所有输入或输出直接连接到开始、结束和停止节点。
Do not connect all inputs or outputs of a gateway or activity directly to start, end, and stop nodes.
在模拟数据流模型时，停止节点显得尤为重要，因为需要用它来释放数据。
The stop node is particularly important when simulating data flow models, because it is required to release the data.
在添加停止节点之前，先重新联接各个分支，以避免出现意外的全局关闭现象。
Rejoin them before adding the stop node to avoid an unintended global shutdown.
务必记住，如果流程带有不在停止节点中结束的路径，则无法正确地模拟该流程。
Keep in mind that processes with paths that do not end in stop nodes will not simulate properly.
结束节点用一个含有十字交叉图案的圆圈表示，停止节点则显示为一个含有黑点的圆圈。
The end node is visualized with a circle containing a cross, while the stop node is visualized with a circle containing a black dot.
注意，我们添加了一个join，以使两个并行的分支重新联接起来，引向某个停止节点。
Note that we added a join to rejoin the two parallel branches so that they can lead to a single stop node.
将未释放到流程输出接口的的活动数据输出连接到某个结束或停止节点，以避免出现悬空输出。
Connect data output of activities that are not released to the process output interface to an end or stop node to avoid dangling outputs.
通常，用户不会察觉到停止节点的全局效果，而只是用它来终止某个流程中的每个单独的分支。
Very often, users are not aware of the global effect of a stop node and use it to end each of the individual branches of a process.
一个可选的方法是将这个输出连接到某个结束或停止节点，以强调该流程的模型已经完全建好了。
An alternative is to connect this output to an end or stop to emphasize that the process has been completely modeled.
在不存在并行的情况下，停止节点与结束节点的效果完全一样，也就是说，它将终止到达它的分支。
Without parallelism, the stop node has exactly the same effect as the end node, i.e., it ends the single branch through which it was reached.
不过，您应当注意到，在模拟运行期间，当某个路径到达了停止节点时，其他并行的路径可能尚未结束。
You should be aware, however, that some parallel paths may not have finished when the stop node is reached during a simulation run.
此处如果换成停止节点将是一个错误的解决方案，因为它会立即终止整个流程，Task4将不会执行。
Using a stop node instead would not be a correct solution, because it would immediately end the whole process and prevent execution of Task 4.
利用一个join节点重新联接并行分支，然后放置一个结束或停止节点，而不是分别结束每个并行分支。
Rejoin parallel branches with a join node and then place a single end or stop node, instead of ending parallel branches individually.
当WASPreUpgrade日志指示命令已成功完成时，请转到V4的管理控制台并停止节点。
When the WASPreUpgrade log indicates that the command has completed successfully, go to the administrative console for V4 and stop the node.
应用推荐