CMDBuild Forum

Re: fill cmdbuild IT asstet attributes using snmp

Old Versions
#1

Hi,

I'm trying to add auto discovery to cmdbuild (something like ManageEngine Asset Manager tool), which by getting system ip, automaticaly fills its related asset entries using snmp agents.

what is the best idea for doing this? i wanna get snmp specific oids for each field in asset table which is statically pre-configured and then put its collected data in cmdbuild database, but now  what if i use a seperate database and synch it with cmdbuild by cmdbuild connectors?

 

than

#2

I suggest you take a look at CMDBuild Connectors Manual:
http://www.cmdbuild.org/en/documentazione/manuali/connectors-manual
CMDBuild Team

#3
Thanks for your reply.
I almost read the document and figured out that the better way is to write a mini-snmp monitoring server to fetch required data(like os type, ram capacity and ...) from network nodes and directly insert them on cmdbuild database, cause i am writing the discovery module by myself and it does not have a db yet so why using a redundant db and synching that with cmdbuild  through passive connectors?!
Previously Tecnoteca wrote:
I suggest you take a look at CMDBuild Connectors Manual:
http://www.cmdbuild.org/en/documentazione/manuali/connectors-manual
CMDBuild Team

 

#4

We suggest you use SOAP or REST web services, rather than writing directly in the CMDBuild database.
CMDBuild Team
 

#5
since by taking your suggestion i should be dependent to a another layer and it's crashes and document, could you please exlpain to me why should i use cmdbuild rest and soap instead of clean hibernate insert?
i assume that all of cmdbuild actions took place through database triggers, anything happening beyond web services that i missed?
Previously Tecnoteca wrote:
We suggest you use SOAP or REST web services, rather than writing directly in the CMDBuild database.
CMDBuild Team
 

 

#6

Because, as in all software projects, we guarantee the backward compatibility of the CMDBuild API, not of the physical structure of the CMDBuild database.
And any changes that we will make to the physical structure of the database can prevent the proper functioning of your connector.
CMDBuild Team

 

 

#7
OK,
You are right!
Thanks a lot.
 
Previously Tecnoteca wrote:
Because, as in all software projects, we guarantee the backward compatibility of the CMDBuild API, not of the physical structure of the CMDBuild database.
And any changes that we will make to the physical structure of the database can prevent the proper functioning of your connector.
CMDBuild Team