[2527] in Enterprise Print Delivery Team

home help back first fref pref prev next nref lref last post

Enterprise printing : GAD meets MIT

daemon@ATHENA.MIT.EDU (Norbert.Warnke@GAD.de)
Wed Sep 11 05:22:13 2002

From: Norbert.Warnke@GAD.de
To: LAMBERT@mitvma.mit.edu
cc: printdel@mit.edu
Message-ID: <C1256C31.002CD135.00@grz_notes_mta.grznord.de>
Date: Wed, 11 Sep 2002 11:21:39 +0200
Mime-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

If you saved any of the rejected email to <lambert@mitvma.mit.edu>, I'd
love to see them to figure out what was broken.

>>> I add the mail at the bottom


We have not implemented IPM for printing to distributed printers.  We'll
evaluate that possibility sometime in the future.  Out implementation of
IPM allows authenticated file submittals from application servers and
desktops.  Due to our authentication requirements, a customized secure
browser interface was developed for desktop submits.  klp -- kerberized
lp can also be used from desktops.  We're only managing central printers
as this time.

>>> OK

Our network environment on the campus is based on a 10/100Mb/s switched
ethernet topology.  All servers, desktops, and printers are connected
via this topology.

>>> nice network, you might be lucky

    How many users do work with the system ?
    Possible to send me some screen shots of the web-client?

You didn't mention anything about business/service recovery.  I would
have a number of issues with deploying additional distributed IPM
servers at the branches if the central server can't handle the load.
Have you considered the possibility of running two central servers,
each with say 75% of the capacity to handle your entire load.  That
implies you have 150% capacity to handle your production load but also
gives you 75% capacity for handling your most critical work should
one of your two production servers go down.  You may have another
whole model for business/service recovery which handles the server
outage problem.


>>>> we would plan the central servers as you mentioned to have a
     backup/recovery.
     the reason considering about additional IPMs is to reduce
     the network traffic . If we use the distributed IPM, printfiles
     from central applications will be transmitted once via the line and
     then is spooled at the distributed IPM, customers the can view
     the reports and print them as often they like without using the
     WAN. It is not clear, when we have to use a secondary IPM relating
     to the network traffic , output amount and printer capacaties.
     I think, we have to test different scenarios.

I can't provide a sizing estimate for you.  IBM should be able to
do that based upon your print volumes, need for converting one
datastream type to another, and the number/size of the printers you
plan to drive at one time.  IBM has a tool to estimate the server size -
both processor size as well as disk.

>>> If we decide to buy IBM, IBM would do this.

I'm assuming you don't have to worry about encryption of the data on
your private WAN.  That's an issue for our open network but we are
living with an unencrypted solution today.

>>> we have no need for encryption




Hope this helps some...


>>> if your solution works and you are satisfied , there is no reason for
me to
    discard IBM from our evaluation roadmap, so it helps




>>> error message of recejected email:
                                                                           
  Ihr          Antwort: Re: Enterprise printing : GAD meets MIT?           
  Dokument:                                                                
                                                                           
  wurde nicht  LAMBERT@mitvma.mit.edu                                      
  zugestellt                                                               
  an:                                                                      
                                                                           
  weil:        Enhanced Mail System Status Code (RFC1893): 4.4.7           
               (Persistent transient failure - routing/network: delivery   
               time expired)                                               
                                                                           






Next week on 18th September we have a meeting with IBM to detail their
concept.

kind regards

GAD eG
Norbert Warnke
_____________________________________
GAD eG
Raiffeisenstraße 12
31275 Lehrte

Tel.:      (05132) 91-2320
Fax.:     (05132) 91-2260

eMail:  Norbert.Warnke@GAD.de

http://www.gad.de




home help back first fref pref prev next nref lref last post