3-20 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition
■
Deleting Multiuser Development History
Viewing Multiuser Development History
You can view the development history of a multiuser development repository. In the Administration Tool, multiuser development history is only available when no
repository is open and after the administrator sets up the shared network directory. This prevents the confusion that could occur if a user opened a history log that did not
match an open, unrelated repository.
To view multiuser development history: 1.
Open the Administration Tool.
2. Without opening a repository, select File Multiuser History.
3.
In the Multiuser Development History dialog, select a repository. A list of all master repositories in the multiuser development directory appears. If
directory contains only one master repository, it is selected by default, and no list appears.
4.
In the Open Offline dialog, type the password for the repository. The Multi User History dialog appears.
Figure 3–7 shows the Multi User History dialog.
Figure 3–7 Multi User History Dialog
5.
In the Multi User History dialog, right-click a row and select an option. Table 3–1
describes the options in the Multi User History dialog.
Tip: To see details for all revisions, right-click in the background with no rows
selected and select View Details. Table 3–1
Options in the Multi User History Dialog Action
Description
View Repository Loads the selected master version of the repository in the
Administration Tool in read-only mode. View Prior to Merge
Projects Loads the selected version of a modified subset repository in the
Administration Tool in read-only mode. View Conflict Resolution
Loads all necessary repositories of the selected version. Also shows the Merge dialog in read-only mode with all selected
decisions as they were during the Merge Local Changes activity at that time. Double-clicking a row for a version with conflict
resolutions has the same effect as selecting this menu item.
Note: This menu item is only enabled for versions that had
conflict resolutions.
Setting Up and Using the Multiuser Development Environment 3-21
Deleting Multiuser Development History
Only multiuser development administrators can delete history. Administrators are defined in a special hidden option file in the multiuser development directory. See
Setting Multiuser Development Options for more information.
An administrator can delete the entire MUD history, or the oldest 1 to n versions. It is not possible to delete versions in the middle of the range. For example, an
administrator cannot delete version 3 if there are still versions 1 and 2. If an administrator deletes the entire MUD history, newly assigned version numbers restart
at version 1.
Setting Multiuser Development Options
You can create a multiuser development option file to specify options for multiuser development. The option file is a text file, in standard Windows INI format. It has the
following properties and characteristics:
■
The option file must be placed in the multiuser development directory. The file has the same name as the corresponding master repository, but with an .opt extension.
For example, for \\network\MUD\sales.rpd, create an option file called \\network\MUD\sales.opt.
■
The file should have the Hidden flag turned on.
■
In general, the option file should be managed only by multiuser development administrators. To ensure this, you may want to change the sharing permissions
for the file.
The following example shows a multiuser development option file: [Options]
BuildNumber = Yes Admin = admin1;admin2
Mandatory Consistency Check = Yes Equalize During Merge = Yes
Options that are not explicitly set are turned off by default. To turn an option on, set its value to Yes. To turn an option off, either remove it from the option file, or set its value
to No.
Table 3–2 explains the options in the multiuser development option file.
View Details Displays a log with details for the selected versions, or displays
details for all versions if no specific versions are selected. View Prior to Merge
Changes Compares modified subset repository of the selected version
with original subset repository and shows all changes made by the user in the selected version.
Find and Find Again Lets you search the list.
Select All Selects all items displayed in the dialog.
Delete Available only to multiuser development administrators.
Table 3–1 Cont. Options in the Multi User History Dialog
Action Description
3-22 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition
Table 3–2 Options in the Multiuser Development Option File
Option Description
BuildNumber When set to Yes, the build version of the Administration Tool is
displayed in the MUD history. Admin
Lists multiuser development administrators. Administrators must be defined in the option file before they can delete MUD
history. Administrators are defined by their computernetwork login
names. When multiple administrators exist, administrator names are separated by semicolons. For example:
Admin=jsmith;mramirez;plafleur Mandatory Consistency
Check When set to Yes, the publish step performs a consistency check.
Publishing cannot proceed unless there are no errors in the given repository.
Equalize During Merge When set to Yes, the multiuser development merge process
performs mandatory equalization during MUD merges. Note that setting this option to Yes affects the performance of the
merge process.
4
Importing Metadata and Working with Data Sources 4-1
4
Importing Metadata and Working with Data Sources
If you do not already have an Oracle BI repository file, you must create one. Then, you can import metadata from your data sources into the Physical layer of your repository.
The Physical layer of the Administration Tool defines the data sources to which the Oracle BI Server submits queries, and the relationships between physical databases
and other data sources that are used to process multiple data source queries.
Metadata imports to an Oracle BI repository must occur through an ODBC or native database connection to the underlying data source. Metadata can also be imported
from software such as Microsoft Excel through an ODBC connection.
Importing metadata directly from each data source saves you time and effort by importing the structure for the Physical layer. Data from these sources can be
displayed on Oracle BI Interactive Dashboards and other clients. You can only import metadata from supported data sources.
After you import metadata, properties in the associated database object and connection pool are typically set automatically. However, you may want to adjust
database or connection pool settings. See Chapter 6, Setting Up Database Objects and
Connection Pools for more information.
Although you can create the Physical layer manually rather than importing metadata, it is a labor-intensive and error-prone activity. It is strongly recommended that you
import metadata.
This chapter contains the following topics:
■
Creating New Oracle BI Repository Files
■
Performing Data Source Preconfiguration Tasks
■
Importing Metadata from Relational Data Sources
■
Importing Metadata from Multidimensional Data Sources
■
Importing Metadata from XML Data Sources
■
Using a Standby Database with Oracle Business Intelligence
Creating New Oracle BI Repository Files
You can use the Create New Repository Wizard in the Administration Tool to create new Oracle BI repository files .rpds. You do not need to create a new repository file if
you already have an existing repository.
4-2 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition
If you have an existing repository file, you can use the existing data source settings in that file as a template to connect to different data sources. To do this, use the existing
data source settings and just change the database type and connection pool information. See
Setting Up Database Objects and
Creating or Changing Connection Pools
for details.
To create a new repository file: 1.
In the Administration Tool, select File, then select New Repository. The Create New Repository Wizard appears.
If an existing repository is open, you are prompted to save your changes, and the existing repository is closed.
2.
Type a name for the repository. Keep the name to 156 characters or less to avoid problems with the metadata dictionary URL. An RPD file extension is
automatically added if you do not explicitly specify it.
3.
Select a location for the new repository. By default, new repositories are stored in the repository subdirectory, located at ORACLE_
INSTANCE\bifoundation\OracleBIServerComponent\coreapplication_ obisn\repository.
4. If you want to import metadata into the repository now, select Yes the default for
