No switchover will happen upon execution of this command; it will just bring down the running broker.
执行这个命令时不会发生切换，只会停止正在运行的代理。
The Statistics views each provide two screens that let you see information about a running broker that has been collected from a local or remote broker instance.
每个Statistics视图提供两个界面，支持您查看从本地或远程实例中收集来的关于正在运行的代理的信息。
With a default configuration in place a sample can be imported to the WebSphere Message broker Toolkit, deployed to a running broker, and executed within a few minutes without doing any coding.
在具备缺省配置之后，可以将一个示例导入WebSphereMessageBroker工具包，部署到一个正在运行的代理并在数分钟内执行，而且无需进行任何编码。
Subsequent sections will explain what happens if the broker is not running when one of these timer events is supposed to happen.
后继部分将说明，当这些计时器事件其中的一个要发生时，如果代理未运行，将会发生何种情况。
First, check that the FTP server is running and that you have sufficient authority using a standard interface outside of the broker.
首先，在代理之外使用标准接口检查FTP服务器是否在运行，并且您拥有足够的权限。
Message flow statistics: Show message throughput rates, CPU use, and elapsed times of message flows running in the broker.
消息流统计：显示消息吞吐率、CPU使用率和在代理上运行的消息流的实耗时间。
Since the queue manager is already running, it is necessary to start the broker manually the first time.
由于队列管理器已经运行，所以第一次需要手动启动代理。
For example, Message Broker might take data from SAP, and using MQ, send it to an enterprise application running on CICS.
例如，MessageBroker可能使用MQ从SAP取得数据，并将数据发送到运行在CICS上的企业应用程序。
The Message Broker provides the publish and subscribe features, and it has to be running in addition to queue manager.
除了队列管理器外，提供发布和订阅特性的MessageBroker也必须运行。
The diagram shows the JMSInput and JMSOutput nodes running in a message flow that will be hosted in a broker.
该图表显示了在将宿主于代理的消息流中运行的JMSInput和JMSOutput节点。
On the standby node, you will find following broker processes running.
在备用节点上，您将发现以下代理进程正在运行。
Execute the commands below on the server, where the corresponding active instances of the multi-instance broker are running. The execution group IBMESBEG will be created.
在服务器上执行下面的命令，对应的多实例代理主动实例在服务器上运行。
Additionally, to connect and publish messages with the example MQTT client, a running installation of Lotus Expeditor micro broker is required.
此外，为了用示例MQTT客户机连接和发布消息，还要安装和运行LotusExpeditormicrobroker。
The active instance of the multi-instance broker will be instantiated on the server, where the corresponding multi-instance queue manager will be running in active state.
多实例代理的主动实例将在服务器上实例化，而服务器上的对应多实例队列管理器将以主动状态运行。
The illustration shows that the broker is running on the same machine as the client application since the local loopback address is used.
演示表明代理和客户端应用程序运行在同一台机器上，这是因为使用了本地回环地址。
Before conducting the tests, ensure that both the default execution group on the MB7BROKER broker and the LDAP server instance are running.
在执行测试之前，请确保MB7BROKER代理上的默认执行组和LDAP服务器实例正常运行。
Deploy the broker archive file DynamicWSUpdate.bar to your runtime broker, and then close the toolkit before running messages through the message flow.
将代理存档文件dynamicwsupdate . bar部署到运行时代理，然后在通过消息流运行消息前关闭工具包。
In order to start this logic running on an execution group, message flows are compiled and combined with any related files into a zipped package called a broker archive (BAR) file.
为了开始在某个执行组上运行此逻辑，需要编译消息流并将其与任何相关文件一起组合到称为代理存档(broker archive, BAR)文件的压缩包中。
Start the broker server by running the broker.start.bat file, which is in the following directory: Program Files \ IBM \ Rational \ DOORS \ 9.2 \ interfaces \ festival-win32.
通过运行broker .start . bat文件来启动broker服务器，它位于以下的目录之中：ProgramFiles \IBM \Rational \DOORS \ 9.2 \interfaces \ festival - win32。
If you were talking to your broker if you go really old days, you'd send a boy running over to your broker.
如果是很久以前，你想向股票经纪委托，你会派一个男孩跑去捎口信。
If you were talking to your broker if you go really old days, you'd send a boy running over to your broker.
如果是很久以前，你想向股票经纪委托，你会派一个男孩跑去捎口信。
应用推荐