On Fri, 19 Jan 2001, Erwin G Olario wrote:
>
> The information we wish to distribute will be on a database from our main
> office, we want to share these data to our brances. No fancy stuff, all they
> really need is the data. This is the reason I'm looking into intranets
> because publishing the information in HTML won't be too difficult (But since
> some of the data will be from a database and we need some interactivity, i
> need to learn some scripting, right? I'm now checking out Python).
check these out, perl, php for scripts and mysql or even postgreSQL for
database
> With these in mind, I am considering old PCs (486DX and P100+ with
> 32Mb+ of RAM) as client-terminals, I don't know about the server yet.
> Initially we plan to connect 10 branches. My actual questions are:
> 1) What kind of skill would I need to implement this on Linux?
all you need is time, patience and most importantly, Internet access, if
there's a problem, the lists are here all the time :)
> 2) Will the specs for the client-terminals be good enough? What
> else should I keep in mind?
IMHO, since you're new to Linux, I'd advise for you to use *OUCH* windo$e
9x with netscape (no IE) for the clients. then gradually move to thin
clients based on linux.
> 3) What kind of specs for my server will suffice for the 10-clients and
> with
> provisions for more in the future?
for 10 clients, even a p200 with 64 to 128 of main memory would suffice.
just make sure you've got reliable peripherals like HD, motherboard, PS,
etc. go for a p2 400+ or p3 to ba able to scale to hundreds.
> 4) The network will be online for about 10-12 hours daily, how should I
> connect these branches?
there are 3 options, with pros and cons
1. private point to multi-point frame-relay circuit
get a 64 to 128 Kbps link to your head office then each can get a
19.6 to 64 kbps link depending on the number of workstations at the
branch.
pros : better security, high reliability
cons : high recurring cost and high investment, 80K PHP est
initial expenditure per branch and 100 to 150 for the head office just for
network.
2. private dialup to head office
get dialup lines on your head office and have your clients
dialup to you
pros : good security, low per branch investment, minimal recurring
costs
cons : high maintenance (unless you get those digital e1r2
variants), around 250 K PHP network hardware investment at head office.
3. dialup through ISP
get a 64kbps (even a shared connection at 1:5 would suffice for as
long as you get full for local traffic) from an ISP, and get a high volume
dial-up account (also from the same ISP)
pros: easier to maintain (ISP's job to keep your network up), low
per branch investment, Internet access already bundled.
cons: security will be an issue, and you will have to use VPN
(with encryption) for sensitive traffic, medium to high recurring costs,
around 100K PHP initial, investment at head office, if you're using
windo$e, there is an issue on monitoring Internet usage (employess might
chat instead of their work... etc)
> 5) What are the Linux components for this type of project?
Based on my network options above, the only linux based unit there will be
the server hosting the database and application itself - initially. By the
time your network matures, then you could move on to linux.
as usual, here's my disclaimer... these are just my opinion and there are
no warranties whatsoever. Price estimates would be blown if our peso
devaluates over 60 to a dollar :(
hth,
-mark
*************************************************************************
Mark Anthony J. Mercado [EMAIL PROTECTED]
Laguna Internet, Incorporated
Rm 404 Vega Centre, Lopez Avenue, Los Banos, Laguna, Philippines 4030
Ph. 63 49 536.0085 Fax. 63 49 536.0067
*************************************************************************
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
