Users
:: architecture
:: features list
:: installing openrsm
:: documentation
:: videos
:: f.a.q.
Downloads
:: sourceforge
:: patches table
Functionality
:: custom jobs
:: delivery
:: dynamic groups
:: dicovery
:: assets management
:: remote control
:: security
Developers
:: releases
:: code revisions
:: compilation
:: com and ports
:: code f.a.q.
:: requests and ideas
:: under development
OpenRSM4J
:: features
:: documentation
:: code revisions
:: todo
Other
:: funding
:: publications
:: stats, page hits, misc
:: links
:: about OpenRSM
|
| |
Architecutre
OpenRSM is composed by three components, the OpenRSM server, the OpenRSM user console and the agent. The console accepts input from the user and conveys it to the server in the form of commands. The server is responsible for action coordination and communication. The agent is a passive component that residing on the managed stations. It accepts commands from the server and conveys them to the operating system of the managed host for execution.
The server comprises of the following components :
:: network monitoring
:: asset management and inventory
:: remote control
:: software delivery
The above components have not been built from scratch. Suitable open source tools have been used and extended according to needs. Network monitoring was intially based on the NINO network management system, a full featured network management platfrom based on perl technology. The inventory subsystem was based on the Winventory assets management web application, now known as OpenAudit. The remote control technology used is UltraVNC , the well-known remote desktop tool. Software delivery has been based on win-get. The primary goal of OpenRSM has been to integrate these tools properly so that it can deliver unified systems and network mangement service. This is the role of the OpenRSM server frontend module, which synchronizes all the components by acuiring user requests, scheduling them and dispatching to the proper subystem.
|
|
