Click OK. Oracle Fusion Middleware Online Documentation Library
11. Click OK.
Note: If you do not see the set of subject areas you expect after the project is created, edit the project to explicitly add the subject areas you need. Setting Up and Using the Multiuser Development Environment 3-7 About Converting Older Projects During Repository Upgrade When you upgrade a repository from Oracle Business Intelligence versions before 10.1.3.2, the project definition is upgraded. During the upgrade, the project definition, subject areas, target levels, list catalogs, and existing fact tables are automatically converted into simple fact tables in the following way: ■ Get presentation columns related to the target levels through the qualifying keys. ■ Get presentation columns related to the list catalogs through the qualifying keys. ■ Get presentation columns related to the subject areas. ■ Get all the logical columns from all the presentation columns. ■ Get all the logical columns from the fact tables in the project. ■ Get the fact tables from all the logical columns. After the upgrade, projects contain only simple fact tables. All the security objects remain unchanged. In addition, projects in repositories from any version before 11g Release 1 11.1.1 are upgraded so that they explicitly contain Presentation layer objects. In previous releases, Presentation layer objects were implicitly included based on the permissions of the users included in the project. Setting Up the Multiuser Development Directory To prepare for multiuser development, an administrator performs the following tasks: ■ Identify or create a shared network directory that will be dedicated to multiuser development. ■ After creating all projects, copy the repository file in which you created the projects to the multiuser development directory where it will be used as your master repository for multiuser development. After the administrator has identified the multiuser development directory and copied the repository file, developers must set up to the Administration Tool to point to the multiuser development directory before they can check out projects. This section contains the following topics: ■ Identifying the Multiuser Development Directory ■ Copying the Master Repository to the Multiuser Development Directory ■ Setting Up a Pointer to the Multiuser Development Directory Identifying the Multiuser Development Directory After defining all projects, the administrator must identify or create a shared network directory called the multiuser development directory that all developers can access, and then upload the new master repository to that location. This shared network directory should be used only for multiuser development. This directory typically contains copies of repositories that need to be maintained by multiple developers. The multiuser development directory must be on a Windows system. Developers create a pointer to the multiuser development directory when they set up the Administration Tool on their computers. 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
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