1 of 1 people found this helpful
Wether it breaks or not is irrelevant. You'd be without support from FMI and that is the deciding factor.
+1 for Wim's comment unless this is a development machine you are just playing with. If it is a production environment, I would not do it.
So why do you not want to upgrade to FM 13? It has been out for quite a while and it is not like this is a leading edge upgrade anymore. Really the only reason not to upgrade is that you have some old Windows XP or Mac OS X 10.6.8 clients applications where FMP 13 won't install. Then again, those operating sytems are not being supported by their respective software manufacturers anymore either. If you have machines that old, you've more than got your money's worth and really is time to upgrade because lots of hardware problems will be creaping in on machines that old.
It sounds like you are getting a nice new server with the latest OS, so why not also upgrade the clients (assuming that is your limitation)! <grin>
I would love to take everyone to fm 13 but here's the deal. One application running on filemaker server is using IWP and they could have 55 people connected at one time but don't have the necessary horse power for both a server AND a webserver to handle that traffic with Web Direct. So it's a catch 22. I'd love to go to 13 but it would be too restrictive as far as the IWP clients. And no time to develop in CWP.
Ahhh, that makes sense. I love WebDirect, but it maxes out at 50 concurrent users and even then, it prefers a two server setup where IIS is on another machine. WebDirect uses more horse power than IWP. It truly is a wonderful improvement over IWP for many user interface reasons. And you are correct that CWP takes a while to develop and make work well. CWP the most efficient use of the server performance wise, but takes the longest to develop.
Is there any reason not to use Windows Server 2008 R2? It actually is a pretty good OS. And you might see if your concurrent connections on 12 really are hitting 55. If they are not going over 50 at a time, then WebDirect would work nicely. Or see if a few of the WebDirect connecting people may want to have FileMaker Pro installed on their machine.
By the way, you say you are using IWP right now on FMS 12. Are you using IIS for IWP on that same machine right now? If so, then you wouldn't be adding a web service to the server, it already is running.
Yeah, the problem with 13 and our school system is that they prefer that two machine system and not just a system but beefed up system. Yes we are running the present 12 on a windows server 2003 with IIS running on that server. But it's older . . . Needed more from it.
We are going to 2008 R2 and run Filemaker Server 2012 Advanced. We'll see what the concurrent connections show.
If possible we could change to 13. Here's a question . . . what's the max concurrent connections of Web Direct possible on one machine? Expecially if that machine is a beefy machine?
Thanks again for your help.
The maximum concurrent connections in Web Direct is 50 according to the specifications. But I have a server from FileMaker that is "unrestricted" number of connections, which means you could do more, but there are no guarantees how well it will work and not a good idea to go over specifications in a production system. The nice thing about the 50 limit is that it is concurrent connections and if you have 55 users, it probalby is rather unlikely that all 55 would ever be logged in at once. Another issue is the licensing. IWP in FileMaker 12 had no additional cost. But in FMS 13, you have to pay for concurrent connections, meaning the licensing costs can go up a lot compared to IWP connections.
what's the max concurrent connections of Web Direct possible on one machine? Expecially if that machine is a beefy machine?
12-50 concurrent users = dedicated 12-core machine recommended. Depending on your desgin and what the users do, you'll need more than that.