Deploy two copies of analytics.ear in OBIEE 11g

3238367

We have a requirement to access the same BI environment from two different URIs

1.  http://www.mywebsite.com:9704/apples/reports/analytics/saw.dll?bieehome&startPage=1

2.  http://www.mywebsite.com:9704/oranges/reports/analytics/saw.dll?bieehome&startPage=1

The context root of analytics.ear was set to /apples/reports/analytics/

We created a copy of analytics.ear and called it analytics2.ear

We changed the context root to /oranges/reports/analytics/ and deployed to Weblogic.

Everything seems to work as expected.  My question is, are there any disadvantages to have two copies of analytics.ear deployed?

Thanks for your help.

rmoff

Are there any disadvantages to have two copies of analytics.ear deployed?

It's a pretty non-standard configuration, so has associated risk and maintenance overheads.

What's the rationale behind wanting the two deployments, if both are hitting the same OBIEE backend?

3238367

The users will be accessing the BI same system but its important to the business that the URL follows their existing structure.

In the given example apples and oranges are two totally different systems but need access to the same reports.

Thanks again for your help.

rmoff

I'd be inclined to leave OBIEE vanilla, and stick nginx or apache on the front to just proxy the URL paths that you need. Plus you can then you have the option to do compression on static resources, which will often help with performance.

Fewer moving parts, much more standard. Otherwise you're going to have a sod of a time each time you want to patch or upgrade your system.

3238367

Thanks again rmoff!  What about using virtual hosts in Weblogic?  Its not something I'm familiar with.  Is this the kind of thing virtual hosts are used for?

Cheers