FileMaker Server, FileMaker Pro and Web Publishing

[stanley]

I've just been asked by a client to plan to make his intranet FMServer system accessible to staff via the internet, and I've never dealt with FileMaker's web publishing capabilities before, so I'm looking for some basic information here. The setup is as follows:

FM Server running on OS 8.6

Client computers on various platforms, all running FMP 5.5

DSL connection to the internet, without a static IP (I realize this will have to change)

I have two basic choices - the sales staff is small (4 or 5 people) so the client can afford licenses for them to have FMP on their laptops; however, because some of them have multiple computers, and may want to access the databases on a customer's machine on-site, perhaps I'm better off web-publishing. I honestly don't know the positives and negatives to these two choices, and I'd appreciate input from one and all on this.

Also, am I going to need to use FM Unlimited to publish the FM Server material over the web, if that's the way I end up going? Is it possible to do this with FM Pro? The 10 IP address limitation is unlikely to ever be a problem, but I don't see how a regular copy of FM Pro would do the job... any info on this would be appreciated too.

Also, if anyone has any suggestions or knows of any pitfalls to avoid, that would help too, because, as you can tell, this is a part of the FileMaker world I've never ventured into before, though I've been blasting away at FMP and FMS for (what feels like) centuries.

Thanks alot all,

Stanley

[Unable]

"...knows of any pitfalls to avoid..."

There are 2727 Threads just on the UFO, WC and CDML forums. They all deal with problems and pitfalls of web publishing. There are no easy answers. There are complex answers, which once understood, can seem relatively easy.

Avoid IWP.

Avoid thinking that you can do everything (or anything) quickly.

Start by going to every db file you have created and renaming all the fields so that they are either one_word or oneword. And the db files themselves should be one_word.fp5.

Realize that there are many issues with relationships on the www which can be overcome with other techniques.

Toss every ScriptMaker Script you have worked so hard to create (unless you are really talented) because ScriptMaker handles only one event at a time and does not queue requests.

Learn HTML or how to use an HTML authoring app.

Understand that there are certain things in web publishing for which JavaScript is absolutely necessary.

Sense that there are issues around data security (and a few threads which are insightful - don't be shy to search the forums and spend hours/days reading).

Be advised that there are many useful examples on the Sample Files forum.

Know that you are going to be busy, very busy.

Savor every moment.

Bon chance.

[Garry Claridge]

Try it with FM on the Client machines first. Check speed etc before venturing into the Custom Web Publishing (CWP) world. You can build great web-applications with FM, however (as Unable said) you will need a good knowledge of HTML first.

You will not need FMUnlimited for the small number of Clients. You will need one computer with FMPro running as the FM WebServer.

All the best.

Garry

[stanley]

Garry:

Thanks (and thanks to Unable, too) for the input. Very helpful. It sounds to me like FM Unlimited/CWP would be more than the client is going to want to budget, which would kill it before it even reaches the runway. As far as running a machine as an FM Webserver - is it possible to use that machine for other FileMaker tasks concurrently, or must it only run as the Webserver?

Regardless of the answer, it sounds as though FileMaker on the client machines is far and away the simpler of the choices, even if I've got to rework some scripts/layouts/etc.

Thanks again

-Stanley

[IdealData]

Rather like you Stanley I've done all my development in FMP without much regard to web publishing. I've done lots of research, and some minor stuff in CWP to overcome some speed problems.

I run a 2 site network with 256k link. Performance at the remote end can be variable due to other traffic requirements, so you need to see the speed of delivery via DSL to appreciate if it will be suitable. Remember, even though your clients may have DSL (say 1Mb down) your delivery performance is still limited by the "up" speed of your DSL connection for the FMServer - this is the real bottleneck.

The 256k line I have supports 10+ users, but not highly active. Maybe that will be sufficient for you too.

Watch out for layouts with multiple records with portals - especially if the relationship is sorted by fields. Also some value lists based on relationships can be very slow as they must also be sorted prior to use. Things speed up once the list has been used by the client.

Incidentally, 56k dial up simply won't hack it

[Anatoli]

RE: Incidentally, 56k dial up simply won't hack it

With Terminal Services I am doing large reprogramming in live databases from home through 64k ISDN dial-up.

From 128k lines it is viable and far the fastest solution for networks with 10 users.

512k is more than enough for 10 users.

T1 is OK for 50 remote users.

Terminal Services must run on PC, but FM server can be anything. Clients must be MacX or PC.

[Steve T.]

Hi, Stanley! I guess doing it profesionally for a client and doing it for yourself is different, though, so in addition to the wisdom from the wizards above, make sure you (or the client) really want to put that information on the internet, and if so, make sure you guard it well if any of it's confidential. I would not trust stock FMP Web Security with credit card info and social security numbers. I would stick w/FMP apps if that's what the staff is used to in the office and they like the full power of custom searches, sorts, and (as Unable mentioned) scripts unless they are 1-event safe.

If neither security or user-limitation is a major issue, then I say have a ball with setting up your first web db. I enjoy it and even folks with modest development/programming skill can put together amazing stuff relatively quickly and easily. The more time, the better, of course, and a lot depends upon how complex the needs are. If the users just do simple searches, then it's cake. Just remember, for each thing they want to be able to do, you have to write/create a means for them to do it via the web. Fortunately, the FMFORUMS folks tend to be eager to help!

--ST

[stanley]

Steve:

Thanks for the input. Because there's a fair amount of scripting involved already (this is a very complicated system that's been in place for two years) using web publishing just isn't going to hack it. Also, you mentioned a VERY important consideration, which is what the staff is used to. Dropping a new (i.e. via the web) method of getting their work done would be a disaster, and would entail daily/hourly tech support calls, all answerable by yours truly.

Thanks all for the input.

-Stanley