Re: Extension modules

Phil Driscoll wrote: > I need to know which of the extension dlls are 'production quality' - ie > which ones work with no problems. > Also, for those which work, I need to know if there are any settings in > php.ini which need to be configured. > > Any information on the above would be appreciated. I (personally) would consider the oci extensions at least "close" to production quality. But they are very tricky to install AND depend somewhat on web-server software (Apache vs. IIS, let's say). Vince Lamonica and I both have OCI8 running with good results, and I'd be happy to help in getting the OCI8 loaded correctly in you installer. Vince, when you get a draft of the "how-to" ready, let me review and we'll pass that along. Phil, here's a quick list of "options" to watch out for... we'll give you the tricky spots when our how-to is ready: 1) Oracle Client Installation v8.1.6 - must be installed for reliable extension loading - need to know WHERE the client is installed (ORACLE_HOME directory) and WHERE their Net8 database definition file is (TNS_ADMIN setting for location of TNSNAMES.ORA file). The BIN directory off of ORACLE_HOME also must be in the system path. 2) Apache 1.3.12 vs. IIS (haven't tried running on other servers, but might be similar). Vince & I both run Apache Win32 and several lines must be added to Apache's httpd.conf for proper connections through SetEnv directives. Under IIS, I suppose having the environment variables set in the system would do, as IIS has more robust tie-in to NT environment and registry. I haven't tried OCI8 under IIS but we're in the process of working with other IIS users to install oci8 extension and will know more soon. Anyone else on the list working fine with oci8 and IIS(4 or 5)? 3) Module/Filter vs. CGI - I know the Apache Module and OCI8 work well together (with php v4.0.2). Also, CGI has tended to be the most stable environment all around. From an OCI8 perspective, under Apache module, the biggest concern is path-naming in both httpd.conf and php.ini. All paths SHOULD be set in a unix-style convention - example "c:/php/extensions" - with front-slashes as path separators. There are some other "tricky" issues which can't directly be address by the install, but might be included in a distributed README.OCI8 (Oracle service naming, local vs. LAN Oracle installations, etc.) -- Andy Hoffman Web Developer Bristol-Myers Squibb email: andy.hoffman@bms.com