The object ID is very important for the generation of the URIs. By means of the ID you can access objects in an unambiguous way via a link. The name of the variable is
objID. The naming formula structure is:
You can specify a prefix for each object type, which precedes the automatically generated number. You can set the prefix at
Administration → CMDB settings → Object type configuration → [Objekt Object type group] → [Object type] → SYSID prefix. If you do not specify your own prefix, the SYSID will begin with the
SYSID_ prefix. When you set an alternative prefix, the generation of the number changes: The object ID is used instead of the UNIX timestamp.
Hostname is assigned in the
Hostaddress category. For each object any number of host names can be documented, even if it is in many cases assigned unambiguously for each device (for example servers are an example). For each host name – as for As with the IP address (see abouveabove) – , a category entry is generated for each host name.
Is When you also specify the
DNS domain attribute set too per category entry, then this will automatically result results in the Fully Qualified Domain Name (
Just like IP addresses this , the name should be unambiguous , but due to various reasons it can also be a recurring name due to various reasons. The FQDN is oftentimes the same as . Oftentimes the FQDN is equated to the object title. The usage of host name / or FQDN for referencing should be considered carefully.
As a rule, MAC addresses are unique worldwide since they are set by the manufacturers of the network components. The low risk of recurring MAC addresses is however only right in theory. Due to the increasing virtualization and the resulting change of MAC addresses by the userusers, this attribute is not always the first choice for unambiguous referencing. As many MAC addresses as desired can be set by entering a MAC address for each port in the
Port (Network) category. When using technologies like bonding /or trunking, the MAC address is documented in the
Logical port (Network) category.
The In most cases the inventory of property is done carried out across the entire organization in most cases and thus is therefore not purely only an IT-related topic (Asset Management). Each material property which is focused by the inventory to be inventoried receives a unique number. in In i-doit This this number can be documented for each object – in the
Inventory number attribute within the
Administration → CMDB settings → Object type configuration →
[Object type group] → [Object type] the automated generation of inventory numbers can be configured, if desired. Here various placeholders are available for creating a naming formular structure per object type.
Inventory numbers and QR codes offer an ideal combination and can be combined nicely with QR-codes for joined to labels. QR - codes are generated for each object by i-doit. Such labels can be printed using the i-doit QR-code printer, for example.
Identifier of Third-Party Systems
Data from third-party system, for example from the inventory/ discovery area, can be imported to i-doit. In most cases, these systems also possess unambiguous identifiers or something similar. When these identifiers are imported, the category
Data Source can be used. This way, multiple used systems can be synchronized in order to unambiguously reference objects on all systems unambiguously.
Internally, i-doit uses constants that unambiguously reference all kinds of data. A constant consists of capital letters (A-Z) and underscores (_). Such constants are used for some objects that already exist in the default installation of i-doit. The
Person object "admin", for example, has the constant
These constants cannot be viewed or even edited in the web GUI. For this reason, this is done in SQL in the database. Each tenant has a separate database in which the
isys_obj table exists. All objects are saved there. The column for the constant is called
Manipulations of the database risk endanger the functionality of i-doit. For this reason, we can not cannot provide any warranties for problems that result resulting from self-made manipulations. Any Thus any activity should thus be well considered and possibly coordinated agreed with us beforehand, if necessary.
Further Unique Attributes
- Attributes can be defined globally as unique or globally, per object type or (for list categories) per object. Multiple occurrences are criticized In case of multiple occurrences a notification window by i-doit is displayed when trying you try to save your entries.
- If the attributes mentioned above do not suffice, additional ones can be created.