JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Solaris System Management Agent Developer's Guide
search filter icon
search icon

Document Information

Preface

1.  Introduction to the System Management Agent

2.  Creating Modules

About Modules

Overview of Creating Modules

Defining a MIB

MIB File Names

Setting MIB Environment Variables

Generating Code Templates

Modifying Code Templates

Configuring the Module

Delivering the Module

Namespace Issues

Avoiding Namespace Collisions

Module Names

Library Names

3.  Data Modeling

4.  Storing Module Data

5.  Implementing Alarms

6.  Deploying Modules

7.  Multiple Instance Modules

8.  Long-Running Data Collection

9.  Entity MIB

10.  Migration of Solstice Enterprise Agents to the System Management Agent

A.  SMA Resources

B.  MIBs Implemented in SMA

Glossary

Index

About Modules

The term module as used in this manual has two closely related meanings. Module refers generically to the “container” of the new pieces of management data that the developer needs to inform the agent about. In this sense, a module is an abstract concept.

However, an abstract module must be represented as a shared object file, which runs on a managed system. The shared object file, or the associated program, is often referred to as a module. Therefore, a module can be defined as a C program that works with the SMA to manage additional resources.

All modules communicate through the API library functions. The API functions are used whether the modules are compiled in the agent, or loaded dynamically, or running in a separate subagent.