Here you will find our monthly tips to improve your OTRS, i-doit, SNAG-View and NeDi configuration. If you need support in setting up your systems or need special adaptations, then simply contact us at +49 441 390 10 10 40 or send us an e-mail, we will be happy to advise you.
More than 100 customers from all areas of business and public administration trust our software solutions and services.
[i-doit] device exchange
The free "Device Exchange" add-on module offers a fast and convenient approach to replacing devices. Imagine the following scenario: A switch which is in use and well-documented fails; it needs to be replaced by another switch. The second switch also exists in the CMDB and is documented as completely as possible (model, accounting, location, status).
Figure 1: Initial situation
Before you can start the exchange, the desired object type must be enabled in the device exchange configuration. You can also select the categories which are exchanged by default.
Figure 2: Configuration of a device exchange (Management -> CMDB settings -> Device exchange)
The module can be found below "Tools". If this is not the case, the authorisations for the module may be missing.
Figure 3: Calling the device exchange module
In the "Exchange objects" module, you now select the two switches to be exchanged. The checkboxes set in the configuration can be edited again at this point
Figure 4: Exchanging devices
After clicking on "Exchange devices" the exchange process starts; a log is then displayed. The stored switch has now adopted the selected category entries of the original switch. The defective switch is assigned a CMDB status of "Replaced".
Figure 5: Switches after the exchange
Using the Device Exchange module can save a great deal of time in the case of more complex categories (network, ports).
Additional placeholders for the path to plugins ($USERXXX$) can be integrated very easily in SNAG-View. The following steps are necessary for this:
A new <item> entry must be created in the "resource_cfg.xml".
Note: Be careful not to change or delete existing <item> entries.
Example:
We currently ship two predefined macros: "$USER1$ and $USER2$". After the change, the macro $USER3$ is available for the path /var/lib/nagios/libexec-customer2.
The script "/usr/bin/createNagiosCfg.sh" is then executed, so that the configuration is saved and saved in the resource.cfg.
With the help of the postmaster filters incoming e-mails can be processed specifically in ((OTRS)) Community Edition. One use case is ignoring automatic replies or absence notes.
In the following example configuration, the content of an automatic reply is not processed and discarded as an article.
The configuration of the postmaster filters can be found in the e-mail settings in the admin area. A new filter can be created via "Add filter".
