1. 22 Copyright © 2008, Oracle. All rights reserved. Multi-User Development

2. Copyright © 2008, Oracle. All rights reserved. 22 - 2 Objectives After completing this lesson, you should be able to: Set up an Oracle Business Intelligence (BI) multi-user development environment (MUDE) Describe the multi-user development environment functionality Develop a repository using multiple developers

3. Copyright © 2008, Oracle. All rights reserved. 22 - 3 Business Challenge By default, the Oracle BI repository development environment is not set up for multiple users. Multiple developers working in online mode lock each other out as they check out objects. This causes inefficiency and potential conflicts while other developers wait for access to the repository.

4. Copyright © 2008, Oracle. All rights reserved. 22 - 4 Business Solution: Oracle BI MUDE Oracle BI MUDE permits multiple users to work with the repository simultaneously: –Users edit local copies of the repository. –Changes are saved locally and then merged to the master repository. MUDE breaks the repository into manageable pieces known as projects. –Multiple users can work on the same or different projects. –Single users can improve efficiency by working on smaller subsets of the repository.

5. Copyright © 2008, Oracle. All rights reserved. 22 - 5 Oracle BI Repository Development Process Adheres to the classic Software Configuration Management (SCM) process: It is conceptually and functionally analogous to processes found in pure-play source control systems. Developers can check out, work on, and merge from the master code repository. Oracle BI enables and manages checkout, merging, conflict resolution, logging, code compares, version backups, and so on.

6. Copyright © 2008, Oracle. All rights reserved. 22 - 6 SCM Three-Way Merge Process to manage concurrent development –Highly restrictive alternative is serial development. Permits changes to the same file by multiple developers Requires merging and reconciliation: –Most merging is automatic; changes generally do not conflict. –Conflicts require manual intervention. Creates a fourth “merged” file based on two changed files, which are base-lined against a common parent file Original file Merged file File version 1 + File version 2 File version 2File version 1

7. Copyright © 2008, Oracle. All rights reserved. 22 - 7 Oracle BI Repository Three-Way Merge Conceptually identical to classic SCM three-way merge: Oracle BI repository is stored as a file (.rpd ). Merge is managed using the Administration Tool. Original.rpd Merged.rpd Current.rpd + Modified.rpd Modified.rpdCurrent.rpd

8. Copyright © 2008, Oracle. All rights reserved. 22 - 8 Multi-User Development Projects Projects: –Are subsets of repository metadata –Consist of Presentation layer catalogs and their associated business model logical facts, dimensions, groups, users, variables, and initialization blocks –Can overlap with other projects The best practice is to create projects of manageable size based on individual logical stars in the business model.

9. Copyright © 2008, Oracle. All rights reserved. 22 - 9 Overview: Oracle BI Multi-User Development The developer: 1.Checks out projects from the master repository 2.Makes changes in the local (current) repository 3.Merges the local changes 4.Publishes to the network Original.rpd Merged.rpd Current.rpd + Modified.rpd Modified.rpdCurrent.rpd Original Master.rpd New Master.rpd 1 2 3 4

10. Copyright © 2008, Oracle. All rights reserved. 22 - 10 ABC Example ABC wants multiple developers to be able to modify objects in the Inventory presentation catalog simultaneously.

11. Copyright © 2008, Oracle. All rights reserved. 22 - 11 Steps to Set Up an Oracle BI MUDE 1.Create projects. 2.Edit projects. 3.Set up a shared network directory. 4.Copy the master repository to the shared directory.

12. Copyright © 2008, Oracle. All rights reserved. 22 - 12 1. Create Projects Select Manage > Projects to open the Project Manager. Then select Action > New Project. Select presentation catalogs or logical fact tables in the catalogs. Selected objects are added to the project.

13. Copyright © 2008, Oracle. All rights reserved. 22 - 13 2. Edit Projects Remove unwanted fact tables from the project. Add other metadata (such as users, groups, or variables) to the project. Remove unwanted fact tables. Add other metadata to the project.

14. Copyright © 2008, Oracle. All rights reserved. 22 - 14 3. Set Up a Shared Network Directory The administrator must identify or create a shared network directory that all developers can access. All users must have access to the shared directory.

15. Copyright © 2008, Oracle. All rights reserved. 22 - 15 4. Copy the Master Repository to the Shared Directory Copy the master repository file and paste it in the directory that you have dedicated to multi-user development. Copy the master repository to the shared directory.

