| Skip Navigation Links | |
| Exit Print View | |
|
Solaris System Management Agent Developer's Guide |
1. Introduction to the System Management Agent
8. Long-Running Data Collection
10. Migration of Solstice Enterprise Agents to the System Management Agent
Migrating Solstice Enterprise Agent Subagents to SMA
demo_module_12 Code Example for Solstice Enterprise Agents Subagent Migration
Analysis of the demo_module_12 Solstice Enterprise Agents Templates
The general process for implementing a Solstice Enterprise Agents subagent as an SMA module is as follows:
Obtain the MIB that was used to create the Solstice Enterprise Agents subagent.
Make a copy of the MIB. Name the MIB file according to the guidelines in MIB File Names, if necessary.
Modify the copy of the MIB for compatibility with mib2c. Use the SUN-SEA-EXTENSIONS-MIB.txt as a model for modifying the MIB. Pay particular attention to the format of the MODULE-IDENTITY group.
Use the mib2c tool to generate C code for SMA module templates from the modified MIB.
Use the Solstice Enterprise Agents mibcodegen tool to generate C code header and stub files for Solstice Enterprise Agents modules from the original MIB.
Compare the template code that mib2c produced to the template code that mibcodegen produced. Examine the instrumentation code from the Solstice Enterprise Agents subagent to determine what you need for instrumentation in the SMA module.
Modify the SMA templates to use the appropriate functions to implement similar instrumentation code.
The following section uses an example MIB in demo_module_12 to illustrate this migration process.
|