imod

These events are defined whenever a system is defined in IMOD .

每当在IMOD中定义系统时，就会定义这些事件。

Three keys to establishing application-centric management in IMOD

在IMOD中实现以应用程序为中心的管理的三个关键步骤

The IMOD software itself is designed to interface with any cloud platform and is currently integrated with five different clouds .

IMOD软件本身设计成能够与任何云平台交互，当前与五种不同的云集成。

In IMOD , servers are organized into groups .

在IMOD中，服务器被组织为组。

These code examples come from a real-world experience in developing and deploying Kaavo IMOD .

这些代码示例源于开发和部署KaavoIMOD的实际经验。

The rationale for using two separate tiers is that IMOD 's N-Tier engine allows us to define deployment order among tiers .

能够使用两个单独的层是因为IMOD的n层引擎允许定义层的部署次序。

With IMOD , this is done using different graphical wizards ; a " hands-on ," manual implementation is beyond the scope of this article .

在IMOD中，可以使用不同的图形化向导实现转换；手工实现超出了本文的范围。

By making a web service call ( which allows users to programmatically interact with IMOD via SOAP using a document / literal wrapped style ) .

通过发出web服务调用（这允许用户通过使用document/literal包装风格的SOAP程序化地与IMOD交互）。

In the implementation phase of Kaavo IMOD , all you would have to do is input these actions to graphical wizards .

在KaavoIMOD的实现阶段，只需把这些动作输入图形化向导即可。

The first step towards an application-centric management approach to managing applications is defining the application , so let 's define the components for IMOD and what each does .

实现以应用程序为中心的管理的第一步是定义应用程序。我们先讨论IMOD的组件以及每个组件的作用。

IMOD is a framework based on patent-pending technology devised by Kaavo that automates the deployment and runtime management of any complex multi-server , multi-tier application or workloads .

IMOD框架基于Kaavo发明的正在申请专利的技术，可以对任何复杂的多服务器、多层应用程序或工作负载的部署和运行时管理进行自动化。