Start the Discoverer Administrator application. When Discoverer Administrator appears, enter your credentials and click Connect.

In the Load Wizard dialog box, click Cancel.

Select File > Export from the Discoverer Administrator menu bar. The Export Wizard: Step 1 dialog box appears.

Select The entire End User Layer and click Next. A brief message appears, informing you that a list of all available EUL objects is being prepared.

In the Export Wizard: Step 2 dialog box, click Browse to identify the folder that contains your exported file.

Create a new top-level folder named DiscoMigration on the installation drive, name the export file video.eex, and click Save.

Click Finish.

Note: If you receive a message that video.eex already exists, click Yes to overwrite the file.

The EUL export is processed. When the Export Log window appears, scroll to review the results and to ensure that no errors were encountered.

Click Close. Alternatively, you can save the log to review it at a later time.

Select File > Exit to close Discoverer Administrator.

As mentioned in the prerequisite topic, you must run the migration assistant on the same machine as the Oracle BI EE installation.

Navigate to the <installdrive>\OracleBI\server\Bin directory. There are two important files in this directory: the migration assistant executable file named MigrateEUL.exe and a properties configuration file named MigrationConfig.properties.

The MigrationConfig.properties file allows you to control the migration behavior. The following table provides the available configuration options:

Sample of the MigrationConfig.properties file:

This tutorial accepts defaults.

A. The MigrateEul.exe file is the migration assistant. Click Start > Run. When the Run dialog box appears, enter cmd and click OK to open a command-prompt window.

B. At the <installdrive> prompt, enter cd DiscoMigration and press Enter. This positions you within the proper subdirectory on the installation drive.

C. Enter MigrateEul.exe video.eex and press Enter.

Your metadata is migrated successfully and a repository file is created in the same directory that contained the .eex file.

The repository file assumes the same name as the .eex file and has an .rpd extension. For this tutorial, the name of the .rpd file is video.rpd.

Note: The migration assistant generates two log files during conversion, examples of which follow the table below. These files are also placed within the same directory. The <filename>.migration log file captures the migration progress at a high level and the <filename>.exception log file captures the names of the items that could not be migrated.

Using the Discoverer Metadata Conversion Assistant is an iterative process, with the exceptions file providing a listing of the areas that need attention. Exceptions can be generated depending on the types of join configuration in the Discoverer metadata (for example, multiple join paths or circular join paths). The joins that are identified will be listed in this file to enable you to decide how to handle these scenarios.

For each Discoverer business area that is converted, these files contain the following details:

The name of the business area being processed

Details of any joins in the Discoverer metadata that may have been skipped due to the existence of multiple join paths. For each skipped join, a "folder ID" is generated that can be used as a reference for a second run of the migration assistant with the required folder IDs added to the MigrationConfig.properties file to generate folder aliases. The folder IDs are listed with the IncludePathsForFolders configuration file option.

The table below highlights the details of the migration assistant output and describes the corresponding items between Discoverer and Oracle BI EE:

(Note: For summarized property migration information, refer to the Oracle Discoverer Metadata Conversion Assistant documentation, topic 3.4, Description of output from the conversion assistant, at this link.)

