|Oracle® Fusion Middleware Administrator's Guide for Oracle Business Intelligence Discoverer
11g Release 1 (11.1.1)
Part Number B32519-02
Use this dialog to specify where you want to save the export file.
You can also:
save workbooks in XML
save export commands as a text file (*.txt)
This dialog is also displayed as:
For more information, see:
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
Clear this check box to only save workbooks in binary format within the
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").
Note that you only export the definition of the EUL, the business area, or the object being exported. You are not exporting the database containing the EUL tables, or the EUL tables themselves. Nor are you exporting the database objects referenced by the EUL objects. If you import a business area or object into a database, the following conditions must apply before Discoverer end users can view the data referenced by the imported business area or object:
the database tables referenced by the imported business area or object must exist in the database
database users must have sufficient privileges to access the database, the EUL tables, and the database objects, that the imported business area or object reference (for more information, see "Controlling Access to Information" and "What are the data access prerequisites?")