One final configuration file for php is needed. It is called GLASSFISHINSTALLDIR/domains/domain1/config/php.ini and should contain as a minimum this property value:

default_mimetype=text/html

Nothing more, nothing less. (If you are using a different GlassFish domain, just put this php.ini file in the domain's config directory.

So to recap, this is the files you should have on disk for configuring a PHP engine with GlassFish:

• GLASSFISHINSTALLDIR/
• lib/
• addons/
• quercus.jar (taken from the quercus-3_1-snap.war)
• resin-util.jar (taken form the quercus-3_1-snap.war)
• jsr223-api.jar (taken from Phobos CVS repository)
• domains/
• domain1/
• config/
• php.ini that contains default_mimetype=text/html

That's it...

Now using your favorite IDE (vi, or NetBeans), you can create a simple Web Application, and what you need to do is declare the PHP engine as a servlet and the location of the php.ini file, as follow:

<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
 version="2.5"> 
 <description>Caucho Technology's PHP Implementation, Running on GlassFish Java EE 5</description> 
 <servlet>
 <servlet-name>Quercus Servlet</servlet-name>
 <servlet-class>com.caucho.quercus.servlet.QuercusServlet</servlet-class>
 <init-param>
 <param-name>php-ini-file</param-name>
 <!-- the following value is a file name relative to the config directory 
 of the running GlassFish domain
 for example GLASSFISHINSTALLDIR/domains/domain1/config/ dir
 the php.ini file contains:
 default_mimetype=text/html 
 otherwise the current Quercus will give a NPE 
 (will be fixed soon from Caucho team)!--> 
  <param-value>php.ini</param-value>
 </init-param> 
 </servlet> 
 <servlet-mapping>
 <servlet-name>Quercus Servlet</servlet-name>
 <url-pattern>*.php</url-pattern>
 </servlet-mapping> 
 <welcome-file-list>
 <welcome-file>index.php</welcome-file>
</welcome-file-list>
</web-app>

Now you are all set: this Web App is PHP ready. Just Add PHP files under the web folder area, where you would put your JSPs files.

The simplest index.php can be:

<?php
 echo "Hello World";
?>

If you want to test the Java interoperability, you can go wild and crazy with this:

<?php
  echo "Hello mom, look I have a date: ";
  $a = new java("java.util.Date", 123);
  echo $a->toString();
?>

A  complex PHP application  is MediaWiki.  Untar the mediawiki PHP application archive inside the WEB-INF area of your web application, and redeploy it (if you are using NetBeans, you have almost nothing to do as NetBeans does an update of the deployed build area when files are modified in the source area). Activate the Web Application at the correct URL to see if MediaWiki 1.9.3 home page is correct as below:

Here is the PHP index page...

<?php
# Initialise common code
require_once('./includes/WebStart.php' );

# Initialize MediaWiki base class

require_once("includes/Wiki.php" );

$mediaWiki = new MediaWiki();

wfProfileIn('main-misc-setup' );

OutputPage::setEncodings();
# Not really used yet

# Query string fields

$action = $wgRequest->getVal( 'action', 'view' );
$title = $wgRequest->getVal( 'title' );

$wgTitle = $mediaWiki->checkInitialQueries( $title,$action,$wgOut,
$wgRequest, $wgContLang );

if ($wgTitle == NULL) {
  unset( $wgTitle );
}

#
# Send Ajax requests to the Ajax dispatcher.
#
if ( $wgUseAjax && $action == 'ajax' ) {   
 require_once( $IP . '/includes/AjaxDispatcher.php' ); 
 $dispatcher = new AjaxDispatcher();
 $dispatcher->performAction();
 $mediaWiki->restInPeace( $wgLoadBalancer );
 exit;
}

wfProfileOut('main-misc-setup' );
# Setting global variables in mediaWiki

$mediaWiki->setVal('Server', $wgServer );
$mediaWiki->setVal('DisableInternalSearch', $wgDisableInternalSearch );

$mediaWiki->setVal('action', $action );
$mediaWiki->setVal('SquidMaxage', $wgSquidMaxage );
$mediaWiki->setVal('EnableDublinCoreRdf', $wgEnableDublinCoreRdf );
$mediaWiki->setVal('EnableCreativeCommonsRdf', $wgEnableCreativeCommonsRdf );
$mediaWiki->setVal('CommandLineMode', $wgCommandLineMode );
$mediaWiki->setVal('UseExternalEditor', $wgUseExternalEditor );
$mediaWiki->setVal('DisabledActions', $wgDisabledActions );

$wgArticle = $mediaWiki->initialize ( $wgTitle, $wgOut, $wgUser, $wgRequest );
$mediaWiki->finalCleanup( $wgDeferredUpdateList, $wgLoadBalancer, $wgOut );

# Not sure when $wgPostCommitUpdateList gets set, so I keep this separate from finalCleanup

$mediaWiki->doUpdates($wgPostCommitUpdateList );
$mediaWiki->restInPeace($wgLoadBalancer );
?>

For more info, read http://quercus.caucho.com/ and the documentation under http://quercus.caucho.com/quercus-3.1/index.xtp .

The pure Java PHP engine is still an Alpha version, so please try it, break it and give feedback. The list of PHP applications the caucho team will be testing is very impressive:

• DokuWiki 2006-11-06
• Dragonfly CMS 9.0.6.1.7
• Drupal 4.7.4
• Gallery2 2.1.2
• Joomla 1.0.11
• MediaWiki 1.9
• Phorum 5.1.16a
• phpBB 2.0.21
• phpMyAdmin 2.9.1.1
• PHProjekt 5.2
• PHP-Nuke 7.9
• Wordpress 2.0.5
• Xoops 2.0.16

And do not forget that the Ajax jMaki project is PHP friendly, and JSP friendly, and Server Side JavaScript Phobos friendly...

A Plus,

Ludo