This section contains notes and hints specific to Sun Java System Web Server,
Sun ONE Web Server, iPlanet and Netscape server installs of PHP on Sun Solaris.
From PHP 4.3.3 on you can use PHP scripts with the
NSAPI module to
generate custom directory
listings and error pages. Additional functions for Apache
compatibility are also available. For support in current webservers read
the note about subrequests.
You can find more information about setting up PHP for the Netscape
Enterprise Server (NES) here:
http://benoit.noss.free.fr/php/install-php4.html
To build PHP with Sun JSWS/Sun ONE WS/iPlanet/Netscape webservers,
enter the proper install directory for the
--with-nsapi=[DIR]
option. The default directory is usually
/opt/netscape/suitespot/.
Please also read /php-xxx-version/sapi/nsapi/nsapi-readme.txt.
Install the following packages from
http://www.sunfreeware.com/ or another download site:
autoconf-2.13 |
automake-1.4 |
bison-1_25-sol26-sparc-local |
flex-2_5_4a-sol26-sparc-local |
gcc-2_95_2-sol26-sparc-local |
gzip-1.2.4-sol26-sparc-local |
m4-1_4-sol26-sparc-local |
make-3_76_1-sol26-sparc-local |
mysql-3.23.24-beta (if you want mysql support)
|
perl-5_005_03-sol26-sparc-local |
tar-1.13 (GNU tar) |
Make sure your path includes the proper directories
PATH=.:/usr/local/bin:/usr/sbin:/usr/bin:/usr/ccs/bin
and make it available to your system export PATH.
gunzip php-x.x.x.tar.gz (if you have a .gz dist,
otherwise go to 4).
tar xvf php-x.x.x.tar
Change to your extracted PHP directory:
cd ../php-x.x.x
For the following step, make sure
/opt/netscape/suitespot/ is
where your netscape server is installed. Otherwise, change to the
correct path and run:
./configure --with-mysql=/usr/local/mysql \
--with-nsapi=/opt/netscape/suitespot/ \
--enable-libgcc |
Run make followed by make install.
After performing the base install and reading the appropriate readme file,
you may need to perform some additional configuration steps.
Note:
The stacksize that PHP uses depends on the configuration of the webserver. If you get
crashes with very large PHP scripts, it is recommended to raise it with the Admin Server
(in the section "MAGNUS EDITOR").
Important when writing PHP scripts is the fact that Sun JSWS/Sun ONE
WS/iPlanet/Netscape is a multithreaded web server. Because of that all
requests are running in the same process space (the space of the webserver
itself) and this space has only one environment. If you want to get CGI
variables like PATH_INFO, HTTP_HOST
etc. it is not the correct way to try this in the old PHP 3.x way with
getenv() or a similar way (register globals to
environment, $_ENV). You would only get the environment
of the running webserver without any valid CGI variables!
Note:
Why are there (invalid) CGI variables in the environment?
Answer: This is because you started the webserver process from the admin server
which runs the startup script of the webserver, you wanted to start, as a CGI script
(a CGI script inside of the admin server!). This is why the environment of
the started webserver has some CGI environment variables in it. You can test
this by starting the webserver not from the administration server. Use
the command line as root user and start it manually - you will see
there are no CGI-like environment variables.
Simply change your scripts to get CGI variables in the correct way for
PHP 4.x by using the superglobal $_SERVER. If you have
older scripts which use $HTTP_HOST, etc., you should turn
on register_globals in php.ini and change the variable
order too (important: remove "E" from it,
because you do not need the environment here):
variables_order = "GPCS"
register_globals = On |
You can use PHP to generate the error pages for "404 Not Found"
or similar. Add the following line to the object in obj.conf for
every error page you want to overwrite:
Error fn="php4_execute" code=XXX script="/path/to/script.php" [inikey=value inikey=value...] |
where
XXX is the HTTP error code. Please delete
any other
Error directives which could interfere with yours.
If you want to place a page for all errors that could exist, leave
the
code parameter out. Your script can get the HTTP status code
with
$_SERVER['ERROR_TYPE'].
Another possibility is to generate self-made directory listings.
Just create a PHP script which displays a directory listing and
replace the corresponding default Service line for
type="magnus-internal/directory"
in obj.conf with the following:
Service fn="php4_execute" type="magnus-internal/directory" script="/path/to/script.php" [inikey=value inikey=value...] |
For both error and directory listing pages the original URI and
translated URI are in the variables
$_SERVER['PATH_INFO'] and
$_SERVER['PATH_TRANSLATED'].
The NSAPI module now supports the nsapi_virtual() function
(alias: virtual())
to make subrequests on the webserver and insert the result in the webpage.
This function uses some undocumented features from the NSAPI library.
On Unix the module automatically looks for the needed functions and uses
them if available. If not, nsapi_virtual() is disabled.