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. 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.
Parts
» Oracle Fusion Middleware Online Documentation Library
» Click OK when you are finished setting preferences.
» Select Set Icon. Oracle Fusion Middleware Online Documentation Library
» Select the appropriate DSN and click OK.
» Click OK. Oracle Fusion Middleware Online Documentation Library
» Without opening a repository, select File Multiuser History.
» In the ODBC Data Source Administrator dialog, click the System DSN tab, and
» In the Select Data Source screen, in the Connection Type field, select the type of
» Click Finish. Oracle Fusion Middleware Online Documentation Library
» In the Administration Tool, select File, then select Import Metadata.
» Provide the Data source name for the primary database. Click OK.
» In the Select Data Source screen, select OracleADF_HTTP for Connection Type.
» Select the objects you want to import in the Available list and move them to the Click Finish.
» In the Database dialog, click the Features tab. In the Features tab, use the information in
» Specify or adjust the properties as needed, then click OK.
» In the Persist connection pool area, click Clear. Click OK.
» To add tables to the display folder, click Add. Then, in the Browse dialog, select Click OK.
» Click OK in the Hierarchy dialog.
» Select View Members. Click Query to display results. When finished, click Close.
» Click OK. Select Create Columns for Alias Table. Then, from the sub-list, select the alias
» Type the text of the hint in the Hint field and click OK.
» In the shortcut menu, select Update Row Count. Click Yes to check out the objects.
» If you want to provide a dynamic list of currency options, create a table in your
» Click OK. Click OK or Cancel to close the Dimensions dialog.
» From the right-click menu, select Create Logical Dimension, then select either
» In the Check Out Objects dialog, click Yes to check out the objects that appear in
» If the values for the source are unique, select the option Select distinct values.
» Click OK. To move a table, in the Name list, select the table you want to reorder. Then, use
» In the Finish Script screen, the complete path and file name appears. Click Finish.
» Click OK, then click OK again to return to the Identity Manager.
» On the General tab, in the Data source definition: Database field, ensure that the
» Click OK. Open the user.sh file. You can find this file at:
» Click Select next to Patch File. Browse to select the patch file you want to apply, Click Finish.
» Select Tools, then select Query Repository. Click Query.
» When you have finished mapping columns between the selected physical tables, Click Finish.
» In the Choose Directory dialog, click Browse to locate and select the location Click OK.
» To remove the selected objects, click Yes.
» Repository initialization blocks only In the Schedule area, select a start date and
» In the [Repository|Session] Variable Initialization Block dialog, click Edit Data
» Click Edit Data Target. Click OK.
» Check out the branch project using File Multiuser Checkout. You can check
Show more