Network Admin needs advice on whether to install PHP+NT/IIS vs PHP+Apache over NT. The main motivator is using PHP to increase our flexibility.

My company operates its own internet, intranet and internal network based on NT/IIS/Office. We also have an AS400 connected to the network for company-wide DBs, applications, and data transfer.

We do NOT want to eliminate the NT/IIS environment, at least not now. Initially, I only plan to use PHP for intranet scripting to assist in handling forms processing, interfacing with the GDLib to enable graphing, and reporting/data exchange with the AS400. I do see us using PHP with OBDC or ? to directly exchange data with the AS400 databases.

What are the pros and cons of using PHP+NT/IIS versus PHP+Apache over NT. Also, if you are aware of any articles etc, I'd appreciate that too.

Bob

    Greetings,

    The only articles that I know of off the top of my head are printed articles in magazines I have. 🙁
    However, hopefully what I say will help you make a decision and not just spin you around in circles. 😛

    1. Apache
      Perhaps the most favorite of all the servers. Not just because it is open source (which is definitely a plus). It's stability is uncanny. It has excellent features such as being able to customize logs, the ability to customize it easily, easy install, and a few other things. Security is incredible. A fresh install without any tweaking is fine for intranet. Apache 1.x purrs like a kitten. Perhaps you are looking in to Apache 2.x since you heard that it was natively built on Windows? I would advise against it since it still has bugs to be worked out and PHP still does not work properly on Apache 2.x.

    2. IIS
      IIS has it's share of problems as you may have already found out. But, the latest IIS seems to have some nice features. It tries to take security first in that instead of leaving everything open as it did in the past, it closes everything and you have to enable what you wish to enable. (which Apache did do first . . .) It does add the nice gui configuration that Apache does not have which makes configuration easier. IIS works fine as far as I know with PHP with a few hiccups once in a while. It is native to Windows which makes it a little less likely to cause a fatal crash.
      [/list=1]
      I hope what I said was as much unbiased as possible. I myself use Apache for everything. My website runs Apache, my localhost runs Apache and that is what I am most familar with. However, I do know a thing or two about IIS and hopefully you can make a decision. Let me know if you need clarification or have any more questions.

      Thanks for the PHP+Apache vs PHP+NT/IIS. Given our ties to NT, I'd like feedback on two different approaches:

      1. Practicality of running an Apache server attached to a primary NT/IIS server. If this approach, then the Apache would be used only for forms handling, PHP, GD, and other specific functions in 'support' of the NT/IIS internet/intranet.

      2. In the NT/IIS environmnet, using PHP for intranet scripting to assist in handling forms processing, interfacing with the GDLib to enable graphing, and reporting/data exchange with the AS400, and PHP with OBDC/MDAC or ? to directly exchange data with the AS400 databases (DB2 and successor).

        Okay, first off, both are quite easy to do. Neither stretching the capabilities.

        1. This is very easy to implement and wouldn't require a whole lot of maintenance. Apache runs quite nicely on Windows. It's quite stable. I wouldn't run apache on windows to host to the outside world but Apache is great for intranet use. (I personally wouldn't try to host to the internet on Windows period due to it's instability but that's just my personal opinion. :p perhaps professional opinion as well . . . ah well. 🙂)

        2. Given that you are tied to NT (I mean no offense by that), IIS is a good idea (though so is Apache) IIS, as I stated above, can also handle this just fine. However, if go through ODBC first (and this is a Windows problem and not IIS related), it slows down the queries tremendously in terms of say 1 or 2 seconds if that much. But, it is noticeable. IIS will not have any problems with the requests you send it providing you set it up correctly.

          Thanks again. Any additional input / experience / differing opinions would also be appreciated, especially with hands-on experience in interfacing PHP/ODBC and AS400/ODBC. (look before I leap!)

            I have never had the opportunity to work with the AS400. 🙁 So I can't help you there. 🙁 As for PHP/ODBC, it's quite simple actually. php.net has some great stuff on odbc if you want to read up. Out of curiousity, which are you going with? Or has that been decided yet? (IIS or Apache)

              Given todays market and what appears to be the development trend, I see us in 2-4 years being in a complete AS400/Linux server/network environment. For now, though, staying in the NT/IIS world, but 'breaking out' of the MS world to use tools like PHP for flexibility. Funny how things seem to go full circle.

                Yes, it is kinda funny how things seem to do that. 🙂 Just a warning, Microsoft has already banned Perl from it's wireless dev. kits and vows to take similar action against any open source products. 🙁

                  ... just one more nail in their coffin.

                    Write a Reply...