Discoverer	Oracle BI EE
EUL	Maps to an Oracle BI EE metadata repository (.rpd) file
Business area	Maps to a presentation catalog, also known as a subject area in Answers
Simple folder	Maps against a database table or view. It correspondingly migrates to a physical table in the Physical layer, logical table in the Business Model and Mapping layer, and a presentation table in the Presentation layer. The table only migrates to the Presentation layer if it is correspondingly set to be visible to users in Discoverer.
Complex folder	Combines items from multiple simple folders. The analogy often used to describe a complex folder is that of a database view. From a Discoverer administration perspective, a complex folder is useful for combining items into logical groups to simplify the end user's view of the metadata. From the perspective of end users, this can simplify their task as they only need to go to a single folder to get all the items they need for a report. A complex folder will be mapped to a logical table in the logical layer having a logical table source that contains the base folders and the joins between them. This folder in turn will be joined to those base folders, which are dimensions. A complex folder appears in the Presentation layer with the following mapping: The item references of the complex folder are picked from the respective base folders in the logical layer. For creating Discoverer administration calculations within a complex folder, a logical table corresponding to the complex folder is created in the logical layer. The calculations involving items from more than one base table are created and the logical folder is moved to the Presentation layer. However, if the administration calculations are based on a single base folder, they are migrated to the corresponding logical folder and not the complex folder. Note: A complex folder based on items from another complex folder cannot be migrated automatically.
Custom folder	Enables flexibility in folder creation—for example, SQL statements using set operators such as UNION,  INTERSECT,  and MINUS. When a SQL statement is entered in the UI for creating a custom folder, a folder is created containing items that are referenced in the SQL statement. In Oracle BI EE, the custom folders are migrated to the Physical layer with a table type of SELECT. This is also known as an opaque view.
Item	Provides the basic building block for queries. An item is mapped to a column in a database table or view, or created from a calculation in Discoverer Administrator. This calculation can be based on PL/SQL functions. A Discoverer item migrates to a physical column in the Physical layer, logical column in the Business Model and Mapping layer, and a presentation column in the Presentation layer of Oracle BI EE. An item that is hidden from the end user will not appear in the Presentation layer. When building a query in Discoverer, end users can either select the default aggregation for an item or select from a list of available aggregation functions. In Oracle BI EE metadata, it is possible to specify the default aggregation for a particular column in the logical layer; however, this aggregation cannot be changed (in a similar manner to Discoverer) during the creation of the Answers worksheet. The user must create another column and define the required aggregation. Discoverer-calculated items based on Oracle PL/SQL functions or Oracle analytic functions will be migrated to Oracle BI EE metadata that uses the EVALUATE and EVALUATE_AGGR functions. These calculations will be created as a logical column with its formula being set in the physical mapping of the logical table source.
Joins	Define relationships between the folders that are used for building queries. Usually joins are defined using the corresponding key columns of the underlying database objects. Because of the differences in the metadata models between Discoverer and Oracle BI EE there are some differences in the types of joins that can be migrated automatically. It is in this area of metadata that the differences between Discoverer and Oracle BI EE metadata become apparent. The main difference is that the logical Business Model and Mapping layer needs to be based on one or more star schema model (this is a common data model for data warehouse design). A variation on the star schema model is known as a snowflake model—commonly representing the hierarchy levels of a dimension as separate tables. In this case, the migration assistant collapses the snowflake dimensions to their lowest level of dimension above the fact table. The Physical layer does not need to be modeled around a star schema, so this layer is created using the join information from the Discoverer metadata. Mandatory conditions Discoverer folders having multiple join paths to another folder will be supported by creating object aliases that are based on the same underlying physical object, but have the required alternative join paths. Duplicate joins In the case where duplicate join definitions exist in the Discoverer metadata, only one of the duplicate joins created in Discoverer will be considered for migration. Any duplicate joins that have been detected will be noted in the migration log files.
Conditions	Allow the creation of conditions in the metadata. Conditions can be both mandatory and optional. Mandatory conditions are not visible to the end user and have the effect of limiting the data that can be queried. Optional conditions can be defined for end user convenience—that is, the user who may not be familiar with SQL syntax can optionally use predefined conditions (perhaps containing complicated logic in their reports) by dragging them into their report from a list of available conditions. Mandatory Conversion depends on the type of folder. For simple and custom folders, mandatory conditions are migrated as “content filters” in the WHERE clause section of the logical table source. For complex folders, all users are migrated to the BI EE group EVERYONE, so mandatory conditions on complex folders are applied to this user group as a "security filter." Optional Not presently migrated Note: It is expected that optional conditions are persisted as "saved filters" in the Web Catalog when workbook migration becomes available.
Aggregate calculated item	Migrates using a variation of the EVALUATE function available in Oracle BI EE
Item hierarchy	Provides end users with a drill path through related data and is migrated to an Oracle BI EE dimension. The levels in the Discoverer item hierarchy are migrated to the associated dimension levels. Multiple hierarchy drill paths are migrated to entries in the preferred drill path property of the Oracle BI EE dimension level property. All hierarchies based on a folder are migrated to a single dimension created on the folder. An Item hierarchy based on complex folders will not be migrated because a dimension in Oracle BI EE must be associated with a dimension table. A hierarchy spanning tables will be migrated by setting the preferred drill path appropriately. Note: Item classes and summary folders are not migrated. Discoverer "template" Date hierarchies do not have corresponding objects in Oracle BI EE; therefore, only actual hierarchies are migrated to Oracle BI EE dimensions.

