Hi Christian, all,

${SPECROOT}/custom/Events/ is the base directory for the files you mentioned. 
You can have AlertMap and EventDisp directly within that directory and/or 
within subdirectories. The subdirectories directories may also have custom 
names, not just modeltype specific. As usual, there are up- and downsides: 
using subdirectories you end up having smaller files allowing for better 
separation and maintenance while working without subdirectories makes keeping 
track of custom event IDs more easy.
Anyway, OneClick Event Configuration will read all files including those within 
subdirectories but will still remove any formatting/comments from your files 
when used for editing.


Mit freundlichen Gruessen - Yours sincerely

Raphael Franck
Consultant
Service Transition - Technical Design
Global Infrastructure Operations

Computacenter AG & Co oHG
Enabling Users

Europaring 34-40, 50170 Kerpen, Germany
WWW: www.computacenter.de<http://www.computacenter.de/>

Von: Fieres, Christian [mailto:c.fie...@mainova.de]
Gesendet: Mittwoch, 25. Juli 2018 10:45
An: spectrum <spectrum@listserv.unc.edu>
Betreff: [spectrum] Exact location of custom AlertMap and EventDisp files

Hi all,

I am in the process of optimizing a SPECTRUM 10.1.1 installation that has been 
growing for 20+ years. Traditionally, AlertMap and EvenDisp files had been 
edited by hand in their original location $SPECROOT/SS/CsVendor/ etc. To 
provide for updates to run more smoothly, it is about time to use customized 
Trap-to-event and Event-to-alarm mappings into the custom directory structure. 
I understand that  every configuration line for the same trap oid or the same 
event handle placed in the custom directory takes precedence over the one in 
the CsVendor directory tree. What I don't get is excactly what files SPECTRUM 
expects to contain the custom entries and where they should be placed.

Docs say, custom EventDisp files must be placed under $SPECROOT/custom/Events, 
while custom AlertMap files are requested to be found under 
$SPECROOT/custom/Events/AlertMap. Does the last term refer to a directory name 
or some sort of "global" custom AlertMap file? In this case, I would assume 
that a corresponding global EventDisp file (Model Type independent) has to be 
placed as $SPECROOT/custom/Events/EventDisp.

_Or_ am I required to build a directory structure similar to the one in the 
CsVendor directory? If so, do I have to do this twice - one, for my AlerMap 
files under $SPECROOT/custom/Events/AlertMap and two, for my EventDisp files 
under $SPECROOT/custom/Events directly?

Currently, in SPECROOT/custom/Events, I only have directories for custom Event 
Text and Probable Cause files which I have been using for many years now. 
Frankly, I have difficulties to understand the CA documentation in this case. 
And I have no SPECTRUM installation at hand that has been customized in a more 
sophisticated way compared to mine. ;-)

Thanks in advance!

Regards,
Christian Fieres

Mainova AG
Sachgebiet Netz- und Infrastruktur (M3-ST4)
Teamleiter Service Operation Center
Solmsstraße 38
60623 Frankfurt am Main

Telefon 069 213 23617
Mobil 0170 5601563
Telefax 069 213 9623617
E-Mail c.fie...@mainova.de<mailto:c.fie...@mainova.de>
Internet http://www.mainova.de

Mainova Aktiengesellschaft - Solmsstraße 38 - 60486 Frankfurt am Main · 
Postadresse: Mainova AG, 60623 Frankfurt am Main · Vorsitzender des 
Aufsichtsrates: Bürgermeister Uwe Becker Vorstand: Dr. Constantin H. Alsheimer 
(Vorsitzender), Norbert Breidenbach, Lothar Herbst Sitz der Aktiengesellschaft: 
Frankfurt am Main - Amtsgericht Frankfurt HRB 7173 - USt-IdNr. DE 114184034 
Mainova steht für besten Service, faire Verträge und top Preise für Ihre 
Energie - mit Auszeichnung! Mehr Infos unter: http://www.mainova.de/auszeichnung

  *   --To unsubscribe from spectrum, send email to 
lists...@unc.edu<mailto:lists...@unc.edu> with the body: unsubscribe spectrum 
raphael.fra...@computacenter.com<mailto:raphael.fra...@computacenter.com>

---
To unsubscribe from spectrum, send email to lists...@unc.edu with the body: 
unsubscribe spectrum arch...@mail-archive.com

Reply via email to