[FX.php List]One FMP DB Multiple Web Servers

Gjermund Gusland Thorsen ggt667 at gmail.com
Thu Oct 11 08:47:24 MDT 2007


You need to make a separat pool for recid that is not redundant.

Gjermund

On 10/11/07, Dale Bengston <dbengston at preservationstudio.com> wrote:
>
> Hi Gerry,
>
> I think you need to balance the risk of corruption with the ongoing task of
> synching separate databases and consolidation of the documents being managed
> from two sources. In my personal experience (and I can only speak for
> myself), corruption has never been an issue with data coming from the web.
> In fact, I believe it's much easier to filter and "clean" user input via the
> web than it is client-server. If all your data is coming from the web
> already, and this is just a matter of whether it comes from inside the
> firewall or outside, then the risk of data corruption is the same either
> way.
>
> I would suggest an alternative to duplicating and synching for your external
> users. I'm guessing the external population may have reduced access to your
> system, or it may make sense to restrict what they can get to. You could
> create a new database file, and create relationships from this
> basically-empty file to your main databases. Then you can use this new file
> to "filter" what is available to external web users,. The web-enabled
> database file would have no data itself; only relationships to the other
> files you want to expose outside the firewall.
>
> Hope this helps,
> Dale
>
>
> --
> Dale Bengston | Streamline Studio, LLC | dbengston at streamline-studio.com
> Member, FileMaker Business Alliance
>
>
>
>
> On Oct 11, 2007, at 6:32 AM, gerry.charest at agfa.com wrote:
>
>
> Thanks for the recommendation John.
>
>  Do you think the web served database is at greater risk of corruption?
> Would a good back up scheme do the same thing?
>
>
>
> <graycol.gif>John Funk <csinfo at comcast.net>
>
>
>
>
>
>
>
> John Funk <csinfo at comcast.net>
>  Sent by: fx.php_list-bounces at mail.iviking.org
>
> 10/10/2007 08:42 AM
> Please respond to
>  "FX.php Discussion List" <fx.php_list at mail.iviking.org>
> <ecblank.gif>
>
> To
> <ecblank.gif>
>  "FX.php Discussion List" <fx.php_list at mail.iviking.org>
> <ecblank.gif>
>
> cc
> <ecblank.gif>
>
> <ecblank.gif>
>
> Subject
> <ecblank.gif>
>  Re: [FX.php List]One FMP DB Multiple Web Servers
> <ecblank.gif>
> <ecblank.gif>
>  Gerry,
>
>  1. Can I support both internal and external web access from one FMP Server?
> - Yes, the router can be the firewall and port forwarding.
>
>  2. Should I connect to one data source or replicate the database outside
> the firewall? - see below
>
>  3. Should I implement an external only solution and have all users hit the
> external site? - see below
>
>
>  In my opinion you should copy of the database and have all the web users
> (internal and external) access that database. You can use the same FileMaker
> server but have the "web served" version" a dfferent name.
>  This way if the web accessed database crashes for ANY reason, your main
> database is safe. Of course you need to figure out the schedule of "syncing"
> the two if you have two way information. You also need to look at the
> traffic you may have from both sources.
>
>  John Funk
>  Critical Solution
>
>
>
>  On 10/10/07 6:04 AM, "gerry.charest at agfa.com" <gerry.charest at agfa.com>
> wrote:
>
>
> Hi all,
>
>  I'm trying to come to grips with an implementation strategy and could use
> your recommendations before I get started. I have a document management
> system based on FMP8 w/FX PHP Windows IIS (will be moving to 9 at some
> point). The solution is for internal users behind a firewall. We would like
> to extend the functionality to support external users moving access outside
> the firewall.
>
>  1. Can I support both internal and external web access from one FMP Server?
>  2. Should I connect to one data source or replicate the database outside
> the firewall?
>  3. Should I implement an external only solution and have all users hit the
> external site?
>
>  Any other input, suggestions, pitfalls, etc. are most welcome.
>
>  Best regards
>  Gerry Charest
>  ________________________________
> _______________________________________________
>  FX.php_List mailing list
>  FX.php_List at mail.iviking.org
>  http://www.iviking.org/mailman/listinfo/fx.php_list
> _______________________________________________
>  FX.php_List mailing list
>  FX.php_List at mail.iviking.org
>  http://www.iviking.org/mailman/listinfo/fx.php_list
>
> <graycol.gif>
> <pic12382.gif>
> <ecblank.gif>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>
>


More information about the FX.php_List mailing list