yes ... the confusion between netview.pre and netnmrc.pre has always be a
mystery .. different docs reference one or the other of the file. I usually
have both files, one being a link to the other (just in case).
You need to have this value set to 1 in order for the ACK status to be
propagated.
As for the opened map, you can have only one Read/Write at a time so it's
either the netviewd daemon of the standard ovw X map. The Java consoles can
connect to either of the two. Maybe what you need to do is start a X
display of the read write map and have the java console connect to it. In
order to do that you use the command "netview -dconsole" to open the map
and stopping the netviewd daemon so that you will have the Read Write
opened as a GUI.
If you don't do that, your display will be read Only and the java console
will have a choice between the two. They need to choose the one opened in
Read Write for it to work correctly.
Salutations, / Regards,
Francois Le Hir
Network Projects & Consulting Services
IBM Global Services
Phone: (514) 964 2145
"Duppong, Jason"
<jason.duppong@th
omson.com> To
Sent by: "'nv-l@lists.us.ibm.com'"
owner-nv-l@lists. <nv-l@lists.us.ibm.com>
us.ibm.com cc
Subject
10/20/2004 11:38 RE: [nv-l] Netview Web Client
AM Question
Please respond to
nv-l
Francois,
Thanks for the response. I do not have a netnmrc.pre file in /usr/OV/bin,
but I do have a /usr/OV/bin/netview.pre. This file contains the entries
you
mentioned so my colleague and I have played with the settings by removing
the lines in the file and setting the variable to 0. Either way the Web
Client and the map it is connected to reflect the same status when we
Acknowledge or Unacknowledge a problem. I've looked up this option in the
archives for this forum and people seem to want to do exactly what we are
trying to do, but I'm guessing they may have been using the X client
instead
of the web client.
I also looked at the /etc/init.d/netnmrc startup script. It references the
file you mentioned so we created the /usr/OV/bin/netnmrc.pre file and
changed the values to 0 then restarted Netview. Web clients still modified
the map they were connected to and thus all web clients eventually
indicated
the same state.
When we have started multiple X clients we have noticed that the web client
offers us a choice of which map to connect to. Is the web client just a
"webinized" interface for an X client and has no real independence?
Thanks again for any responses
Jason
-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On
Behalf Of Francois Le Hir
Sent: Wednesday, October 20, 2004 8:50 AM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Netview Web Client Question
Jason,
do you have
NVMAPGLOBALACK=1
export NVMAPGLOBALACK
in /usr/OV/bin/netnmrc.pre ?
Salutations, / Regards,
Francois Le Hir
Network Projects & Consulting Services
IBM Global Services
Phone: (514) 964 2145
"Duppong, Jason"
<jason.duppong@th
omson.com> To
Sent by: "'nv-l@lists.us.ibm.com'"
owner-nv-l@lists. <nv-l@lists.us.ibm.com>
us.ibm.com cc
Subject
10/19/2004 02:15 [nv-l] Netview Web Client Question
PM
Please respond to
nv-l
Hi,
I support a group of users that currently make use of the X Client for
various tasks. From what I've been able to tell the Web Client would
provide nearly all features this group needs except for the ability to
independently acknowledge/unacknowledged events. During testing I've
created separate logins to the web client as well as used the same logins
and nothing seems to allow us to independently respond to events. When
someone uses the web client to acknowledge an event, all web clients update
with the acknowledgement as well as the Read/Write map. If we acknowledge
the event on a read-only X client only that client is updated while the web
clients and the read/write map remain unchanged. Based on the
documentation
I've read, this makes sense since the web client uses the Read/Write map,
but I would think that since the Web Client is a separate application that
you can 'install' it would have the same or similar capabilities with
respect to the acknowledgement feature.
Anyone know if this is just an accepted limitation of the web client or is
there a backdoor modification one could do to get similar functionality
with
the X client?
Thanks,
Jason
|