Export

The export feature is part of the export/import utility in iKnowBase. With the export feature you can define and build transport sets and export data. Components, metadata, and content can be exported. The import feature lets you import previously exported data.

The export/import utility in iKnowBase also supports export and import of Oracle Portal data, which you will need if your iKnowBase application uses Oracle Portal as a frontend. Before you can generate the iKnowBase export set, you must create and export the appropriate Oracle Portal export set.

Properties

This section describes the properties of an export definition, as shown on the corresponding Edit pane.

Edit Tab

The Edit tab contains general information about the domain.

insert into exp_imp_obj_selection (export_guid, table_name, object_guid)
select '<the export Guid>','DOCUMENT',document_guid from document where <condition>;

Overview – tables Tab

The Overview – tables tab contains information on tables chosen for export. The content of this tab is available after the transport set is built or data exported.

Debug and error log Tab

This tab contains information on actual export process. The content of this tab is available after the building of the transport set or export of data is started.

Export tree Tab

This tab contains information on all exported objects. The content of this tab is available after the building of the transport set or export of data is started.

Tasks

Adding Objects to an Export Tab

To add objects (e.g. components configured in Development Studio or database tables) to an export, perform the following steps:

1. On the edit tab of the Edit pane for the export, select the appropriate object type in the select objects dropdown. The region select objects which displays a list of all existing objects of the given type appears.
2. In the select objects region, click on the checkboxes for the objects that you want to include in the export.
3. Click Apply or OK. The selected objects are added to the export definition, and will appear as selected objects in the region selected objects and tables in the transport set in the Edit pane.

Note: You can add objects of multiple object types to an export. After you have added objects of one object type and saved the export, you can repeat the steps above for a different object type.

To remove an object from an export definition, perform the following steps:

1. On the Edit pane for the export, click on the checkbox for the object you want to remove in the region selected objects and tables in the transport set.
2. Click Save. The object is removed from the list.

Adding Documents to an Export

To add documents to an export, perform the following steps:

1. On the Edit tab of the Edit pane for the export, click the document archive link next to select documents. The document archive opens in a new browser window.
2. In the document archive, find and select the documents to be included in the export.
3. Click OK. The list of documents to include in the export will appear next to select documents in the Edit pane. Note: It is possible to remove a document by clicking on the X icon in front of the document.
4. On the Edit pane for the export, click on Apply. The selected documents are added to the export definition, and will appear as selected objects in the region Selected objects and tables in the transport set in the Edit pane.

To remove a document from an export definition, perform the following steps:

1. On the Edit pane for the export, click on the checkbox for the document you want to remove in the region Selected objects and tables in the transport set.
2. Click Save. The document is removed from the list.

Exporting Data for iKnowBase PageEngine use

To export data for use with the iKnowBase Page Engine, perform the steps below. For exporting data for Oracle Portal, see the next chapter:

1. Create an export definition, defining which data you want to export.
2. Click on the Build dataset button on the Edit pane of the export definition. The dataset is built, and a debug and error log becomes available on the Debug and error log tab. An overview of how many rows from which tables will be exported becomes available on the Overview � tables tab and a graphical overview of object dependencies becomes available on the Export tree tab.
3. If you want to define import rules for each table (replace on import/delete details) you can preset values before you export the file.
4. Check the Debug and error logs tab.
5. When the dataset is built, click on the Export button on the Edit pane of the export definition. The specified data is exported to the server data pump directory. The exported data file will be named EXP-SchemaName-ExportDefGuid-ExportDefName.dmp, where SchemaName is the name of the database schema, ExportDefGuid is the guid of the export definition, and ExportDefName is the name of the export definition. An iKnowBase document with the information type “iKnowBase Transport Set” with the dump file will be created. It will be given the title Export(DMP), where Export is the name of export definition. A debug and error log becomes available on the Debug and error log tab. An overview of how many rows from which tables are exported becomes available on the Overview – tables tab and a graphical overview of object dependencies becomes available on the Export tree tab.
6. Download the dump file through the web interface, or retrieve it directly from the database server.

Exporting Data with Oracle Portal Data

To export data with Oracle Portal data, perform the following steps:

1. In Oracle Portal, create an export set. Select the pages and page groups to include in the export set. Select “Export now” on the final step.
2. Download the Oracle Portal .bat or .sh file.
3. Run the Oracle Portal file to generate the dump file. Example: call <script-file>.bat -mode export -s portal -p <portal password> -c <sid> -d myexport.dmp
4. Create an export definition, defining which data you want to export, including the Oracle Portal export set you created in the first step.
5. Click on the Build dataset button on the Edit pane of the export definition. The dataset is built, and a debug and error log becomes available on the Debug and error log tab. An overview of how many rows from which tables will be exported becomes available on the Overview � tables tab and a graphical overview of object dependencies becomes available on the Export tree tab.
6. If you want to define import rules for each table (replace on import/delete details) you can preset values before you export the file. When you rebuild the dataset, these settings has to be set again.
7. Check the debug and error logs.
8. When the dataset is built, click on the Export button on the Edit pane of the export definition. The specified data is exported to the server data pump directory. The exported data file will be named EXP-SchemaName-ExportDefGuid-ExportDefName.dmp, where SchemaName is the name of the database schema, ExportDefGuid is the guid of the export definition, and ExportDefName is the name of the export definition. An iKnowBase document with the information type “iKnowBase Transport Set” with the dump file will be created. It will be given the title Export(DMP), where Export is the name of export definition. A debug and error log becomes available on the Debug and error log tab. An overview of how many rows from which tables are exported becomes available on the Overview – tables tab and a graphical overview of object dependencies becomes available on the Export tree tab.
9. Download the dump file through the web interface, or retrieve it directly from the database server.