Re: Forms through a 64K leased line

From: Glenn Goslin <glenng_at_iafrica.com>
Date: Fri, 24 Nov 2000 22:24:05 +0200
Message-ID: <3a1ecf5c.0_at_news1.mweb.co.za>


This may be a silly question, but what exactly are your requesting ? New fmx's or a sql query ?

We run a forms application where we store the fmx's on a central server in Johannesburg. We then have branch servers in our major cities, of which the furtherest is Cape Town (+/- 1300 km) and is linked using a 2mb line.

When changes are made we "push" the updated fmx's to the branch servers overnight, after having undergone a testing process at central office. When users at the branches startup up the app, they actually first start a DOS batch file which always first compares the date-time stamp of the files on their PC's to that on the local branch server, and then starts up the forms runtime. This means that users always get new fmx's from their local server and not across the WAN.

This process works well for us, and with +/- 3000 users in 19 sites we don't have too many problems, except of course when someone leaves their app open overnight, but users are made aware of the implications.

The trick is to keep to an absolute minimum the amount of unneccessary WAN traffic. We try to ensure that the only WAN traffic during peak hours is the sql query and the result, not large files.

It may be worthwile to get someone to "snif" your networks. When we started with Oracle as our main platform, we had all sorts of problems with response times over the networks. Of course, users suspected Oracle.

After we got someone to monitor the network, we discovered all sorts of interesting going on's. Massive files being moved around, e-mail, a badly written app, however small, can trash even the biggest bandwidth networks.

We found that forms was more effecient across our WAN than anything we had run before ( but that may be because the previous stuff was not well written :)).

Glenn

Patrick De Giorgi <pdegiorgi_at_infomaniak.ch> wrote in message news:8vioqq$b9t$1_at_pollux.ip-plus.net...
> Hi !
>
> Thanks for the answers !
>
> For info, all the .fmx aren't on the server ! They are on the local
 machine
> !
> What we send through the leased line is only the requests !
>
> That's what is strange....why a min.30 s pause between the request and the
> answer...?
>
> Any idea ?
>
> Thanks,
>
> Patrick
>
> "Connor McDonald" <connor_mcdonald_at_yahoo.com> a écrit dans le message
 news:
> 3A1BA6E4.1CA9_at_yahoo.com...
> > Patrick De Giorgi wrote:
> > >
> > > Hello !
> > >
> > > We are testing Forms 6 through a 64K leased line between Switzerland
 and
> > > Belgium.
> > > The version of Oracle Server is 7.3.4.
> > >
> > > The results are ... awful !
> > > When we press enter to send the request, we measured that it sends
 about
> > > 1,5Ko in average, then we wait about 30 s and then we received the
 answer
> > > (also about 1,5Ko).
> > >
> > > If we do the same tests on our Lan, the results are normal. Almost no
 wait
> > > between the request and the answer.
> > >
> > > We are using TCP/IP through 2 routers (1 Cisco 4000 and 1 Magellan).
> > >
> > > Is there a way to use Forms 6 like this but with a normal answer time
 ?
> > >
> > > If no, which leased line speed should we have ?
> > >
> > > Thanks,
> > >
> > > Patrick
> >
> > For client/server then two things are very important...
> >
> > a) don't bring your fmx's down the leased line - have them local to the
> > client (which also induces deployment headaches)
> >
> > b) you really need to code with WAN in mind (simple things like a select
> > in a POST-query can kill you)...
> >
> > Alternatively look at running web-based forms which could possibly be
> > more efficient - we're doing that over dial-up with reasonable results..
> >
> > HTH
> > --
> > ===========================================
> > Connor McDonald
> > http://www.oracledba.co.uk (mirrored at
> > http://www.oradba.freeserve.co.uk)
> >
> > "Some days you're the pigeon, some days you're the statue"
>
>
Received on Fri Nov 24 2000 - 21:24:05 CET

Original text of this message