You can then define and start multiple instances of this queue manager on different machines, with one active instance and one standby instance.
之后您可以在不同机器上定义并启动此队列管理器的多个实例，包括一个活动实例和一个备用实例。
The second is to stop both the active and the standby instances of the queue manager.
第二种方法是同时停止队列管理器的活动和备用实例。
Should the queue manager be started using the STRMQM command (without the -x option), the instances of the queue manager configured on other machines are prevented from starting as standby instances.
如果使用strmqm命令(不带- x选项)启动队列管理器，那么在其他机器上配置的队列管理器实例将不能作为备用实例启动。
Start the standby instance of queue manager on Server 2.
启动Server2中队列管理器的备用实例。
Each broker instance is embedded into a WebSphere MQ service so that, when the queue manager switches over to the standby system, the broker is automatically started on the standby node.
每个代理实例都嵌入到一个WebSphereMQ服务中，以便当队列管理器切换到备用系统时，代理自动在备用节点上启动。
For example, the IP address for your standby Content Manager, version 10.3.0.1, may be mapped to the hostname cm_standby.
例如，备用ContentManager,version10.3.0.1的IP地址可能映射到主机名cm_standby。
Each broker instance can be started as an MQ service, so that when the queue manager fails over to the standby, the broker is automatically started.
每个代理实例可以启动为一个MQ服务，从而在队列管理器故障转移到备份代理时自动启动该代理。
The systems described here have included one broker or queue manager instance that is active and one standby.
这里描述的系统包含一个活动代理或队列管理器实例和一个备用实例。
If an attempt is made to start another instance, the user would receive the response that the queue manager instance is not permitted to run as a standby.
如果用户企图启动另一个实例，将收到一个响应，表明该队列管理器实例不允许作为备用实例运行。
You should see the results shown in Listings 27 and 28, indicating that the queue manager and broker instances there are the standby instances.
您应该能看到清单27和28中显示的结果，表明那里的队列管理器和代理实例是备用实例。
Only two queue manager instances can run at the same time: an active instance and a standby.
只有以下两个队列管理器实例可以同时运行：活动实例和备用实例。
The exclusive access lock on the queue manager data and logs is released, and the standby queue manager takes over.
队列管理器数据和日志上的独占访问权锁释放，备用队列管理器接管。
Automatic reconnect for JMS applications to a standby gateway queue manager when an active queue manager fails or becomes unavailable.
当某个活动队列管理器失败或变得不可用时，JMS应用程序会自动重新连接到备用网关队列管理器。
In another window on Server 1, end the queue manager with the -is option so that it will switch over to a standby queue manager.
在Server1的另一个窗口中，使用- is选项结束队列管理器，这样它将切换到备用队列管理器。
Next, you will need to provide connection details for the active and standby queue managers, and instruct WebSphere MQ Explorer to auto-reconnect to the active queue manager in case of a failover.
下面，您需要提供活动和备用队列管理器的连接细节，指示WebSphereMQExplorer在故障转移时自动重新连接活动队列管理器。
Starting the deployment manager on the standby machine.
在备份节点上启动部署管理器。
Queue manager: Standby instance created.
队列管理器：创建的备用实例。
When a queue manager goes down for any reason, this will cause the associated broker to fail; Message broker will then switch to the standby instance.
当一个队列管理器由于某种原因而出现故障时，将会导致关联代理失败；MessageBroker然后将切换到备用实例。
If you issue the command endmqm IBMESBQM on the active instance of the queue manager — without, as you will note, the -s option — you will stop both the active and the standby instances.
如果在队列管理器的活动实例上执行endmqmIBMESBQM命令—您将注意到，没有-s选项—将同时停止活动和备用实例。
Select Permit a standby instance, click Finish, and the queue manager will be created.
选择Permita standbyinstance并单击Finish来创建队列管理器。
Select Permit a standby instance, click Finish, and the queue manager will be created.
选择Permita standbyinstance并单击Finish来创建队列管理器。
应用推荐