Sorry but what you see is what you get. Your only options, as I see it, are to
tell the new users to use just forwardall.rs and that's it, or to move your
other rulesets out of /usr/OV/conf/rulesets and deal with that complexity as the
administrator. Rulesets in ESE.automation should be fully-qualified so the
path does not matter. But you will have more trouble editing them, as you will
have to set the location filter on open.
As for rulesets remaining active, that also would be part of the design, and if
you want that changed you may call Support and have a formal change request
opened or you may send an informal note to netview@tivoli.com.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Sylvia Koch <sylvia.koch@EMPRISE.DE> on 01/21/2000 05:00:06 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks/Tivoli Systems)
Subject: Rulesets offered in Webbrowser
Hi,
I am working at customers site with NetView for AIX 5.1.1
The NetView Web Browser offers a list of rulesets for filtering the event
display. The offered list of rulesets includes all rulesets stored in
/usr/OV/conf/rulesets and includes as well those rulesets which are
designed and created for usage in ESE.automation and not for filtering.
How can I exclude those automation rulesets from being offered in the
NetView Web Browser?
I observed that NetView users try to use different rulesets including those
automation rulesets, so that the automation actions are triggered several
times for each trap. Furthermore, though the NetView users have meanwhile
closed their Web Browser, the rulesets they have used remains activ until I
stop the appropriate WebServer processes.
Does anybody have an idea?
Thanks
Sylvia
|