OBIEE 12C UI (Presentation Services) in Windows using IIS

Question

Hi Friends,

I am working on OBIEE 11g for past 7 Yrs. Now my client wants to upgrade the system to OBIEE 12C. Their requirement is to upgrade the system from OBIEE 11g in Windows to OBIEE 12c Linux.

But they want the "User Interface to be hosted on Windows Servers using Internet Information Services (IIS) and the Oracle WebLogic Plugin for IIS to avoid converting utilities and tools which have been developed using the .NET framework to support OBIEE applications."

Could anyone of you please explain me what they mean by UI to be hosted on Windows while the OBIEE is installed on Linux box ?, and how can we do that ?

Regards,

Suresh

Gianni Ceresa · Answer

If I'm not wrong there is a plugin for IIS which make IIS act as a proxy in front of weblogic. A bit like OHS (Oracle HTTP Server) which is just Apache acting as proxy.

I never set it up in IIS, but there was/is definitely a little plugin making this "proxy-like" setup.

So "UI hosted on Windows" sounds like a pretty poor way to define that  or just the impression a proxy give, but in the end the content is just on Weblogic like it has always been. Search for "Oracle WebLogic Server Proxy Plug-Ins" (a random link I found: https://docs.oracle.com/middleware/1212/webtier/PLGWL/isapi.htm#PLGWL4329) and the doc tell you how to set it up. As far as I remember based on what I saw it's fine to have it on 2 different server (so OBIEE on linux but having users accessing it via IIS on Windows Server).

Joel Acha · Answer

That requirement makes no sense at all as it sounds like they've built some .NET application in the past and want to continue using it even though they plan to move to a linux platform. OBIEE has a number of utilities which can be used to manage the underlying components rather than having to build this infrastructure in house.

[Deleted User] · Answer

Suresh

Just ask them if they want a custom GUI in .NET....or whether they want to fake requirements so they can justify switching to Microsoft.

Because otherwise that "requirement" makes no sense at all.