Hi All,
Just installed CMDB Build over the weekend and really impressed with the possibilities it offers. The flexibility it offers is incredible.
I have read through the technical manual and it is not clear to me how to create a separate instance for testing. By that I mean use the same Tomcat and postgres database server but have a completely separate test instance/database I can access with a slightly different URL e.g http://host:8080/cmdbuildTEST. There are references in your forums and manuals to other instances but it is just not clear how to set one up. Would really appreciate advice on this. Perhaps it could be added to future versions of the tehcnical manual as well?
Finally and this is a more general question has anyone modeled cloud/virtualised infrastructure with this. For example do people create a separate class ie. CloudServer or do they just add attributes to an existing physical server class that include cloud/virtualisation attributes?
Hoping to benefit from someone's experience with this scenario.
Regards
Phil
To install more CMDBuild instances using the same Tomcat and Postgres is enough to create multiple webapps in Tomcat and multiple databases in Postgres, and configure each instance as described in the manual.
The URL to access each CMDBuild instance from the browser will depend on the name of the webapp.
There are several ways to model cloud / virtualised infrastructure.
For example, if you created a hierarchy of classes and subclasses as Asset => Hardware => Server you can create a new subclass VirtualServer at the same level of Server, hiding the attributes inherited from Asset and Hardware that are not applicable (Manufacturer, Location, etc.). Then you can create a class Cluster related to Server and VirtualServer.
Or you can use a solution quite different, considering the Server as only a "piece of iron" and introducing an "Host" class modeling the computing environment (virtual and non-virtual), connected to Server and Clusters.
Or you can choose another different model that best suits your needs.
CMDBuild Team
Thanks for your advice. For anyone reading this I had a few troubles dealing with the auto deploying tomcat WAR file ie CMDbuild.war. I could not run duplicate renamed ones in the root of webapps.
So the course of action I followed was to UNZIP the WAR file (a WAR file is a zipped archive essentially) with 7zip then rename the unzipped folder as "CMDBuildTEST" (or whatever) and copy into the root of webapps. Reachable via Http://localhost:8080/CMDBuildTEST/. And going through the configuration creating a new database etc.
Anyway my follow-up question is what do you mean by "class CLUSTER". I understand the class concept of course and I think I understand what your driving at but there is no reference in the manuals to
clustering
classes so could you spell that out more explicitly?
Phil
Previously Tecnoteca wrote:
To install more CMDBuild instances using the same Tomcat and Postgres is enough to create multiple webapps in Tomcat and multiple databases in Postgres, and configure each instance as described in the manual.
The URL to access each CMDBuild instance from the browser will depend on the name of the webapp.
There are several ways to model cloud / virtualised infrastructure.
For example, if you created a hierarchy of classes and subclasses as Asset => Hardware => Server you can create a new subclass VirtualServer at the same level of Server, hiding the attributes inherited from Asset and Hardware that are not applicable (Manufacturer, Location, etc.). Then you can create a class Cluster related to Server and VirtualServer.
Or you can use a solution quite different, considering the Server as only a "piece of iron" and introducing an "Host" class modeling the computing environment (virtual and non-virtual), connected to Server and Clusters.
Or you can choose another different model that best suits your needs.
CMDBuild Team
The class “clusters” that I mentioned is a possible “applicative” class that can be used or not, according to the needs of each CMDBuild administrator.
The same thing goes for classes Rack, Host, Server, License, Network device, Supplier, Contract, Application, SLA, etc.
All of these are not predefined system classes, but are classes that each user can, if he wants, enter in his own data model.
It depends on how he wants to model the entities to manage in his asset management system.
Therefore they are not described and can not be described in the CMDBuild manuals.
CMDBuild Team