• Save
OBIEE11g  Multi User Development - MUD
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


OBIEE11g Multi User Development - MUD

Uploaded on

This document is part of OBIEE11g Certification course offered by Adiva Consulting Inc. ...

This document is part of OBIEE11g Certification course offered by Adiva Consulting Inc.

Start a great career as Oracle Business Intelligence Expert, Join Adiva Online BI Certification course. contact info@adivaconsulting.com

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 12

http://www.slideee.com 12

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Multi User Development OBIEE 11g Training www.adivaconsulting.com
  • 2. What is MUD • Facilitates the development of application metadata in enterprise-scale deployments • Application metadata is stored in a centralized metadata repository (RPD) file • Several developers work concurrently on subsets of the metadata and then merge these subsets back into a master OBIEE 11g Training metadata and then merge these subsets back into a master repository • No scope for overwriting each other’s work • Features include versioning, version history viewing and version comparison www.adivaconsulting.com
  • 3. Steps for MUD 1. Define “Projects” to break down rpd metadata to manageable and logical chunks 2. Set up shared network directory to act as MUD directory 3. Copy master rpd to the shared directory created above 4. Extract one/more projects to local machine 5. Make changed to the above extracted rpd Administrator Steps (One time setup) OBIEE 11g Training 5. Make changed to the above extracted rpd 6. Merge local changes to master rpd (locks the rpd) 7. Resolve conflicts 8. Save and check consistency 9. Publish changes Developer Steps www.adivaconsulting.com
  • 4. Creating Projects • File > Open > Offline • Manage > Projects>New Project • Provide a Name to the project • Select rpd objects to be part of the project and save OBIEE 11g Training www.adivaconsulting.com
  • 5. Setting up connection to MUD OBIEE 11g Training www.adivaconsulting.com
  • 6. “extractprojects” Utility • Command line utility for extracting OBIRR projects from MUD RPD • Located at the Dir : ORACLE_INSTANCE/bifoundation/OracleBIApplication/coreappli cation/setup • extractprojects -B base_repository_name -O output_repository_name {-I input_project_name} [-P OBIEE 11g Training output_repository_name {-I input_project_name} [-P repository_password] [-L] • extractprojects -B my_repos.rpd -O extract_repos.rpd -I project1 -I project2 Give password: my_rpd_password • Logging file ProjExtr.YYYYMMDD.HHMMSS.xml www.adivaconsulting.com
  • 7. MUD Menu Options • Compare with Original. Compares the working extracted local repository to the original extracted repository. When this option is selected, the Compare repositories dialog opens and lists all the changes made to the working extracted repository since you checked out the projects. • Merge Local Changes. Locks the master repository on the network multiuser directory to allow you to check in your changes. • Publish to Network. After you successfully merge your changes, the master OBIEE 11g Training • Publish to Network. After you successfully merge your changes, the master repository opens locally and the Publish to Network submenu item is available. When you select this option, the lock is removed, the repository is published, and the repository closes. • Undo Merge Local Changes. Rolls back any previously merged local changes, and leaves the repository checked out so that you can make additional changes and then merge your local changes again. This option is only available after you have already merged local changes. • Discard Local Changes. Any time after check out and before check in, you can discard your changes. When you select this option, the working repository closes without giving you an opportunity to save your work. www.adivaconsulting.com
  • 8. MUD Env Development Options • networkMUDdevoptfile.opt created to specify development options • In standard windows INI format • Hidden flag should be turned on for the file • To be managed “ONLY by MUD administrators” • OPT file contents and explanations : OBIEE 11g Training [Options] BuildNumber = Yes (Displays Version of rpd) Admin = weblogic;admin2 (Logins of MUD Admins) Mandatory Consistency Check = Yes (Forces CC when before Publish) Equalize During Merge = Yes (Forces Equalization during merge process) www.adivaconsulting.com
  • 9. Select a project from the main rpd and check out the subset rpd OBIEE 11g Training www.adivaconsulting.com
  • 10. Once checked out the this creates 2 rpd’s Metadata1 and originalMetadata1.rpd Metadata1.rpd opens up for modification, automatically Save the modifications and do consistency check OBIEE 11g Training www.adivaconsulting.com
  • 11. Once done, we can do a “Compare with original” to check the changes we made Do a “Merge Local Changes” to merge your work done earlier to main rpd This step LOCKS the rpd no developer can checkout/merge now OBIEE 11g Training www.adivaconsulting.com
  • 12. Once merged any conflicts present will show up in Merge Strategy window that pops up This needs to be resolved (keep Modified, keep Current changes or Merge Choices) Post this a 3 way merge happens (b/w Main rpd(original), originalMetadata1.rpd(current), Metadata1.rpd(modified)) www.adivaconsulting.com
  • 13. Once merged, the Main rpd opens up for review and consistency check Check you work in this main rpd Post this step, “Publish to Network”, rpd lock is released after publish Our changes are now visible to anyone who checks out now www.adivaconsulting.com