 |
|
Oracle Tips by Burleson |
Viewing the HTLM DB Source Code
Trial and error
is the best way to learn new aspects of any program. The goal of this
section is to illustrate how it is possible to teach oneself how to do
something that has not been covered or documented in the book.
An earlier chapter covered Application Deployment
with Oracle HTML DB. This is where how to export and import
applications was covered. Well … guess what? HTML DB is itself an
exported application; nine of them, actually. Therefore, the HTML DB
application files are used to create new HTML DB applications. It is
not possible to run them due to security restrictions, but it is
possible to look at the code to see how the developers of HTML DB did
things. This is a great way to learn how HTML DB was intended to be
used.
Loading the HTML DB application files
When testing a new skill or trying something new,
it is wise to create a new workspace into which these applications can
be imported. That way, the workspace can be dropped later if problems
arise. Also, make sure there is enough space in the HTMLDB20
tablespace. If a practice tablespace was created as suggested in an
earlier chapter, expand the size to 200MB. A statement like the
following can be used:
alter database
datafile 'C:\oradata\hdb20\htmldb20_01.dbf' resize 204864m;
M
CAUTION: When attempting this, it is important to pay
close attention to Removing the Application Alias from each of the
applications.
Ok, now that the customary disclaimers are out of
the way, load the applications. The following process assumes that a
new workspace has already been created. For explanations, the parsing
schema will be named as HDBAPPS.
An earlier chapter covered the download of the
installation files for HTML DB. If the steps in that chapter were
followed, there will be nine files in the C:\htmldb_book\htmldb\builder
directory.
1.
Navigate to the Application Builder home page and click on the
Import button.
2.
On the Import page:
-
Import file: C:\htmldb_book\htmldb\builder\f4000.sql.
-
File Type: Application/Page Export.
-
File Character Set: Leave the default
-
Click Next.
3.
On the next page, click the Install button.
4.
On the Install Application page:
-
Parse As Schema: HDBAPPS, unless the
user’s schema has a different name, in which case that schema
should be used.
-
Build Status: Run and Build
Application.
-
Install As Application: Change
Application ID.
-
New Application: 400.
If possible, enter the
same application ID’s shown in Figure 16.11. Otherwise choose what is
available.
5.
Click the Install Application button.
6.
On the Application Installed page, click on the Edit
Application Attributes link.
7.
On the Application Attributes page:
-
For the Name, add the number of the
file loaded to the front of the name. For example, file f4000.sql
was loaded, so change the Name field and add 4000. The name
should then be 4000 – HTML DB Application Builder. This will make
it easier to associate with the file used to load the application
in the future.
-
Application Alias: Clear this field so
it is NULL. This is very important.
-
Click the Apply Changes button.
For this example, the author has loaded all the
HTML DB applications in the environment and shown the Application
Builder home page in Figure 16.11.
Continue loading the applications in the C:\htmldb_book\htmldb\builder
directory. If they are not all loaded at this time, they can be
loaded at a later time. The next exercise, however, will show why the
HTML DB application should probably be loaded.
The
above book excerpt is from:
Easy HTML-DB
Oracle Application Express
Create Dynamic
Web Pages with OAE
ISBN 0-9761573-1-4
Michael Cunningham & Kent Crotty
http://www.rampant-books.com/book_2005_2_html_db.htm
 |
For more details and scripts, see my new book "
Oracle
Tuning: The Definitive Reference", over 900 pages
of BC's favorite tuning tips & scripts.
You can buy it direct from the publisher for 30%-off and get
instant access to the code depot. |
|