Examples of both log files for the video migration appear below.

Sample of the Video.migration file:

Sample of the Video.exception file:

This exception file indicates that there is a complex folder based on items from another complex folder— it is not possible to automatically create a complex folder of this nature in this version of the Discoverer Metadata Conversion Assistant. In addition, it is not possible to migrate hierarchies based on Discoverer complex folders because in Oracle BI EE, the hierarchies are based on dimension tables as defined in the Business Model and Mapping layer.

The final exceptions listed in this image concern optional conditions defined in Discoverer Administrator. Oracle plans to migrate these optional conditions to filters in a future version of the Discoverer Metadata Conversion Assistant after the workbook conversion is supported.

The next topic focuses on the newly created repository file and how to view it within Oracle BI EE.

Now that you have successfully created a migration file, you need to review the content. Navigate to the <installdrive>\DiscoMigration subdirectory that houses the video.rpd file created above in step 4, and double-click the video.rpd file.

Accept the default User, Administrator, and click OK to open the repository in offline mode.

The Oracle BI Administration Tool opens.

All three layers of metadata required by Oracle BI EE were created during migration.

A. Expand Video Store Tutorial in the Physical layer.

B. Expand VIDEO5.

These Physical layer objects were derived from the Discoverer metadata properties: owner and object.

Additionally, Join properties from Discoverer were also used during the conversion.

Next, review the Business Model and Mapping layer objects. This layer is a logical layer.

Expand Video Store Tutorial in the Business Model and Mapping layer.

This layer has been derived in a similar manner. However, the dimensions were derived from Discoverer hierarchies.

Review the Presentation layer objects. Expand Business Area: Video Store Tutorial in the Presentation layer.

This layer not only contains objects that were defined in Discoverer as visible to the end user, but also contains generated complex folders.

The following image illustrates what the Product folder from Discoverer looks like across the repository layers in Oracle BI EE.

The migration assistant converts Discoverer metadata as follows:

Next, you need to enter the parameters for the connection pool so that you can test your access to the data. Right-click ConnectionPool in the Physical layer pane and select Properties.

The Connection Pool Properties dialog box appears.

Select OCI 10g/11g from the Call interface drop-down list, enter your Data source name (for this tutorial on this machine, the data source name is ORCL), and enter your User name and Password to access the data source.

Your dialog box should look like this:

Click OK and confirm your password when prompted. You can now test the connection by viewing the data.

Right-click the Product folder and select View Data.

The View Data dialog box for the Product table appears, illustrating that your connection works correctly.

Click Close.

Before you can use this repository for queries and so forth, you need to run a consistency check. The Oracle BI Administration Tool enables you to ensure that a repository meets specific requirements, such as all logical columns are mapped directly or indirectly to one or more physical columns, all logical dimension tables have a logical key, all logical tables have a logical join relationship to another logical table, and a Presentation catalog exists for the business model, and so forth.

If the repository or an object within the repository is not consistent, a detailed error message appears. The Consistency Check Manager delivers three types of messages:

Select File > Check Global Consistency. Consistency Check Manager appears with all error, warning, and best practice information messages.

Because a warning message is not a critical error, click Close to exit Consistency Check Manager and select File > Save to save the repository. (Note: If you receive a message that requires you to check in your changes before saving the repository, click OK.)

To complete the final stage in preparing this repository for use with queries, you must copy the repository file to an appropriate location for repositories and edit the NQSConfig.ini file.

A. Navigate to <installdrive>\DiscoMigration. Select the video.rpd file and select Edit > Copy.

