CA SystemEDGE User Guide › Concepts › AIM Architecture

AIM Architecture

Application Insight Modules (AIMs) extend the SystemEDGE agent capabilities to application-specific monitoring or provide specialized monitoring capabilities that do not exist in the base agent. A wide variety of AIMs are available with different architectures, but the following conventions apply to all AIMs:

• Typically, AIMs are automatically loaded after installation. The AIM installation program creates the enable_req file in the directory SystemEDGE/plugins/plugin-name as the last step of the installation program. This helps ensure that the AIM product files are available when the SystemEDGE agent discovers the enable_req file.
  Alternatively, you can enter the sysedge_plugin <plugin name> parameter in the sysedge.cf file if the SystemEDGE agent is in an unmanaged mode. After the AIMs are loaded successfully, the SystemEDGE agent creates the enable_ack file.

  Note: Write-access must be specified during CA Virtual Assurance installation.

• SystemEDGE can load AIMs with a warm start, but the agent requires a full restart to remove previously loaded AIMs.
• Each SystemEDGE Version 5.0 AIM has its own MIB that the core agent supports.
• Each AIM can have its own configuration file in which you can enter AIM configuration instructions.

For more information about using AIMs, see the documentation specific to AIM.