If you're connecting over 100 users you should be looking at investing in a custom web publishing front end to your database.
If you need WebDirect, the only way to pass 100 connections is to have multiple servers that sync with each other.
100 connections is concurrent. It can support a lot more users, just limited to 100 people connected at once.
As in FMP web publishing or something else?
Any quick diagram on how you might architect that?
yes, as in custom web publishing using the filemaker PHP API. You can support thousands of users without the need for concurrent connection licenses or multiple servers. The tradeoff is that you need to invest a lot more time in front-end development to essentially rewrite your entire UI.
Correction: CWP =
1. XML & any web app to process.
2. FM API for PHP -> XML and PHP with a canned set of classes for communication with FMServer
3. xDBC & any web app to process
BTW research fx.php for alternate PHP classes for XML from FMServer.
-- sent from myPhone --
Thanks for your reply.
There will around 500 - 600 users connecting at once.As of now,we cannot invest our time on CWP development.
Can you please help me to know the process of syncing between the servers and the multiple instance concept in server?
Yes, this sounds like a critical scaling issue that has always kept me away from FMS for Internet (vs. Intranet) applications.
And, it sounds like FM doesn't have a ready answer for this issue? Considering how much you paid for the 100 licenses (>$20K for a stand-alone license with 100 concurrent connections), it's hard to believe that there isn't a ready-to-roll solution from FM.
If I'm right, and FM can't quickly scale you up, you may have to find time to invest in another approach. I've not used CWP (Beverly is the expert here), but I'm not sure how even that approach would free you from the hard limit of 100 connections. I'm assuming, using CWP, you would have to do some type of processing on the other web application (to free up needing to contact FMS so much) and just pass some requests on to FileMaker Server.
Unfortunately, for the xDBC approach, FMS only supports 50 simultaneous ODBC/JDBC connections, so you're limited there too.
The total number of concurrent users is a critical question to ask at the beginning of a project given FM's latest (version 13+) pricing model ($$$).
Bev is right where CWP has multiple meanings, however as a PHP dev I would highly advise AGAINST using the fx.php class due to past headaches with it.
Yeah, syncing six servers together would be a colossal mess, and I can't recommend it or advise you to go that route.
For 500-600 users you should not be looking at WebDirect.
YMMV (or YKMV)
any api can be a headache. Since the XML is not constrained to PHP or the API's you're welcome to do as you can.
WebDirect is getting more capable from version to version of FileMaker, and for some simple solutions I am convinced that a very well configured FileMaker server can easily handle more than 100 concurrent connections.
You should contact your FileMaker representative and ask about a license number allowing more concurrent licences. Of course you will need to buy them as well.
But I must admit that 500 concurrent users is a bit more than I believe will be a good idea for WebDirect ... unless the solution is very very very simple.
Could you please let us know a little bit about the solution?
I can only imagine how many there are around you .... depending on where you are having your office.
With WebDirect I agree that there are pretty tight limits to how many users you can have at once, at least with complicated/deep relational solutions.
But with CWP the limit is very high and FileMaker is performing splendid, especially in two server setups.
And we have build pretty complex and high visit websites by shooting an MySQL or MSSQL server in between FileMaker and the webserver. The overhead in development will usually be pretty easy to handle.
Interesting, but as I understand it, you're basically just creasing a regular Web App and then making xDBC (or other) calls to FMP elsewhere on the server, thereby working around the connection limit, correct?
So, if that's correct, then FMP is basically just a DB server like MySQL, etc., but without MySQL's performance.
Is it just me or does $20K+ seem ridiculous for 100 user connections?
$20k per year for 100 users is not a ridiculous price, given the full power of the filemaker platform.
Look at salesforce, for their "enterprise" CRM, it's $125/user/month, or $150,000 a year. And that price doesn't include a single minute of custom development, and will require you hours upon hours of work just to train your users how to use salesforce. Does $20,000 seem so ridiculous now?
Filemaker allows you to net a savings by building only what you need, and yes, it IS cheaper than a lot of other SaaS offerings, especially when scaled.
As for CWP as we've noted, yes, essentially you are using FileMaker as a backend database, similar to what MySQL would be used for. However, you still have the ability to connect other filemaker users (say for admin functions), and also the API supports filemaker specific classes, such as the execution of scripts and streaming container content, something that's disjoined from MySQL.