Skip Headers
Oracle® Fusion Middleware Administrator's Guide for Oracle Business Intelligence Discoverer
11g Release 1 (11.1.1)

Part Number B32519-02
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

Export Wizard: Step 2/3 dialog

Use this dialog to specify where you want to save the export file.

You can also:

This dialog is also displayed as:

Export Wizard: Step 2 dialog
Export Wizard: Step 3 dialog

For more information, see:

"What is an End User Layer?"

"About copying EULs and EUL objects by exporting and importing"

Where do you want to save the file?

Use this field to specify the name and location of the export file in which to save the exported objects. The export file will have .eex as the suffix.

Use the Browse button to specify the export file name and location using the Save As dialog.

Tip: It is a good idea to give the export file a name that suggests the kind of EUL objects the file contains. A descriptive name makes it easier to locate the file when you want to import it into another EUL later.

The following objects will be exported:

This field displays all of the objects that will be exported to the export file.

Generate additional XML for exported workbooks

Select this check box to save workbooks in XML format within the .eex file.

Clear this check box to only save workbooks in binary format within the .eex file.

Discoverer Administrator saves exported EUL objects (except workbooks) in XML format in the export file. By default, workbooks are saved in binary format. By saving workbooks additionally in XML format you can view workbook definitions in an XML browser.

Save export commands as text file (*.txt)

Select this check box to create an additional text file containing the commands that were used to create this export. You might save export commands as a text file, to reuse them in the Discoverer command-line interface (for more information, see "About using the Discoverer command-line interface").