Using 2 RPDs through same server and same OBIEE tool

Question

Hello Experts,

I am new to OBIEE tool , hence kindly bear with me if my query is basic in nature.

I am wondering about using 2 RPDs through same server and same OBIEE tool.

I have 2 RPD files, a.rpd and b.rpd. I need to switch between these 2 RPDs on same server and through same OBIEE tool.

Do I need to deploy both RPD on server to switch between these two through same OBIEE tool?

As per my own attempt, I can open both RPD file through Administration (obiee tool) : File --> Open-->Offline and without any deployment.

Is it mandatory to deploy both RPD at server to open it on line?

I guess I need to define 2 different ODBC system data sources for my repositories after deployment.

Thanks,

Rajneesh

Gianni Ceresa · Answer

You must keep in mind that the fully qualified name of objects aren't just the name you see. Your "address_d" isn't really named "address_d" but depends on what other object it is child of etc.

That's why it's possible to safely merge 2 RPD which would have different business models and different subject areas and different physical sources. In case of conflicts you must solve it: keep A or replace it with B. It's like when you have to manage conflicts in versioning control systems etc.

You never mentioned a version of OBIEE, so I assume the last one available 12.2.1.4 : the server doesn't use the RPD anymore, it works with XML files.

An RPD edited offline will never be available online even if you restart the OBIEE server. You have to download the RPD, edit it offline and upload it again. Only after an upload the new RPD will be available.

Working online allows you to do changes to the repository used by a server without needing to download, edit offline and upload. You do your changes online directly.

You don't need to work online, you can work online. It's up to you and what your processes looks like. It's also safer to work offline as you can do the whole work and then verify the RPD and only once you did everything you upload. If you work online and start doing changes but don't finish your work, people will be using an OBIEE system with a RPD half done. This could lead to errors. Also working online has some constraints because of how check in and out works.

Rajneesh S-Oracle · Answer

Hi Gianni,

Thanks for your expert advice, it helps !!!

May I know a bit more please to gain crystal clarity:

1) If I have common dimension or fact  tables between these 2 repositories (let's say address_d ), then during merge it will not allow me to rename the conflicting name like address_d1?

2) As per my own research ,  If a repository is not loaded/deployed to server and I open in offline mode, I can edit and save. If I restart the server the repository and changes will become available  to users. So I need to understand why we need online mode/load to server than working in offline mode(reading and editing repository from files)?

Thanks,

Rajneesh

Gianni Ceresa · Answer

You are correct that you can open both files locally, but as you say you opened them "offline", for that all you need is the file itself.

OBIEE has a single repository at any point in time. You can deploy A, use it and after a bit deploy B and use it. But it's either A or B and you will not have both on the server.

You can merge A and B together (the Admin tool allows you to do that and you obviously need unique names inside both or they will override things) if you want to have A+B deployed.

That's how the tool work, no workaround or anything: it's a key design principle of OBIEE, single repository.