Thanks for your prompt reply

Your idea of a new table linked to the 'isys_cats_enclosure_list' looks like a good solution. It could be called something like 'isys_cats_enclosure_pos' and would require the following fields:

isys_cats_enclosure_pos__id
  isys_cats_enclosure_pos__isys_cats_enclosure_list__id
  isys_cats_enclosure_pos__u
  isys_cats_enclosure_pos__isys_obj__id

Btw there is 1 other table linked to 'isys_cats_enclosure_list' called 'isys_pos_gps', could you tell me what is the purpose of this table?

Regards,

Nik

Hi all,

Cheers guys on a fantastic application, I've been looking at it for a couple of weeks now and I'm very impressed with it's functionality.

My question is regarding rack management. The organisation I work for are looking for a CMDB very much like I-doit, but they also need a more visual representation of racks, specifically server location. At the moment it's possible to populate an enclosure with servers/KVM/Power/etc, so you can see what is in the rack, but not where in the rack. For example if I create a 42u enclosure and populate it with a bunch of servers, I would like to know where in the rack they are and what free space is available. Can you tell me if there are any plans to add this kind of functionality in the future?

If not then could you point me at the particular set of tables within the DB that would potentially need modifying to include rack location data? I've generated a DB diagram within MySQLWorkbench, but with 346 tables within the _data DB it's VERY difficult to reverse engineer.

Cheers,

Nik

So how do you then view a list of servers the Application is linked to once a link has been created via Server -> Application/Service -> new -> link object?

You can see the apps linked to each server by clicking on each server, but not the other way around.