|
Oracle® HTML DB
Release 2.0 |
|
 Previous |
 Next |
You export and import application definitions and all associated files using the Workspace, Application, CSS, Images, Script Files, Themes, and User Interface Defaults buttons located at the top the Export page.
Topics:
When you export a application, Oracle HTML DB generates a text file containing PL/SQL API calls.
To export an application:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
On the Application Builder home page, click Export/Import.
When prompted to select a task, select Export and click Next.
From File Format, select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
From Build Status Override, select one of the following:
Run Application Only - Developers can only run an application
Run and Build Application - Developers can both run and edit an application
Selecting Run Application Only is an effective way to protect an application from modifications from other developers. Note that if you select Run Application Only you cannot set the argument p_trace to Yes. Also, be aware that once you override the Build Status, you can only change it in Oracle HTML DB Administration Services.
Use the As of field to export your application as it was previously defined. Specify the number of minutes in the field provided.
This utility uses the DBMS_FLASHBACK package. Because the timestamp to System Change Number (SCN) mapping is refreshed approximately every five minutes, you may have to wait that amount of time to locate the version you are looking for. The time undo information is retained and influenced by the startup parameter UNDO_RETENTION (the default is three hours). However, this only influences the size of the undo tablespace. While two databases may have the same UNDO_RETENTION parameter, you will be able to go back further in time on a database with fewer transactions since it is not filling the undo tablespace, forcing older data to be archived.
Click Export Application.
In addition to exporting the actual application file, you may also need to export other related files such cascading style sheets, images, and script files.
You can export a specific page within an application by clicking the Export button on the Page Definition. When exporting a page, remember the following:
Exported pages can only be imported sucessfully if they have the same application ID and workspace ID.
Some pages may reference shared components. To export all pages within an application as well as application shared components, you need to export the entire application.
To export a page in an application:
Navigate to the appropriate Page Definition:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
Select a page.
The Page Definition appears.
On the Page Definition, click Export at the top of the page.
From Page, select the page to be exported.
From File Format, select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Use the As of field to export a page as it was previously defined. Specify the number of minutes in the field provided.
This utility uses the DBMS_FLASHBACK package. Because the timestamp to System Change Number (SCN) mapping is refreshed approximately every five minutes, you may have to wait that amount of time to locate the version you are looking for. The time undo information is retained and influenced by the startup parameter UNDO_RETENTION (the default is three hours). However, this only influences the size of the undo tablespace. While two databases may have the same UNDO_RETENTION parameter, you will be able to go back further in time on a database with fewer transactions since it is not filling the undo tablespace, forcing older data to be archived.
Click Export Page.
Use the Export Cascading Style Sheets utility to export cascading style sheets you imported.
To export related cascading style sheets:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
On the Application Builder home page, click Export/Import.
When prompted to select a task, select Export and click Next.
Click CSS at the top of the page.
On the Export Cascading Style Sheets page:
Select the cascading style sheets
From File Format, select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Click Export Style Sheets.
Use the Export Images utility to export images you have imported.
To export related images:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
On the Application Builder home page, click Export/Import.
When prompted to select a task, select Export and click Next.
Click Images at the top of the page.
On the Export Images page:
Select an application from which to export images.
Be aware that selecting Workspace Images only exports those images in your repository that are not associated with a specific application. If all of your images are associated with specific applications then the workspace image export file will be empty.
From File Format, select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Click Export Images.
Use the Export Static Files utility to export static files you have imported.
To export related static files:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
On the Application Builder home page, click Export/Import.
When prompted to select a task, select Export and click Next.
Click Files at the top of the page.
On Export Static Files:
Select the files to be exported.
From File Format, select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Click Export File(s).
Note that you cannot use Web interface described in this section to import exported static files into another Oracle HTML DB instance. To import exported static files into another Oracle HTML DB instance, use SQL*Plus while connected as the Oracle HTML DB database user. Note that you must export from and to a workspace having the same name and workspace ID.
You can transfer selected scripts from your current Script Repository to a Script Repository in a different Workspace by using the Export and Import tasks.
To export script files:
Navigate to the Workspace home page.
Click SQL Workshop.
Click SQL Scripts.
From the Tasks list, select Export.
Select the appropriate script files and click Add to Export.
Review the file name and click Export All.
Select the Remove check box to remove the script.
Use the Export Theme utility to export themes from one Oracle HTML DB development instance to a file.
To export an application theme from the Export page:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
On the Application Builder home page, click Export/Import.
When prompted to select a task, select Export and click Next.
Click Themes at the top of the page.
On the Export Application Theme page:
Select the theme to be exported.
From File Format, select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Click Export Theme.
To export an application theme from the Themes page:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
On the Application Builder home page, click Shared Components.
Under User Interface, select Themes.
The Themes page appears.
From the Tasks list, select Export Theme.
The Export page appears.
Click Themes at the top of the page.
On the Export Application Theme page:
Select the theme to be exported.
From File Format, select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Click Export Theme.
Exporting User Interface Defaults is useful when you plan to develop on the target machine.
When you export User Interface Defaults, all User Interface Defaults for the selected schema are exported to a single SQL*Plus script. When prompted, save this file to your hard drive. The file contains an API call to create table hints by making calls to the application PL/SQL API. You can use this file to import User Interface Defaults to another database and Oracle HTML DB instance.
To export User Interface Defaults from the Export page:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
On the Application Builder home page, click Export/Import.
When prompted to select a task, select Export and click Next.
Click User Interface Defaults at the top of the page.
On the Export User Interface Defaults page:
From Schema, select the schema that owns the table associated with the User Interface Defaults.
From File Format, select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Click Export.
To export User Interface Defaults from the User Interface Defaults page:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
On the Application Builder home page, click Shared Components.
Under User Interface, select User Interface Defaults.
The User Interface Defaults page appears.
Click Export.
The Export page appears.
Click Themes at the top of the page.
On the Export User Interface Defaults page:
From Schema, select the schema that owns the table associated with the User Interface Defaults.
From File Format, select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Click Export.