tag:blogger.com,1999:blog-8884584404576003487.post3456501020085941589..comments2024-02-29T09:43:12.251-05:00Comments on ORACLENERD: OBIEE: Physical Development Environmentoraclenerdhttp://www.blogger.com/profile/12412013306950057961noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8884584404576003487.post-3710936566186751842010-05-07T11:49:13.454-04:002010-05-07T11:49:13.454-04:00i like thisi like thisd singhhttp://www.oracledba.in/noreply@blogger.comtag:blogger.com,1999:blog-8884584404576003487.post-85959728472438448492010-05-04T16:56:24.662-04:002010-05-04T16:56:24.662-04:00Chet:
The link you mention from our blog, http://...Chet:<br /><br />The link you mention from our blog, http://www.rittmanmead.com/2009/12/02/obiee-software-configuration-management-part-3-version-controlling-the-project/, does explain one way to do merges into the RPD, but it's not nearly as powerful as using Subversion on a text file.<br /><br />There are some ways to mitigate the bottleneck issue, but not solve it completely. You can have the RPD in online mode on a dev environment, using the multi-user development functionality to lock portions of the RPD while they are worked on, and the unlocked once those pieces are complete. This just constrains multi-user development for all intents and purposes... but it does keep users from squashing changes created by others. Then, the COPY AS option in the Administrator can be used to write the current RPD file to a Subversion local directory periodically, and checked in.<br /><br />There are partially-supported ways of merging using UDML. This is outside my area of expertise... but I now of clients that are doing this. Perhaps some one with information on this could post... but if it sounds interesting, I could get a little more detail and pass it on to you.Stewart Brysonhttps://www.blogger.com/profile/16904522901298746643noreply@blogger.comtag:blogger.com,1999:blog-8884584404576003487.post-60352394086727311102010-05-03T03:03:11.877-04:002010-05-03T03:03:11.877-04:00Hey chet,
Your line "the RPD can be a bottle...Hey chet,<br /><br />Your line "the RPD can be a bottleneck" sums it up for me - it just doesn't play well with the typical dev/SCM methodology. <br /><br />This is Déjà vu for me -- we have the exact same problem here and I spent several weeks a few months ago scratching my head over it. Aside from the hair loss, the conclusion I came to was that merging RPDs is to be avoided. We're also upgrading OBIA and the upgrade process includes a merge, and boy, it HURT.<br /><br />Maybe you could hack something together now with an nqxudmlgen of each RPD and a diff and then nqxudmlexe but it's majorly unsupported and I'm not sure if the hacking necessary would be worth it (or even work). OBIEE 11g is supposed to have an XML(?) API for the RPD, maybe this will be the answer to our prayers. <br /><br />I'm interested in your idea though. Maybe you should try a POC with it, because just as with Merging not being as simple as its functional name suggests, perhaps there'd be some serious Gotchas using Import to join the RPDs into the DEV stage.<br />Plus as you say -- shared dimensions etc would be difficult to maintain across multiple development instances.Anonymousnoreply@blogger.com