Architecture
- Package layout
- Startup and initialization
- Sources, Sinks and Products
- Basic runtime command/message flow
- iPAM runtime architecture
- Internal product structure
Developing new agents
- Input agent, Provider Inteface Module (PIM)
- Middle agent - Handler, Juggler
- Output agent, Datacaster Interface Module ( DIM)
- Daemon
- Wizard
- Servlet (to be written)
- GUI (to be written)
- Agent attributes
- Generic HTML parser
- Product Pools and Memory Size
Developing a plugin
iPAM "plugin"
HTTP requests
Not designed for interactive use by people. They are used by the remote user interface, Bert. Requests exist to subscribe to Backweb channels, examine and control the executive, and perform serveral test/development functions. See list of requests
Java RMI
The daemon "remoteAgentEditor" allows an external Java application to connect to, monitor, and control PAM's operation. The daemon must be declared in the configuration of PAM. It is nonexistent by default.
iPAM Ports
A list of TCP/IP ports used by various agents and services
For further info send questions to cda@mitre.org.