This is an interface to a PHP interpreter engine and environment for theN WASD OpenVMS Web server. It is designed to be able to be used in standard CGIK and CGIplus/RTE persistent scripting modes. The persistent modes provide a N ~7x (yes, an approximately seven times) improvement in script activation timesO and reduced load on server and system. PHPWASD cannot be used interactively or O at the command line, it is only for scripting use. Note that this package does M not contain the PHP engine, that has to be obtained and installed separately. G
PHPWASD is linked against the CSWS (OpenVMS Apache) PHP interpreter I shareable image (although other comparable versions and images should be J possible, including the original CSWS PHP 1.0). It is anticipated that asO bugfixed and improved (or at least later) versions of these OpenVMS PHP engines K become available the PHPWASD interface will only require a relink to update (that's the plan anyway :^). M
Currently CSWS PHP is Alpha (AXP) only. The release notes state a minimum O requirement of VMS V7.2-2. PHPWASD has been developed and tested on VMS V7.3-1. (
, There is an issue with the CSWS v1.1 PHP kit ( CPQ-AXPVMS-CSWS_PHP-V0101--1.PCSI
B contains an initialization bug and requires the application of the 1 CPQ-AXPVMS-CSWS_PHP11_UPDATE-V0100--4.PCSI
; patch kit available from the HP OpenVMS site to be applied. 3 See Installation below. *
PHPWASD v1.1
For those who have used PHPWASD v1.0, please note that this kit has a K significantly different structure in line with changes introduced with WASD M v8.1. This effectively decouples the source and executable components of the kits.
4+
) Directory Purpose % HT_ROOT:[SRC.PHP] OSource code for PHPWASD. Contains nothing from the CSWS PHP kit. ) HT_ROOT:[PHP] NLocation of PHP_ROOT logical name. Executable components of the scriptingJ environment (e.g. PHPSHR.EXE, extension shareable images). The [.SCRIPTS]N directory could be used for .PHP files with appropropriate mappings. ) HT_ROOT:[CGI-BIN] NContains the .PHP script files. This may be changed (to [PHP.SCRIPTS] for example) via mappings. HT_ROOT:[AXP-BIN] /PHP interface; PHPWASD.EXE image.
# CSWS (OpenVMS Apache)
Currently (CSWS PHP V1.1) based on PHP 4.1.1. The procedureL INSTALL.COM will use the PCSI kit as a source of required files, extractingN and installing them in a HT_ROOT:[PHP] directory tree (that parallels the CSWSO tree). The following files are extracted from the CSWS PHP kit and placed into I the WASD directory structure. Of course there is no reason why this tree A cannot be relocated (with appropriate startup procedure changes).
4I'
C CSWS_PHP WASD F [APACHE.PHP.BIN]PHP.EXE HT_ROOT:[PHP.BIN] O [APACHE.PHP.BIN]PHPSHR.EXE HT_ROOT:[PHP.BIN] I [APACHE.PHP.EXTENSIONS]*.EXE HT_ROOT:[PHP.EXTENSIONS] [APACHE.PHP.SCRIPTS]*.PHP HT_ROOT:[PHP.SCRIPTS]
The CSWS PHP 1.1 kit contains a significant number of PHP extensions:
F BCMATH BZ2 CALENDAR CTYPE DBA EXIF B FTP ICONV LDAP MHASH OCI8 ODBC M OPENSSL ORACLE PCRE POSIX SESSION SOCKETS XML ZIP ZLIB: (shareable images in the format PHP_extension.EXE). !
Installation
$ RENAME HT_ROOT:[SRC]PHP.DIR HT_ROOT:[SRC]PHP10.DIR@
http://wasd.vsm.com.au/wasd/+ and install it as per the kit instructions. @
http://h71000.www7.hp.com/openvms/products/ips/apache/csws_patches.html%
$ @HT_ROOT:[SRC.PHP]INSTALL kit:[location]F Note that this performs a link-only build - full build instructions. )
$ @HT_ROOT:[SRC.PHP]INSTALL UPDATE111 kit:[location]>
With the default configuration PHP script files will need to be placed; into [CGI-BIN] (examples from [SRC.PHP]WEBSERVERSPY.PHP and [PHP.SCRIPTS]*.PHP). 5
$ @HT_ROOT:[SRC.PHP]PHP_STARTUP.COM9 (or the equivalent) to your system/Web startup procedures
Configure WASD
Server global configuration (HTTPD$CONFIG) is used to indicate which file L types should activate the PHP interpreter and how perform non-script access.
# HTTPD$CONFIG [DclScriptRunTime]# .PHP $CGI-BIN:[000000]PHPWASD.EXE [AddType] ( .INI text/plain initialization file .PHP text/plain PHP source .PHPS text/plain PHP source .PHTML text/plain PHP sourceN
There are various ways to employ the WASD PHP interpreter. It can be usedO in vanilla CGI mode, or in persistent CGIplus/RTE mode. Benchmarking indicates O the CGIplus/RTE use reduces activation time to 15% of CGI (yes, that's correct, N by a factor 7). There are subtle differences in the way CGIplus and RTE parseL and provide the PATH_INFO data. See the "WASD Scripting Overview"H for more detail. The following rules require the PHP script files to beI located in the site administrator controlled /cgi-bin/ path. This may be changed using appropriate rules. I
# HTTPD$MAP for CGI, CGIplus or RTE usage (perhaps for comparison) : exec+ /php-bin/* (cgi-bin:[000000]phpwasd.exe)/cgi-bin/* .. exec /cgi-bin/* /cgi-bin/*! exec+ /cgiplus-bin/* /cgi-bin/*J
or, to automatically map scripts ending in ".php" to the RTE engine *
# HTTPD$MAP for automatic RTE usage> if (!script-name:/php/*) map /cgi-bin/*.php* /php-bin/*.php*9 exec /php-bin/* (cgi-bin:[000000]phpwasd.exe)/cgi-bin/* .. exec /cgi-bin/* /cgi-bin/*! exec+ /cgiplus-bin/* /cgi-bin/*N
The following rules allow .PHP type files anywhere in the mapped directoryO structure to be executed. This means that any document author can script using N PHP. This may be what is desired but can be dangerous. PHP provides for thisF type of usage. Please familiarise yourself with it's requirements andI controls. As an additional safeguard it is suggested that PHP scripts be K executed under a non-server account. This is the default configuration for N WASD v8.1 and later. If not using the default setup it can also be done usingH the WASD PERSONA capabilities (see the "Technical Overview" if6 unfamiliar with this functionality and configuration). <
exec+ /web/*.php* /web/*.php* script=as=OTHER-ACCOUNTK
By default WASD validates query strings in it's own N inimitable fashion (correctly in the author's HO). This validation interferesJ with the requesting of the internally generated PHP and Zend logos (as areE included by the php_info.php script). To disable query string I validation by WASD include the following HTTPD$MAP rule at an appropriate ' location before mapping of PHP scripts. (
set /**.php* script=query=relaxed"
Configure PHP
See NOTE with introduction. K
The author of PHPWASD is only a PHP novice, so anything in this section M should be taken with a large pinch of salt. Any scripting environment should M be approached with due caution and diligence. Please ensure you are familiar H with PHP and it's security requirements in particular before betting the$ company on anything in this section. N
The PHP engine has a set of default configuration parameters and so can beM used without specific configuration. To change the specifics a configuration M file name PHP.INI may be provided. The default location of this for CSWS and WASD is
PHP_ROOT:[000000]PHP.INIA default version is provided in F
HT_ROOT:[SRC.PHP]PHP.INI( and may be copied to the above location. $
Example Scripts
After configuration the following scripts may be used to confirm the environment is functioning.
Performance
The performance of PHPWASD is quite respectable. This table shows some O results on the author's development system, a Digital AlphaStation 500/333 with M 1 CPU and 256MB running VMS V7.3-1, with WASD 8.1, CSWS 1.3 and CSWS PHP 1.1, A using the ApacheBench tool.
4%:
Environment Path Req/Sec WASD CGI &/cgi-bin/php_info.php
$ /cgi-bin/php_rules.php5
6WASD RTE &/php-bin/php_info.php "
$ /php-bin/php_rules.php34
52CSWS mod_php "/php/php_info.php "
/php/php_rules.php15
18
Command-line PHP
The PHPWASD.EXE engine interface is only suitable for scripting use. ItH cannot be used outside of the CGI environment and certainly not from theO command line. It is often useful to have a PHP tool that can be used in such a K manner and the CSWS kit provides one. To access this image assign a symbol 1 (foreign command) in the (SY)LOGIN.COM procedure. *
$ PHP = "$HT_ROOT:[PHP.BIN]PHP.EXE"O (This can also be used as a CGI scripting engine if desired. See PHPWASD.C for detail.)
Full Build
The PHPWASD kit comes with object code that allows the image to be linked P against the CSWS PHP shareable image. To compile the PHPWASD image at least theM CSWS PHP header files are required. Basically this means the full source kit 1 needs to be installed. This may be obtained from ª
http://www.openvms.compaq.com/openvms/products/ips/apache/csws_source.htmlJ and by default should be placed in HT_ROOT:[SRC.PHP.PHP...] although it is> possible to build with it located elsewhere. Please check theG BUILD_PHPWASD.COM procedure for detail.
Problems?
Unfortunately the author of the PHPWASD interface is such a PHP novice he M is not in any position to answer queries about PHP "programming" or J usage. If there's an obvious behavioural problem with PHPWASD (preferably> diagnosed by someone with PHP experience) then he's it though. $
Acknowlegements
Thanks to OpenVMS Engineering and the CSWS team for their efforts on PHPO and Web technologies in general. Thanks also to the efforts of Dave Jones with F his PHP port (usable with PHPWASD v1.0). Of course, thanks to the PHP development team! (