28.06.2013 Views

Papers in PDF format

Papers in PDF format

Papers in PDF format

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

4.3. The Production Phase<br />

The production phase started January 1, 1995. Accord<strong>in</strong>g to the results of the <strong>in</strong>troduction phase it was<br />

immediately clear that we need a much more powerful mach<strong>in</strong>e for this phase. But to m<strong>in</strong>imise costs as well as<br />

adm<strong>in</strong>istration overhead we cont<strong>in</strong>ued to run all services on a s<strong>in</strong>gle mach<strong>in</strong>e which was sponsored by GMD.<br />

We placed the mach<strong>in</strong>e on a separate service net.<br />

Figure 1: System structure<br />

Via a firewall system this service net is l<strong>in</strong>ked to GMD's IP backbone [Chapman and Zwicky 95]. As a member<br />

of GMD's Technopark gekko is also connected to the central backbone. Beside the service mach<strong>in</strong>e we<br />

<strong>in</strong>stalled a modem pool at the service net which users can connect to for retriev<strong>in</strong>g <strong>in</strong><strong>format</strong>ion from the<br />

servers. Our <strong>in</strong>frastructure is completed by an ISDN router which is connected to GMD's backbone. One of its<br />

<strong>in</strong>terfaces is reserved for use by DW only to transfer raw text material from DW to gekko for conversion <strong>in</strong>to<br />

HTML as well as to give some selected employees of DW full Internet access via GMD.<br />

We used standard software (NCSA's httpd, ftpd from the Wash<strong>in</strong>gton University <strong>in</strong> St. Louis, freeWAIS and<br />

sendmail [NCSA 95, Liu et al. 94, Costales et al. 93]) for realis<strong>in</strong>g all services due to their rich functionality<br />

and widely usage with<strong>in</strong> the Internet community. Especially, we used a public doma<strong>in</strong> Web server because no<br />

matured commercial server was available at that time.<br />

Also the migration to our new server mach<strong>in</strong>e at the beg<strong>in</strong>n<strong>in</strong>g of the production phase was smoothly and<br />

nearly transparent to the users. One service after the other was transferred by chang<strong>in</strong>g its DNS entry after<br />

prepar<strong>in</strong>g the service on the new mach<strong>in</strong>e. At the beg<strong>in</strong>n<strong>in</strong>g, some users and programs (especially Web crawler<br />

for <strong>in</strong>dex<strong>in</strong>g entire Web sites) cont<strong>in</strong>ued to use the old IP address. Thus, for a transitional period we kept the<br />

old servers runn<strong>in</strong>g but po<strong>in</strong>t<strong>in</strong>g any users to the new mach<strong>in</strong>e.<br />

To guarantee and to verify our quality of service agreements we monitor the hardware with our <strong>in</strong>ternal<br />

SNMP-based network management system [Eisenblätter et al. 93, Case et al. 1990]. Us<strong>in</strong>g these mechanisms<br />

we are also able to detect any violations of agreed resource limits (like e.g. Internet bandwidth) and to obviate<br />

them if necessary. For the beg<strong>in</strong>n<strong>in</strong>g we also manage DW's ISDN connection to GMD. We keep access data for<br />

all services as well as the router utilisation <strong>in</strong> order to produce our monthly usage statistics. Backups of the<br />

data areas are made automatically over night.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!