Amazon is perfect for this.
You can build an instance of Windows Server 2008, install FileMaker Server and use it for testing your databases.
Best regards, Fabio.
You're marvelous. Thanks.
can you guys give me some suggestion for virtual server?
As you are only in development you can install Filemaker Server on your own machine.
If you really want to set up a virtual machine you can use VirtualBox which is a free download.
If I installed in my own private machine, then I can't access it because I closed when go to work. For virtual box I don't know it yet. Let me check. Thanks.
I have installed FMS on Windows Azure, with OS Windows Servers 2012. But currently no success yet on remotely connecting to FMS via Internet, but with the same virtual machine I have a FMP and was able to run the test page successfully. Anyone has similar issues but overcome it? Please share, thanks!
Thanks wimdecorte for the note on w2012 support. I went on to install fms on a windows server 2008 R2, following what was stated in the fms guide. Again, I still cannot connect to the database hosted from my fm go. I have added the endpoints 5003, 16000, 16001 to my virtual machine. But I am not sure what should I do to check the firewall. wimdecorte, could you point me to the place where the settings needs to be checked? Thanks!
Here's some resources from MS on firewall configs:
Still no idea what you mean with endpoints so that may be causing more problems than fixing them.
Keep in mind that there probably is another firwall between your VM and the internet, apart from the software firewall in Windows 2008. Perhaps that's the endpoint config you mention?
Thanks wimdecorte! This discussion has enriched me with more understanding on setting up FMS and navigating thru VM. I have just realized that my database address 10.78.204.16 is an internal address, and hence there was no way I can use that to connect to my FMS! I found the external address and finally able to connect FMS! HOORAY!!!
And your right that only port 5003 is required, because I experimented it by removing the inbound rule on the Windows Firewall that allows for this port and shortly after a connection error popped up on my ipad that connection with host was lost. Why I did this was I thought that by specifying endpoints for the virtual machine for port 5003 will suffice, and I was proven wrong. The support folks from Azure told me that endpoints are needed to open up ports. So in conclusion, not only the virtual machine needs to have these ports opened, but we also need to specify in Windows Server 2008 for its Firewall settings to open up the port as well.
Thanks very much for the continous sharing that helped me to overcome this huddle!