In the Multiuser tab, for Multiuser development directory, enter the full path to In the Full Name field, type your complete name, then click OK.

3-8 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition Copying the Master Repository to the Multiuser Development Directory After the multiuser development directory is identified, the administrator must copy the master repository file to the multiuser development directory. Projects from this master repository will be extracted and downloaded by the developers who will make changes and then merge these changes back into the master repository. After you copy the repository to the multiuser development network directory, notify developers that the multiuser development environment is ready. Setting Up a Pointer to the Multiuser Development Directory Before checking out projects, each developer must set up their Administration Tool to point to the multiuser development directory on the network. The Administration Tool stores this path in a hidden Windows registry setting on the workstation of the developer and uses it when the developer checks out and checks in objects in the multiuser development directory. Initially, the network directory contains the master repositories. The repositories in this location are shared with other developers. Later, the network directory contains additional multiuser development history files, including historical subsets and repository versions. Do not manually delete any files in the multiuser development directory; these files are important and are used by the system. When setting up the pointer, the developer can also complete the Full Name field. Although the field is optional, it is recommended that the developer complete this field to allow other developers to know who has locked the repository. The Full Name value is stored in HKEY_CURRENT_USER in the registry, and is unique for each login. To set up a pointer to the multiuser development directory: 1. From the Administration Tool menu, choose Tools Options. 2. In the Options dialog, click the Multiuser tab.

3. In the Multiuser tab, for Multiuser development directory, enter the full path to

the network directory. Alternatively, click Browse, select the multiuser development directory, and then click OK.

4. In the Full Name field, type your complete name, then click OK.

Making Changes in a Multiuser Development Environment During check-out and check-in, a copy of the master repository is temporarily copied to the developers local repository directory typically, ORACLE_ INSTANCE\bifoundation\OracleBIServerComponent\coreapplication_ obisn\repository by default. After checking out projects and making changes in a Caution: The administrator must set up a separate, shared network directory that is dedicated to multiuser development. If not set up and used as specified, critical repository files can be unintentionally overwritten and repository data can be lost. Note: Until the pointer is set up, the multiuser options are not available in the Administration Tool. Setting Up and Using the Multiuser Development Environment 3-9 local repository file, each developer can check in merge changes into the master repository or discard the changes. To make changes in a multiuser development environment, perform the tasks described in the following sections: ■ Checking Out Repository Projects ■ About Changing and Testing Metadata ■ About Multiuser Development Menu Options Checking Out Repository Projects After setting up a pointer to the multiuser development default directory, a developer can check out projects, change metadata, and test the metadata. In the File Multiuser submenu, the Checkout option is only available when there is a multiuser development directory defined in the Multiuser tab of the Options dialog. If a developer checks out a local repository and attempts to exit the application before publishing it to the network or discarding local changes, a message appears to allow the developer to select an action. See About Closing a Repository Before Publishing It to the Network for more information. This section contains the following topics: ■ About Repository Project Checkout ■ Checking Out Projects ■ Using the extractprojects Utility to Extract Projects About Repository Project Checkout During checkout, the Administration Tool performs the following tasks: ■ In the developers local repository directory, the Administration Tool makes a temporary copy of the master repository. ■ In the developers local repository directory, the Administration Tool saves a local copy of the selected projects in a new repository, such as Metadata1.rpd. The developer provides a name for the local copy. The developer makes metadata changes in this file. The number is incremented for each checkout for that session. ■ In the developers local repository directory, the Administration Tool saves a second local copy of the new repository, adding original as the prefix for example, originalMetadata1.rpd. ■ After the developer saves the new repository file, check out is complete. In the developers local repository directory, the temporary copy of the master repository is automatically deleted. Note: If a repository with that name exists in this location, the developer is asked to confirm overwriting the existing repository. If the developer clicks Yes, the existing local repository is immediately overwritten in the background and after the new repository is saved, the temporary master repository file is automatically deleted. 3-10 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition Checking Out Projects This section explains how to check out projects using the Administration Tool. To check out projects: 1. From the Administration Tool menu, choose File Multiuser Checkout. 2. If there is more than one repository in the multiuser development directory, the Multiuser Development Checkout dialog appears. Select the appropriate repository, and then click OK. This dialog does not appear if there is only one repository in the multiuser development directory.

3. In the Extract from dialog, type the repository password, and then click OK.