16. Copyright © 2008, Oracle. All rights reserved. 22 - 16 Making Changes in an Oracle BI MUDE 1.Point to the multi-user directory. 2.Check out projects. 3.Tasks performed by Administration Tool during checkout 4.Change metadata. 5.Multi-user options during development 6.Administration Tool tasks during check in 7.Check-in changes: Lock Information dialog box 8.Check-in changes: “Merge repositories” dialog box 9.Closing a repository before publishing to network 10.Publish to network. 11.Merge decisions. 12.Track project history.

17. Copyright © 2008, Oracle. All rights reserved. 22 - 17 1. Point to the Multi-User Directory Before checking out projects, each developer must set up the Administration Tool application to point to the multi-user development directory. Shared directory Username

18. Copyright © 2008, Oracle. All rights reserved. 22 - 18 2. Check Out Projects Select File > Multiuser > Checkout and select the desired project or projects. Select one or more projects to extract. Select master repository. Save extracted repository.

19. Copyright © 2008, Oracle. All rights reserved. 22 - 19 3. Administration Tool Tasks During Checkout Makes a temporary copy of the master repository in the local directory Saves a local copy of projects in the new repository in the local directory Saves a second local copy of projects in the new repository in the local directory with “original” as the prefix Deletes temporary copy of the master repository from the local directory Tracks transactions in a log Shared directory after extract Local directory after extract

20. Copyright © 2008, Oracle. All rights reserved. 22 - 20 4. Change Metadata Change metadata as you would during single-user development, with the following exceptions: Hierarchy definitions Project definitions Physical connection settings

21. Copyright © 2008, Oracle. All rights reserved. 22 - 21 5. Multi-User Options During Development The following multi-user options are enabled when the local, extracted repository is open: Compare with Original –Launches a dialog box that compares the local version of the original repository with the subset repository Discard Local Changes –Discards changes to local repository without checking in Merge Local Changes –Launches a dialog box to merge local changes with the master repository

22. Copyright © 2008, Oracle. All rights reserved. 22 - 22 6. Administration Tool Tasks During Checkin Locks the master repository to prevent other developers from attempting to merge at the same time Copies the master repository to the local directory to ensure that the developer merges with the most recent version

23. Copyright © 2008, Oracle. All rights reserved. 22 - 23 7. Checkin Changes: Lock Information Dialog Box Select File > Multiuser > Merge Local Changes to display the Lock Information dialog box.

24. Copyright © 2008, Oracle. All rights reserved. 22 - 24 8. Checkin Changes: “Merge repositories” Dialog Box After a developer successfully locks the master repository, the “Merge repositories” dialog box is displayed. At this point, changes are merged to the local copy of the shared repository.

25. Copyright © 2008, Oracle. All rights reserved. 22 - 25 9. Closing a Repository Before Publishing to Network If a developer attempts to close the local master repository before publishing it to the network or discarding local changes, the following dialog box is displayed:

26. Copyright © 2008, Oracle. All rights reserved. 22 - 26 10. Publish to Network Select File > Multiuser > Publish to Network. This publishes the merged repository to the network share as the new master, releases the lock on the master, and logs the event.

27. Copyright © 2008, Oracle. All rights reserved. 22 - 27 11. Merge Decisions The Regions table exists in the original and modified repositories but not in the current repository. Merge decision

28. Copyright © 2008, Oracle. All rights reserved. 22 - 28 12. Track Project History Log history is stored in a log viewer. 1. File > Multiuser > History 2. Select master repository. 3. User ID and password 4. Multi User History

29. Copyright © 2008, Oracle. All rights reserved. 22 - 29 History Menu Options Use menu options to navigate and view history. Details

30. Copyright © 2008, Oracle. All rights reserved. 22 - 30 Deleting History Items The Delete menu item is available only to Administrators defined in a hidden option file in the MUD directory. Hidden option fileStored in MUD directory

31. Copyright © 2008, Oracle. All rights reserved. 22 - 31 Summary In this lesson, you should have learned how to: Set up an Oracle BI multi-user development environment Describe multi-user development environment functionality Develop a repository using multiple developers

32. Copyright © 2008, Oracle. All rights reserved. 22 - 32 Practice 22-1 Overview: Setting Up a Multi-User Development Environment This practice covers the following topics: Creating projects Copying a master repository to a shared directory Setting a multi-user shared directory

33. Copyright © 2008, Oracle. All rights reserved. 22 - 33 Practice 22-2 Overview: Using a Multi-User Development Environment This practice covers the following topics: Checking out projects Modifying project metadata Checking in projects Publishing changes to the network Merging changes Checking project history

34. Copyright © 2008, Oracle. All rights reserved. 22 - 34