编辑静态路由文件。
Generate the static routing file.
生成静态路由文件。
Propagate the static routing file.
传播静态路由文件。
There is no need to manually edit any routing file.
不需要手动编辑任何路由文件。
Keep the static routing file in sync with topology changes.
使静态路由文件与拓扑结构修改保持同步。
As with the classic proxy server, there is no need to manually edit any static routing file.
和典型的代理服务器一样，不需要手动地编辑任何静态路由文件。
Presently, the generated plug-in routing file contains only the ODRs that are up and running at the time of generation.
目前，生成的插件路由文件只包含在生成后配置并运行的ODR。
With the classic proxy server, you can configure the plug-in routing file generation and distribution Settings at the cluster level.
对于典型的代理服务器，您可以在集群的级别配置插件路由文件的生成和分发设置。
Using the RouteToLabel node is one method of routing file records through a message flow based on message content. In this example, the FileInput node reads an input file as shown.
使用RouteToLabel节点是通过消息流基于消息内容路由文件记录的方法之一。
With a DMZ secure proxy server in high security mode (the default), you are required to supply a file that contains static routing information to the secure proxy server.
对 DMZ安全代理服务器使用高级安全模式（默认设置），您需要为安全代理服务器提供一个包含静态路由信息的文件。
At startup, the on demand configuration code inside the secure proxy reads the static route file and builds the in-memory routing data.
在启动后，安全代理内部的随需应变配置代码将读取静态路由文件并构建内存路由数据。
This takes care of routing requests to the appropriate file system.
它负责将请求路由到合适的文件系统。
Routing within the message flow based on file content.
消息流中基于文件内容的路由。
You have two options, the first is to write a pre-processing exit for the File Directory Receiver that will set the routing information required by Partner Gateway.
您有两种选择，一种选择是为FileDirectoryReceiver编写一个预处理的exit，它将设置PartnerGateway所需要的路由信息。
Listing 11: Sample routing properties file.
清单11：样本路由属性文件。
Understanding how the ODR processes requests is useful in understanding how to analyze the target.xml file to resolve routing problems.
理解ODR如何处理请求有助于理解如何分析target.xml文件，以便解决路由问题。
The HTTP plug-in router will make routing decisions based on the client request (URL) and the information contained in the plugin-cfg.xml file.
HTTP插件路由器将根据客户机请求（URL）和plugin-cfg.xml 文件中包含的信息作出路由决策。
Script outputs the current routing information (target.xml file) and an indication of whether or not requests are being queued by the Autonomic request Flow Manager (ARFM).
jacl脚本输出当前路由信息(target . xml文件)，并标明请求是否正在通过AutonomicRequestFlowManager (ARFM)排队。
WebSphere Virtual Enterprise maintains the data needed to make routing decisions in memory, unlike a web server which USES a static file.
WebSphereVirtualEnterprise在内存中包含进行路由决策所需要的数据，这与web服务器不同，后者使用一个静态文件。
The target.xml file is a snapshot of the state of the cell, and includes information about server state, application state and routing information.
xml文件是单元状态的快照，包括服务器状态、应用程序状态和路由信息。
But first, update the web.xml file to include the RestServlet from Apache Wink that is responsible for routing the requests to the correct resources.
但首先，更新web . xml文件并从ApacheWink将RestServlet包含进来，它负责将请求路由到正确的资源。
The routing handler USES a properties file to map service level values to target service endpoints.
路由处理器使用一个属性文件来映射服务级别值到目标服务端点。
The routing handler USES a properties file to map subscriber common names to target service endpoints.
路由处理程序使用一个属性文件来将订阅公共名称映射到目标服务端点。
The latter file is a transient file and typically should not be used for actual routing.
后者是一个临时文件，通常不应用于实际的路由。
Documents are part of the framework's standard command routing and consequently receive commands from standard user-interface components (such as the File Save menu item).
文档是一个框架标准命令路由，因此从标准用户界面组件(如文件保存菜单项)接受命令。
This is commonly read by a daemon (klogd or rsyslogd) that consumes the messages and passes them to rsyslog for routing to the appropriate log file (based on its configuration).
这个读取操作通常是由一个守护程序(klogd或rsyslogd)实现的，它会处理这些消息，然后将它们传递给rsyslog，以便(基于它的配置)转发到正确的日志文件中。
However this supposition does not come into existence in such problems as domain routing, IP Multicast, P2P file sharing etc.
对于域间路由、IP多播、P 2 P文件共享等问题，这个假设并不成立。
However this supposition does not come into existence in such problems as domain routing, IP Multicast, P2P file sharing etc.
对于域间路由、IP多播、P 2 P文件共享等问题，这个假设并不成立。
应用推荐