B. Navigate to <installdrive>\OracleBI\server\Repository. Select Edit > Paste. The video.rpd file is copied to the repository subdirectory.

C. The NQSConfig.ini file is an initialization file. By updating the Repository section of this file, you are instructing the BI Server to load this specific repository into memory upon startup.

Navigate to <installdrive>\OracleBI\server\Config. Double-click the NQSConfig.ini file (you can use a text editor, such as Notepad to edit this file) and scroll down to locate the [REPOSITORY] section.

D. In the [REPOSITORY] section, enter Star = video.rpd, DEFAULT;. Enter a # sign in front of the active repository file (in this example, the active repository is paint.rpd), and select File > Save to register the repository. The NQSConfig.ini file should look like this:

Close the NQSConfig.ini file.

After the changes have been made to the NQSConfig.ini file, you must restart the Oracle Business Intelligence services that support the repository.

A. Click Start > All Programs > Administrative Tools > Services.

B. Scroll to locate and select Oracle BI Server. Click the Restart () icon to restart the services.

While the Services window is still open, ensure that Oracle BI Presentation Server and Oracle BI Java Host services are also started. (These services are required for Answers.)

Close the Services window.

To ensure that your repository has been correctly configured, open the Oracle BI Administration Tool online.

Click Start > All Programs > Oracle Business Intelligence > Administration. The Oracle BI Administration Tool appears.

Click the Open Online () icon to open the Video repository. The Open Online AnalyticsWeb dialog box appears.

Click Open. The Video repository opens, ensuring that you can now use this repository to run queries.

To further verify that you are able to use the repository, create and run a query against the Video repository by using Answers.

A. From the Start menu, select All Programs > Oracle Business Intelligence > Presentation Services. The Oracle Business Intelligence Log In window appears.

B. Enter Administrator in the User ID field and click Log In.

The My Dashboard page appears.

Click the Answers link. The Answers Start page appears.

The Answers Start page is composed of two panes: Selection and Workspace.

The Selection pane on the left contains the Catalog and Dashboard tabs from which you select items to manipulate.

The Presentation Catalog (Catalog) stores the content created with Answers and Interactive Dashboards. The content can be organized into folders that are either shared or personal. Types of content that can be stored in the Catalog include requests created with Answers, HTML content, and links to other images, documents, and sites.

A dashboard is made up of sections of information that can contain items, such as results from Answers requests, external Web content, HTML text, graphics, links to other sites, embedded objects such as requests, and so on. Dashboard content is organized into pages. Pages appear as tabs across the top of the screen in Interactive Dashboards.

The Workspace pane on the right contains a list of the actions you can perform and the subject areas that are available to you. Oracle Business Intelligence presents data in subject areas. A subject area contains columns that represent information about the areas of your organization’s business, or about groups of users within your organization. Subject areas have names that correspond to the types of information they contain—for example, Marketing Contracts, Service Requests, and Orders. Columns also have names that indicate the types of information they contain, such as Account and Contact.

The subject areas that you see in the image are the same ones represented in the Oracle BI Administration Tool.

The "feature links" listed at the top of the Workspace pane provide access to other Oracle Business Intelligence functions.

Click the Business Area: Video Store Tutorial subject area.

The Answers workspace page appears.

The Answers workspace displays the following tabs for working with a request:

	Criteria: Provides access to the columns selected for the request, and buttons to access the most common view types
	Results: Allows you to work with the results of the request
	Prompts: Allows you to create prompts to filter the request
	Advanced: Allows advanced users to work with the XML and logical SQL for the request

Each tab contains on-screen information and buttons to help you create, access, and manage requests.

These steps show you how to create a simple query that provides product sales information.

A. Expand the Products and Sales Facts folders to view their respective columns.

B. Click Product Category in the Products folder to add it to the Criteria workspace.

C. Click Product Description in the Products folder to add it to the Criteria workspace.

D. Click Sales Sum in the Sales Facts folder to add it to the Criteria workspace.

Your workspace should look like the following:

Click Display Results. Your query appears.

The corresponding query in Discoverer appears below: