确保作业管理器和任何部署管理器及管理代理都已启动。
Make sure that the job manager and any deployment managers and administrative agents have been started.
由于队列管理器已经运行，所以第一次需要手动启动代理。
Since the queue manager is already running, it is necessary to start the broker manually the first time.
管理代理还利用了MVS Route命令，因此可以跨同一Sysplex上的不同LPAR启动或停止注册的基本节点。
The administrative agent also takes advantage of the MVS Route command to be able to start or stop registered base nodes across the LPARs of the same sysplex.
具体地说，您可以使用Geronimo部署程序和管理工具部署、启动和管理Active MQ消息代理实例。
Specifically, you can deploy, start, and manage instances of ActiveMQ message brokers using Geronimo deployer and management tools.
Activator：管理代理的生命周期(启动，停止)。
一个NetBoot代理运行于远程服务器上，下载被集中管理的配置，并使用该配置启动本地的Mule实例。
A NetBoot agent sits on a remote server and downloads the centrally managed configuration, booting up the local instance of Mule using that configuration.
当MessageBroker的启动任务运行以后，消息代理将立刻通过自动重启管理注册自己。
When the Message Broker's started task is run, the Message Broker will now register itself with Automatic Restart Management.
使用以下命令启动代理和配置管理器：SimpleJSF 和mqsistart 。
Start your broker and configration manager using the following commands: mqsistart and mqsistart .
在队列管理器上，这转化为要求其上驻留一个代理的每个主机有一个启动队列。
On the queue manager, this translates to a requirement for an initiation queue for each host on which an agent resides.
项目中的最后一步将启动单元中的所有进程，包括部署管理器、节点代理和应用程序服务器集群。
The final step in the project will start all the processes in the cell including the Deployment manager, node agents, and application server cluster.
您将需要重新启动部署管理器、节点代理和您的应用服务器，以便使更改生效。
You will need to restart the deployment manager, node agents, and your application servers for these changes to take affect.
按此方式设置了计算单元后，必须重新启动部署管理器和所有节点代理才能重新读取配置。
Once a cell has been setup in this way, the deployment manager and all node agents must be restarted to re-read the configuration.
每个额外的代理程序都需要一些资源开销，这些开销在启动数据库管理器时会分配给代理程序。
Each additional agent requires some resource overhead that is allocated at the time the database manager is started.
每个代理实例可以启动为一个MQ服务，从而在队列管理器故障转移到备份代理时自动启动该代理。
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.
如果您在启动WebSphereApplicationServer部署管理器或节点代理时接收到以下错误消息。
If you receive this error message when starting the WebSphere Application Server deployment manager or node agent.
当代理释放器命令队列上的输入句柄时，则队列管理器检测到命令队列有一个大于0的深度，从而发出一个新的触发器事件，然后代理重新启动。
As soon as the agent releases the input handle on its command queue, the queue manager detects that the command queue has a depth greater than zero, fires a new trigger event, and the agent restarts.
在Linux和UNIX 上，您很可能知道如何使用 startManager.sh 和 startNode.sh 脚本来启动部署管理器和节点代理。
On Linux and UNIX, you're probably familiar with using the startManager.sh and startNode.sh scripts to start the deployment manager and node agent.
每个代理实例都嵌入到一个WebSphereMQ服务中，以便当队列管理器切换到备用系统时，代理自动在备用节点上启动。
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.
当统计功能启动时，BrokerExplorer在代理队列管理器中为您动态创建一个订阅点来收集快照数据。
When statistics are enabled, the broker Explorer creates a subscription point in the broker's queue manager automatically for you to gather the snapshot data.
当统计功能启动时，BrokerExplorer在代理队列管理器中为您动态创建一个订阅点来收集快照数据。
When statistics are enabled, the broker Explorer creates a subscription point in the broker's queue manager automatically for you to gather the snapshot data.
应用推荐