I have a home network of machines with different static (not dynamic) IPs.
Is there any reason why I can't run PHP, Apache and MySQL with the SE db on my Mac G5 OS 10.4.9, and then run DCS, MP and ODBC software on my Windows XP?
Do these things all need to be on the same machine?
Installation question
Moderator: SEOW Developers
-
IV/JG7_4Shades
- Posts: 2237
- Joined: Mon 08 Jan 2007 11:10 pm
- Location: Perth, Western Australia
Hi MadMonk,
SEOW is designed to be distributable, in the sense that different components can reside on different machines. However, for the installation to be efficient, administrators should take care to arrange things sensibly. Maybe a little background information could be useful here.
SEDB and MySQL
The only role that MySQL has to play in SEOW is to make the SEDB database visible to other SEOW component applications. MySQL is a server technology, that is it can expose a database to remote connections. This means that Machine A on the internet can connect to a a SEOW database on MySQL server Machine B, no matter how far apart the two machines A and B are. Nice! But not necessarily efficient!! Note that remote connections to MySQL servers are usually enabled using the "%" wildcard for remote hostnames.
MP (and PHP and web servers)
The MP is just a collection of PHP scripts used to present a GUI interface to mission planners. It needs a web server to interpret the PHP scripts, and the PHP performs its own connection to the SEOW database, wherever that may be. It is perfectly feasible to run the MP (+web server+PHP) on a separate machine to where the SEDB lives. This works, but is slow, basically because each request to SEDB has to transit the ping time between the MP machine and the SEDB machine. Best to keep MP+webserver+PHP on the same machine as SEDB, if possible.
SEDCS
SEDCS is the admin tool that builds and analyzes missions. It needs MyODBC and .NET Framework 2.0 to be installed on the machine that runs SEDCS (nowhere else). The SEDCS machine can be anywhere on the internet, but greatest speed is obtained if SEDCS is installed on the same machine as SEDB/MySQL. This is because SEDCS, like MP, performs many database queries in each Build/Analyze operation; if SEDB is very close to SEDCS, then the operations run fast.
OK, to answer your question MadMonk, NO, there is no reason why you cannot split up components between different machines. However, only do this if the performance hits will not be a problem for you. Also, as outlined above, there is no sensible reason to separate MP from PHP, since MP needs a local PHP installation to run. Same for Apache and MP, or any other web server you choose.
FYI, my gaming machine runs MySQL, Apache, PHP, MP, SEDCS plus MSOffice and anything else you can think of, and still runs IL-2 fine.
Cheers,
4Shades
SEOW is designed to be distributable, in the sense that different components can reside on different machines. However, for the installation to be efficient, administrators should take care to arrange things sensibly. Maybe a little background information could be useful here.
SEDB and MySQL
The only role that MySQL has to play in SEOW is to make the SEDB database visible to other SEOW component applications. MySQL is a server technology, that is it can expose a database to remote connections. This means that Machine A on the internet can connect to a a SEOW database on MySQL server Machine B, no matter how far apart the two machines A and B are. Nice! But not necessarily efficient!! Note that remote connections to MySQL servers are usually enabled using the "%" wildcard for remote hostnames.
MP (and PHP and web servers)
The MP is just a collection of PHP scripts used to present a GUI interface to mission planners. It needs a web server to interpret the PHP scripts, and the PHP performs its own connection to the SEOW database, wherever that may be. It is perfectly feasible to run the MP (+web server+PHP) on a separate machine to where the SEDB lives. This works, but is slow, basically because each request to SEDB has to transit the ping time between the MP machine and the SEDB machine. Best to keep MP+webserver+PHP on the same machine as SEDB, if possible.
SEDCS
SEDCS is the admin tool that builds and analyzes missions. It needs MyODBC and .NET Framework 2.0 to be installed on the machine that runs SEDCS (nowhere else). The SEDCS machine can be anywhere on the internet, but greatest speed is obtained if SEDCS is installed on the same machine as SEDB/MySQL. This is because SEDCS, like MP, performs many database queries in each Build/Analyze operation; if SEDB is very close to SEDCS, then the operations run fast.
OK, to answer your question MadMonk, NO, there is no reason why you cannot split up components between different machines. However, only do this if the performance hits will not be a problem for you. Also, as outlined above, there is no sensible reason to separate MP from PHP, since MP needs a local PHP installation to run. Same for Apache and MP, or any other web server you choose.
FYI, my gaming machine runs MySQL, Apache, PHP, MP, SEDCS plus MSOffice and anything else you can think of, and still runs IL-2 fine.
Cheers,
4Shades
IV/JG7_4Shades
SEOW Developer
SEOW Developer
4Shades,
Thanks for this excellent explanation. What you're doing with SEOW is extremely impressive.
I will go back to my original plan -- running the whole thing on my XP machine. I've worked with Apache in the past, but MySQL is completely new territory, and very confusing.
I'm using .NET 3.0 BTW. Any problems with that? Thanks again.
MadMonk
Thanks for this excellent explanation. What you're doing with SEOW is extremely impressive.
I will go back to my original plan -- running the whole thing on my XP machine. I've worked with Apache in the past, but MySQL is completely new territory, and very confusing.
I'm using .NET 3.0 BTW. Any problems with that? Thanks again.
MadMonk
-
IV/JG7_4Shades
- Posts: 2237
- Joined: Mon 08 Jan 2007 11:10 pm
- Location: Perth, Western Australia