The data modification stored procedure will run the "Trigger.bat" utility on the database server which in turn triggers the import deployment agent in the target environment.
数据修改存储过程将在数据库服务器上运行“Trigger . bat”实用工具，这又会在目标环境中触发导入部署代理。
There should be four tasks, one to export the deployment, one to execute the batch file, and then one to E-mail notification for either success or failure of the agent or any of the previous tasks.
这里应该有四个任务，一个导出部署，一个执行批文件，还有一个对代理或者以前的任何任务的成败进行电子邮件通知。
Actions invoked through these views are communicated by the deployment manager to the node agent of the corresponding application server node.
部署管理器将通过这些视图调用的操作传达至相应应用程序服务器节点的节点代理。
Of course, you're not going to let me off without a discussion of the functions that reside solely in the node agent and deployment manager, and I don't blame you, so, let's get to it.
当然，如果我不讨论这些单独存在于节点代理和部署管理器的功能，您是不会轻易放过我的，我不会怪您，那么让我们来看看这些功能吧。
When transferring a job from the job manager to the administrative agent or the deployment manager, security information about the job submitter is also transferred.
将作业从作业管理器传输到管理代理或部署管理器时，也会传输关于作业提交者的安全信息。
After a base node is removed from a deployment manager federation, it can be registered with an administrative agent.
从部署管理器联合中删除某个基本节点之后，可以将该节点注册到管理代理。
In the same way, all notifications in the node agent are sent to the deployment manager.
同样，也将节点代理中的所有通知发送到部署管理器。
The polling cycle time is configurable at the administrative agent or the deployment manager.
可在管理代理或部署管理器上配置轮询周期时间。
When a node is federated with a deployment manager, the base node's configuration is first backed up, then replaced with a new configuration containing the node agent.
当某个节点与部署管理器联合时，首先备份基本节点的配置，然后替换为包含节点代理的新配置。
As a result, once a connection has been made, all running node agent JVMs have a cache of the IP address for the original server that the deployment manager was running on.
因此，一旦建立起一个连接后，所有运行的节点代理JVM都缓存了运行部署管理器的原始服务器的IP地址。
This can be a JSR-88 compliant deployment tool or even an automated system-management agent.
这个工具可以是一个兼容JSR-88 的部署工具，甚至可以是一个自动化的系统托管代理。
The deployment architecture of the agent is shown in Figure 2.
图 2 中显示了抽样代理的部署架构。
In a Network Deployment installation however, all notifications from the application server are also sent to the node agent on the same machine.
而在Net workDeployment安装中，还将来自应用程序服务器的所有通知发送到同一台机器上的节点代理。
On the other hand, if you are running into the above issues, you can create the new administrative agent or job manager topologies based on your existing base or Network Deployment topologies.
另一方面，如果您遇到上述问题，则可以根据您的现有基本拓扑或Network Deployment拓扑创建新的管理代理拓扑或作业管理器拓扑。
If no node has been registered, the administrative agent console login page will appear, similar to that of the base or Network Deployment environment.
如果尚未注册节点，则会显示管理代理控制台登录页，该页面与基本或Network Deployment环境的登录页类似。
The same is true of the administrative agent and its registered base nodes, and also any job manager or Network Deployment cells in the topology.
管理代理及其注册基本节点，以及拓扑中的任何作业管理器或NetworkDeployment单元也是如此。
Furthermore, there are differences in how nodes are removed from a deployment manager cell and how they are unregistered from an administrative agent.
而且，从部署管理器单元移除节点的方式与从管理代理取消注册节点的方式有所不同。
Using the Local OS user registry requires the node agent, the deployment manager, and the application server process to run as root.
要使用LocalOS用户注册表，需要将节点代理、部署管理器和应用程序服务器进程作为根运行。
The Trigger.bat utility will trigger the required “Event Studio Import Agent” in the target environment that will run the export and import of the deployment.
bat实用工具将触发目标环境中需要的 “EventStudioImportAgent”（它将运行部署的导出和导入）。
The recipients list can include IBM Cognos administrators and application architects who would run this agent as and when required for deployment.
接收人列表可以包含IBMCognos管理员和应用程序设计人员，他们在部署需要时会运行这个代理。
Once the VM is fully instantiated, the Workload Deployer-specific agent residing inside the VM initiates the action to configure the VM for the role it will play in this application deployment.
在完全完成VM的实例化之后，位于VM中的特定于WorkloadDeployer的代理开始行动，将VM配置为它在该应用程序部署中将要扮演的角色。
If you receive this error message when starting the WebSphere Application Server deployment manager or node agent.
如果您在启动WebSphereApplicationServer部署管理器或节点代理时接收到以下错误消息。
In this context, "WebSphere application server" includes all WebSphere application server components, including deployment manager, node agent, application server, and so on.
在这个上下文中，WebSphereApplicationServer包括所有的WebSphere Application Server组件，包括部署管理器、节点代理、应用服务器，等等。
The recipients list can include IBM Cognos administrators and application architects who would run this agent when required for deployment.
接收人列表可以包含IBMCognos管理员和应用程序设计人员，他们在部署需要时会运行这个代理。
This approach provides flexibility for the IBM Cognos architects to perform the code deployment themselves by just running the Event Studio agent in the source IBM Cognos environment.
通过只在源ibmCognos环境中运行EventStudio代理，这种方法为IBM Cognos设计人员自己执行代码部署提供了灵活性。
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.
在Linux和UNIX 上，您很可能知道如何使用 startManager.sh 和startNode.sh 脚本来启动部署管理器和节点代理。
A device management agent to enable the remote auditing of the client as well as the over-the-air deployment of new or updated applications.
设备管理代理，用于启用客户机的远程审计和以空中下载(over -the - air)方式部署新的或已更新的应用程序。
In Version 6.0, when you federate an application server node into a deployment manager cell, the deployment manager instantiates the node agent server process on the application server node.
在Version 6.0中，当您将某个应用程序服务器节点联合到部署管理器计算单元中时，部署管理器会在该应用程序服务器节点上实例化节点代理服务器进程。
In Version 6.1, when you federate an application server node into a deployment manager cell, the deployment manager instantiates the node agent server process on the application server node.
在Version 6.1中，当您将某个应用程序服务器节点联合到部署管理器计算单元中时，部署管理器会在该应用程序服务器节点上实例化节点代理服务器进程。
The Event Studio agent is designed in the source environment where the deployment is to be taken.
EventStudio代理被设计在发生部署的源环境中。
应用推荐