I have a severe web-sever user-access problems in version 4 that is
reveling because I transformed the V3 sever for customer information into
version 3.

 I using fore trouble shooting / experimenting an G5 Imapper V4 and to
inform other RIVM ict-departments  an old Imac MacOS9 with lots of memory.
Why did I used the old MacOS and version 3?   For its stability and lack of
time.
Everybody can see the total view of al the devices that we monitoring was
is up and down. Not everybody had access tot al the maps / devices, but V3
gave a good overview.
Why did I have to the switch to version V4? Because at the office I use a
G5 and v4 so to be more efficient I want tot use one version.



The problems:
================================================================================
User interface:
V3 when a user contacts the web-server, it start in a error-overview of all
the devices.

V4 starts with the alphabetical first map-jpg!!  where the user has access
rights.  http://mapxx/document/_/!index.html.  I am in need over a thin
html-file that give a total overview.  (V3)

================================================================================
Access control
When I give a user (rivm) a class B access 131.224.*.*  then it is
difficult to access the server files that are restricted . The user have to
know the exact name of de map and merge that in the URL !!!

Example when I automatically log on to
http://rivm-net51:8090/NAS-polling-5sec/document/_/maplist.html and then  I
what tot access map âxserversâ  where I have a username and password
access,  I must replace the part in the URL  âNAS-polling-5secâ  with
âxserversâ

The method is not user friendly!!!
===============================================================================

Lack of overview using web-access:

V3 used the total devices error page a start outages would have a better
choice. V4 give at first a alphabetic map jpg.  As troubleshooter or our
helpdesk there is a need for a light (html) web-window with give a overview
of the present and former problems.
================================================================================

Bug in OS9
In V4 MacOS9 is a difference (bug) in displaying the full device-list in
the full map-list, it will only give the full of de first map in the
list!!!
When I imported a V4 map form the MacX into the G3 the cisco core switches
where in a stat of non polling!!! Where  I changed that in polling the
system rediscovered and the map was ruined . So I used a old V3 map.


================================================================================

Conclusion:
It is a long story and I wished tot roll back to the V3 web-interface
because it better served my purpose.
================================================================================

with regards Hans  RIVM the Netherlands


Used configurations
Testing purposes / monitoring:
G5
MacX 10.3.8
Imapper 4.2.4
Polling > 250 devices

Information-server
G3
MacOS9.04
Imapper 4.2.4
Polling > 250 devices
____________________________________________________________________________

"Dit bericht en eventuele aangehechte bestanden zijn vertrouwelijk en
uitsluitend bestemd voor de geadresseerde. Ongeautoriseerde verstrekking of
bekendmaking aan en gebruik door anderen zijn niet toegestaan. Als u dit
bericht per vergissing hebt ontvangen wordt u verzocht dit onmiddellijk aan
de afzender te melden en het bericht van uw systemen te verwijderen.
De werkgever van de afzender kan niet garanderen dat de verzonden en/of
ontvangen informatie juist is en aanvaardt geen aansprakelijkheid voor
schade die eruit kan voortvloeien."

"This message and any files transmitted with it may contain confidential
information and is solely intended for the addressee(s). Any unauthorized
disclosure or actions taken in reliance on it are forbidden. If you have
received this message in error, please delete it and notify the sender.
The employer of the sender does not guarantee that the information sent
and/or received is correct and does not accept any liability for damages
related thereto."

Reply via email to