1. Introduction to the System Management Agent
How to Dynamically Load a Module and Restart the Agent
How to Dynamically Load a Module Without Restarting the Agent
Deploying a Module as a Subagent
demo_module_8 Code Example for Implementing a Subagent
8. Long-Running Data Collection
10. Migration of Solstice Enterprise Agents to the System Management Agent
In general, when you are first developing and testing your module, you should dynamically load the module in the master agent. This method reduces the complexity while you work out any problems in the module. When you are ready to deploy a module, you should compile the module in a subagent instead of dynamically loading into the master agent. By using subagents, you can more easily isolate problems in the module.
However, sometimes a subagent is not the optimal deployment method. Use the following criteria to determine when to load a module into a master agent instead of a subagent:
If more than five requests per second are targeted to the module's MIB, you should consider loading the module into the master agent.
If your module queries the SYSTEM group often, and queries the IP branch very rarely, load the module into the master agent.
If your module queries the IP branch of the MIB very often, load the module in the subagent. The IP group of the module MIB is six times more computationally costly compared to the SYSTEM group.
The following table summarizes the primary advantages and disadvantages of dynamically loaded modules and subagents.
Table 6-1 Advantages and Disadvantages of Deployment Methods
|