Running Plumtree Portal on IIS7 and Windows Server 2008

The latest version of WebCenter Interaction (aka Neo, or 10gR4) officially added support for IIS7 and Windows Server 2008. But WCI 10gR3 – or (gasp!) Aqualogic User Interaction or Plumtree don’t since IIS 7 didn’t exist way back then. We’ve discussed how to get these older revisions working on 64-bit Windows, but many of you don’t have the luxury of upgrading Plumtree or have cancelled your support and maintenance contracts (and, if you haven’t, why not?) .

Still, time marches on, new application servers and operating systems are introduced, and your server team is antsy to get you to upgrade what you can. So, today’s post is about getting older versions of WCI working on IIS7 and Windows Server 2008. It’s – of course – not officially supported, but from my testing with WCI 10gR3 it seems to work OK. Your mileage may vary, and I can’t say I’ve actually supported a production environment running 10gR3 in this configuration yet, so proceed at your own risk.

The problem starts with the portal installer – you’re likely to see something like the following lines in your error logs:

“E:\bea\alui\installlogs\portalappserver_deployment.log”(51,13): [echo] ERROR: Web Site Default Web Site does not exist. Virtual directory cannot be created.
“E:\bea\alui\installlogs\WebCenter_Interaction_InstallLog.log”(38038,51): Additional Notes: FATAL ERROR – ANT post-installation action returned an error. See e:\bea\alui\uninstall\ptportal\10.3.0\register\configmgr_config-setup.log for details.
ANT Post-install Check:
Status: FATAL ERROR
Additional Notes: FATAL ERROR – ANT post-installation action returned an error. See e:\bea\alui\uninstall\ptportal\10.3.0\register\configmgr_config-setup.log for details.
ANT Post-install Check:
Status: FATAL ERROR
Additional Notes: FATAL ERROR – ANT post-installation action returned an error. See e:\bea\alui\uninstall\ptportal\10.3.0\register\configmgr_setup-service.log for details.
e:\bea\alui\uninstall\ptportal\10.3.0\register\configmgr_setup-service.log:
BUILD FAILED
E:\bea\alui\uninstall\ptportal\10.3.0\register\register-configuration-manager.xml:191: java.io.FileNotFoundException: E:\bea\alui\configmgr\2.0\bin\configmgr.url (The system cannot find the path specified)

Basically, this is telling you that the installer wasn’t able to deploy the web app to IIS7. But, it does copy all of the appropriate files, so they’re ready to be deployed manually. Read on for the steps to get started in getting your old portal working with the latest IIS Application Server…

In order to prevent adding too many additional variables, we’re going to run the portal code in 32-bit mode using .NET 2.0. So, after installing .NET 2.0, run the following two commands:

cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
C:\Windows\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis.exe -i

Now, we need to deploy the portal server web application:
1. Right-click on “Default Web Site” and select “Add Application”; pick “Classic .NET AppPool”, and enter the portal path:

2. If the .NET 2.0 handler hasn’t been registered, double-click “Handler Mappings”, then “Add Script Map”. Register *.pt as a script pointing to your .NET 2.0 filter at C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll. Under “Request Restrictions”, select Verbs and add:
GET, HEAD, POST, OPTIONS, PROPFIND, PROPPATCH, MKCOL, LOCK, UNLOCK, PUT, DELETE, COPY, MOVE

This will add the following to your %ALUI%\ptportal\10.3.0\ webapp\portal\web\ Web.config file:

    <system.webServer>
        <handlers>
            <add name="WCI" path="*.pt" verb="GET, HEAD, POST, OPTIONS, PROPFIND, PROPPATCH, MKCOL, LOCK, UNLOCK, PUT, DELETE, COPY, MOVE" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.NET\Framework\ v2.0.50727\aspnet_isapi.dll" resourceType="Unspecified" preCondition="classicMode,runtimeVersionv2.0,bitness32" />
        </handlers>
    </system.webServer>

3. Next, change the portal’s application pool to use “Classic .NET AppPool”. Microsoft recommends using Integration Mode in IIS7, but remember, we’re striving for backwards compatibility here – if you have the luxury of upgrading to WCI 10gR4, then you’ll be able to use this new mode.

4. Finally, add the imageserver virtual directory by right-clicking on “Default Web Site” again:

… and that should do it!

Tags: , , , , , ,

Leave a Reply