Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Aperi/architecture"
| Line 37: | Line 37: | ||
=== Integration with IBM Tivoli Monitoring === | === Integration with IBM Tivoli Monitoring === | ||
| − | * [http://www.eclipse.org/aperi/tech/Aperi_Storage_Network_UA.doc | + | * [http://www.eclipse.org/aperi/tech/Aperi_Storage_Network_UA.doc This document (MS Word)] describes how to develop an agent that reports data collected by Aperi to ITM using the ITM Universal Agent framework. |
Revision as of 19:02, 20 March 2007
Contents
This page is a collection of information regarding the architecture of Aperi.
- Aperi Use Cases
- Aperi Technical Roadmap v6
- Aperi Architecture Document
- Aperi System Design (MS Word)
Overview Component Designs
- Database Component Design (MS Word)
- Device Server Component Design (MS Word)
- Disk Manager Component Design (MS Word)
- Fabric Manager Component Design (MS Word)
- JLog (Logging API) User's Guide
R2 Designs
- Aperi Agent Design R2
- Aperi Connector Design R2
- Aperi Data Server Design R2
- Aperi Device Server Design R2
- Material from Tech Face to Face in July 2006
- Aperi Performance Issues using Derby as Repository
R2 API Documentation
- Aperi Data Server R2 Extensibility
- Aperi Device Server R2 Extensibility
- Aperi Database R2 Extensibility
- Aperi Agent R2 Extensibility
R3 Designs
- WEF Events Design (MS Word)
- Narrated Report Viewer UI Design (Power Point ~24M) (HTML - IE required for audio)
Integration with IBM Tivoli Monitoring
- This document (MS Word) describes how to develop an agent that reports data collected by Aperi to ITM using the ITM Universal Agent framework.