Posts Tagged ‘IIS’

Simplify WCI 10gR4 installs in IIS7 by dodging this bug

Monday, September 21st, 2015

Years ago I wrote about manually deploying WCI to IIS7 because the installer simply fails to do it, without reporting any error. In doing a recent 10gR4 upgrade, I came across this issue again and found that it’s actually a documented bug (login required):

When installing WebCenter Interaction 10.3.3 on IIS7 on Windows 2008 Server, the installer fails to configure the IIS application pool, web site, and virtual directory. The installer returns no error and there are none in the Windows event logs.

Turns out that the workaround is simple enough to get the installer to automatically deploy the portal to IIS7 – just enable the “IIS 6 Management Compatibility” service:


WebCenter Interaction and Internet Explorer 11

Tuesday, April 7th, 2015

In our last post, we hacked support for IE11 into Collaboration Server. Today, we’ll look at a small tweak to fix some UI issues with Internet Explorer 11, because, you know, technically Oracle WebCenter Interaction only supports up to IE9 (forget about Chrome!):

Microsoft Internet Explorer 6.0, 6.0 SP1, 6.0 SP2 (on XP), 7.0 (on Vista), 7.0 SP2 (on XP SP2), or 8.0

Internet Explorer has followed a long tradition of screwing up web sites by changing the way it renders pages, and IE11 is no exception. For example, one of the sites I manage started rendering a squished navigation bar in IE11:

Rather than trying to hack code or anything, we’re left with a pretty good solution: force IE to use its old IE9 rendering engine. You do this by adding an HTTP response header to your portal pages:

X-UA-Compatible: IE=EmulateIE9


Turn WebEdit OFF in IIS for WebCenter Interaction Collaboration Server

Monday, March 25th, 2013

We’ve had a good run with WebEdit functionality in the old Plumtree / ALUI / WebCenter Collaboration Server. There comes a time, though, when the pain/cost is increasing and the benefit/payback of fixing the issues is decreasing.

Such was the case at a client was getting this security prompt every time they tried to open an Office document that had been uploaded to Collaboration server through WCI:

It turns out that when Office 2010 opens a document from a web page, the first thing it tries to do after downloading the document is execute a WebDAV request (PROPFIND) to that server:
This makes all kinds of sense from Microsoft’s perspective – if a Word document is opened from a web site, first check to see if it’s a SHAREPOINT site, right? That way Office can enable all those neat WebEdit/WebDAV features automatically.

The problem was that IIS was choking on this request because Windows Integrated Authentication was prompting for the user’s domain credentials – and even if the proper user/pass was supplied to IIS, the portal still had no idea what to do with those WebDAV verbs.

The solution: just kill off WebDAV entirely in this portal instance. You do this by changing the verbs for the portal virtual directory (.pt extension) to only accept the verbs “GET,HEAD,POST”:


This way, even if Office does try to check the WebDAV verbs, IIS is going to deny those requests before even letting them through to the portal, which probably wouldn’t know what to do with them anyway.

Running Plumtree Portal on IIS7 and Windows Server 2008

Wednesday, September 19th, 2012

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:
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:
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\register-configuration-manager.xml:191: 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… (more…)

Running WebCenter Interaction on 64-bit Windows

Monday, June 18th, 2012

Technically, WCI 10gR3 and previous versions aren’t supported on 64-bit Windows. WebCenter Interaction 10gR4 does support 64-bit, but not every item in the stack got a refresh (ahem, Publisher).

But, aside from this blog, which is running WordPress, the rest of this site has been running 10gR3 on Windows 64-bit without a problem. Everything pretty much installs normally, with the exception of the portal itself on IIS. In order to get that running, you’ll need to run a tweak or two. Specifically, you’re going to want to configure IIS to run 32-bit applications.

There’s a Microsoft Knowledge Base article on how this is done. Basically you just need to:

1) Enable 32-bit applications

cscript \inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1

2) Install and register 32-bit .NET 2.0

\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -lk

3) Enable 32-bit .NET 2.0 in IIS Configuration manager