You can find out how Tivoli works by asking your marketing rep.
In Tivoli terminology a "lighthouse" customer is one who has entered into a
special relationship with Tivoli. They have formally agreed to test beta code
and to help development smooth out problems in new releases before they go GA,
so that other customers will have an easier time. They also agree in some sense
or other to be reference accounts for marketing purposes and sometimes even to
prouce presentations at Planet Tivoli telling other users about how they have
benefitted from Tivoli products. In return of course they get more influence on
what new code gets developed.
And not all customers can get to be "lighthouse" -- they have to be leaders in
or very representative of their industry so that other firms in that will be
impressed by what they have accomplished. Sometimes too, the number of
lighthouse customers is restricted by how many development can concurrently
handle. Any Tivoli marketing rep should be able to provide information on how
to become a lighthouse customer.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Steve Kostyk <skostyk@KODAK.COM> on 09/29/99 08:40:47 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: Re: Netview Version 6
From: Stephan J. Kostyk
James,
I've always wondered how Tivoli works internally. Can you define what a
"Lighthouse" customer
is?
sk
James Shanks <James_Shanks@TIVOLI.COM> on 09/29/99 08:22:15 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: Stephan J. Kostyk/505732/EKC)
Subject: Re: Netview Version 6
Well, I didn't think lighthouse customers were supposed to release that
information publicly, but as long as you have, I m surprised that you
haven't
said anything about the fact that there is a brand new "universal" web
client --
that you use the same one for UNIX and NT and that it is greatly enhanced.
That is the GUI direction I was hinting at before. No changes are
currently
being done to the NetView clients that I am aware of.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Stephan Schwalb <sschwalb@DEBIS.DE> on 09/29/99 02:46:20 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: Re: Netview Version 6
Hi,
most of the changes for V 6.0 (formerly named V 5.2) were already presented
by
some
powerpoint
presentations at the last Planet Tivoli (this year and end of last year).
New functions were (this is for unix):
- location sensitive topology (through a locations.conf - multiple
hirachies)
- the choice of using snmp instead of ping for polling (in the seed file as
in
the
oid_to_type)
- serial interface handling (unnumbered serial interfaces)
- improved installation verification
- supmap explorer (as already realized with NV on NT)
- auto-discovery of web-enabled devices
- migration function V5.1 - V 6.0
As we participating in the field tests for V 5.2 /V 6.0 (litehouse program)
we
already
received field test 1 and could verify some of the stuff above. Based on
lack of
time
we've only checked some points, but as far as I could see, snmp instead of
pinging
and submap explorer is working.
In addition we found support for multiple community names and some changes
in
status
propagation.
For sure we will verify the rest, at least when receiving the 2nd fields
test
(next
month) but all of the
information it is not official yet.
Hope this helps you to get a view on what we all can expect from NetView in
the
near
future.
Have fun___Stephan
Chris Cowan schrieb:
> James Shanks wrote:
> >
> > Possible? Nothing is impossible if you are willing to start over and
re-design
> > code from the ground up. I didn't say it couldn't be done; I said it
probably
> > wouldn't. The Tivoli desktop, which isn't nearly as sophisticated as
the
> > NetView desktop, was designed differently from the get-go. The Tivoli
desktop
> > is just a front- end for the oserv running on that box. It is the
oserv on
the
> > box with the desktop which talks to the other oserv on the server. But
the
> > NetView client has no daemon process to do what the oserv does. It is
just
a
> > desktop and it must therefore be of the same type as the server.
>
> My real intent in posting was not to focus on the GUI, but to get some
> recon on what V6 is going to be.
> So far, all I know is all of the development is now at Cambridge, MA.
> So that smells to me like we'll get some convergence.
>
> None the less, HP OpenView does have the ability to do this. So there's
> a factor that could drive the decision.
>
> > So what did I say? I said I don't think they are going to re-design
the
NetView
> > client-server. Instead I think what they will do is improve the web
interface
> > so you won't need an Xclient or a Windows client. That's the industry
direction
> > after all, not just NetView's.
> >
>
> I'm not going to comment on this existing Web interface. Regardless,
> the GUI performance would still be an issue (and probably not acceptable
> with Web/Java/JavaScript) without some significant changes.
--
______________________________________________________
Mit freundlichen Gruessen / With kind regards / Saludos
Stephan Schwalb
Systems engineer - Networkmanagement
debis - Systemhaus
Tel.: +49 (711)-17-49971
Fax : +49 (711)-17-49663
email: sschwalb@dbmail.debis.de or sschwalb@debis.de
-------------------------------------------
Services by Daimler Chrysler
-------------------------------------------
_____________________________________________________
|