| Oracle® HTML DB Installation Guide Release 2.0 Part Number B16375-01 |
|
|
PDF · Mobi · ePub |
| Oracle® HTML DB Installation Guide Release 2.0 Part Number B16375-01 |
|
|
PDF · Mobi · ePub |
This chapter describes tasks that you need to complete after you install the software.
This chapter contains these topics:
Note:
Within the context of this document, the Oracle home directory (
ORACLE_HOME) is the location where Oracle HTTP Server is installed.After you install Oracle HTML DB, you need to complete the following steps:
Run the utlrp.sql script from the Oracle Database home to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.
SQL> @?/rdbms/admin/utlrp.sql
Restart the processes that you stopped before you began the installation, such as listener and other processes. In addition, restart Oracle HTTP Server.
See Also:
"Recommended Pre-installation Tasks"Whether you are loading a new installation or upgrading from a previous release, you must copy the images directory from the top level of the unzipped htmldb_2.0.zip file to the location on the file system containing the Oracle home for Oracle HTTP Server.
If you are upgrading from a previous version of Oracle HTML DB, you should rename the existing images directory for Oracle HTML DB to reflect the release number (for example, images_1_5). By renaming the images directory, you have the option reverting to it later on.
To locate images directory on the file system, review the following files for the text alias /i/:
Oracle9i HTTP Server Release 2, see the httpd.conf file
Oracle HTTP Server 10g, see the marvel.conf file
Oracle Application Server 10g, see the marvel.conf file
On a Windows system, you can copy the htmldb\images directory using Windows Explorer or execute a command such as the following from a command prompt:
xcopy /E /I htmldb\images ORACLE_BASE\ORACLE_HOME\Apache\Apache\images
On UNIX or Linux based systems, you can copy the htmldb/images directory by executing a command such as the following:
cp -rf htmldb/images ORACLE_BASE/ORACLE_HOME/Apache/Apache
If you are upgrading Oracle HTML DB from release 1.5.0.00.33. 1.5.1.00.12, 1.6.0.00.87 or 1.6.1.00.03 and the password you provided during your initial installation differs from the one you specified while executing the htmldbins.sql script, you need to modify the file that contains the Database Access Descriptors (DADs). In addition, you must add two new MIME types to support SQL Workshop. The following sections describe the parameter you need to modify depending upon the type of Oracle HTTP Server in your environment.
Topics in this section include:
If you are upgrading Oracle HTML DB and are running Oracle HTTP Server release 9.0.3 or higher, you must modify the parameter password in the wdbsvr.app file and modify the httpd.conf file to add two new MIME types to support SQL Workshop.
Perform the following tasks if the password you provided during your initial installation differs from the one you specified while executing the htmldbins.sql script.
To modify the parameter password in the wdbsvr.app file:
Use a text editor and open the wdbsvr.app file.
For UNIX and Linux based systems, the file is located at:
ORACLE_BASE/ORACLE_HOME/Apache/modplsql/cfg/wdbsvr.app
For Windows based systems, the file is located at:
ORACLE_BASE\ORACLE_HOME\Apache\modplsql\cfg\wdbsvr.app
Find the DAD settings for Oracle HTML DB by searching for the following:
DAD_htmldb
Edit value next to the parameter password to match the password you provided while executing the htmldbins.sql script.
Save your changes.
Stop and restart Oracle HTTP Server.
For UNIX and Linux based systems, execute the following commands:
ORACLE_BASE/ORACLE_HOME/Apache/Apache/bin/apachectl stop ORACLE_BASE/ORACLE_HOME/Apache/Apache/bin/apachectl start
Note that if the Oracle HTTP Server is listening on a port less than 1024, the these commands must be executed as a privileged user (such as root).
For Windows based systems:
Stop Oracle HTTP Server - From the Start menu, select Programs, Oracle - OraHome, Oracle HTTP Server, and Stop HTTP Server.
Restart Oracle HTTP Server - - From the Start menu, select Oracle - OraHome, Oracle HTTP Server, and Start HTTP Server.
See Also:
Oracle HTTP Server Administration GuideYou need to modify the httpd.conf file to add two new MIME types to support SQL Workshop.
To modify httpd.conf file:
Use a text editor and open the httpd.conf file
For UNIX and Linux based systems, the file is located at:
ORACLE_BASE/ORACLE_HOME/Apache/Apache/conf/httpd.conf
For Windows based systems:
ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf\httpd.conf
Add the following line if it does not currently exist:
AddType text/xml xbl
Add the following line if it does not currently exist:
AddType text/x-component htc
Save and exit the httpd.conf file.
Stop and restart Oracle HTTP Server.
For UNIX and Linux based systems, execute the following commands:
ORACLE_BASE/ORACLE_HOME/Apache/Apache/bin/apachectl stop ORACLE_BASE/ORACLE_HOME/Apache/Apache/bin/apachectl start
Note that if the Oracle HTTP Server is listening on a port less than 1024, the these commands must be executed as a privileged user (such as root).
For Windows based systems:
Stop Oracle HTTP Server - From the Start menu, select Programs, Oracle - OraHome, Oracle HTTP Server, and Stop HTTP Server.
Restart Oracle HTTP Server- From the Start menu, select Programs, Oracle - OraHome, Oracle HTTP Server, and Start HTTP Server.
See Also:
Oracle HTTP Server Administration GuideIf you are upgrading Oracle HTML DB and are running Oracle HTTP Server 10g Release 1 or Oracle Application Server 10g, you must modify the parameter PlsqlDatabasePassword and add two new MIME types in the marvel.conf file.
To modify the parameter PlsqlDatabasePassword in the marvel.conf file:
Use a text editor and open the marvel.conf file:
For UNIX and Linux based systems, the file is located at:
ORACLE_BASE/ORACLE_HOME/Apache/modplsql/conf/marvel.conf
For Windows based systems, the file is located at:
ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf\marvel.conf
Find the DAD settings for Oracle HTML DB by searching for the following:
/pls/htmldb
Modify the value of the parameter PlsqlDatabasePassword to match the password you provided while executing the htmldbins.sql script.
Next, add two new MIME types to support SQL Workshop.
Add the following line if it does not currently exist:
AddType text/xml xbl
Add the following line if it does not currently exist:
AddType text/x-component htc
Save your changes.
For Oracle Application Server 10g, execute the following commands:
For UNIX and Linux based systems:
ORACLE_BASE/ORACLE_HOME/dcm/bin/dcmctl updateConfig -ct ohs
For Windows based systems:
ORACLE_BASE\ORACLE_HOME\dcm\bin\dcmctl updateConfig -ct ohs
Stop and restart Oracle HTTP Server.
For UNIX and Linux based systems, execute the following commands:
ORACLE_BASE/ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server ORACLE_BASE/ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=HTTP_Server
For Windows based systems:
ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl stopproc ias-component=HTTP_Server ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=HTTP_Server
Oracle HTML DB must have access to Oracle HTTP Server with mod_plsql. The instructions that follow explain how to configure different versions of Oracle HTTP Server with mod_plsql.
Topics in this section include:
The wdbsvr.app file contains information about Database Access Descriptors (DADs). A DAD is a set of values that specify how the Oracle HTTP Server component modplsql connects to the database server to fulfill an HTTP request. You create a DAD to specify how to connect to an Oracle HTML DB instance.
To create the DAD you modify the file wdbsvr.app and add an entry for Oracle HTML DB.
To modify the wdbsvr.app file:
Use a text editor and open the wdbsvr.app file:
For UNIX and Linux based systems, the file is located at:
ORACLE_BASE/ORACLE_HOME/Apache/modplsql/cfg/wdbsvr.app
For Windows based systems:
ORACLE_BASE\ORACLE_HOME\Apache\modplsql\cfg\wdbsvr.app
Add an entry for Oracle HTML DB using the following syntax. Only change the settings indicated in italics.
[DAD_htmldb] connect_string = localhost:1521:orcl password = htmldb username = htmldb_public_user default_page = htmldb document_table = wwv_flow_file_objects$ document_path = docs document_proc = wwv_flow_file_mgr.process_download reuse = Yes enablesso = No stateful = STATELESS_RESET nls_lang = American_America.AL32UTF8
Where:
connect_string refers to the host ID, port number, and Oracle9i database where Oracle HTML DB was installed. Use the format host:port:sid.
If the Oracle9i version of Oracle HTTP Server you want to use is installed in the same Oracle home as the database you specified for use with Oracle HTML DB, leave this parameter blank.
password is the HTML DB password you passed as the first argument to the htmldbins.sql script.
nls_lang refers to the language setting. It must match the NLS settings of the database. For example:
American_America.AL32UTF8
If either the territory portion or the language portion of the NLS settings contain a space, you must wrap the value in double quotes, like the following example:
nls_lang = "ENGLISH_UNITED KINGDOM.AL32UTF8"
You can find information about your database's NLS settings by querying the view NLS_DATABASE_PARAMETERS as shown in the following example:
SELECT parameter,value
FROM nls_database_parameters
WHERE PARAMETER IN ('NLS_CHARACTERSET','NLS_LANGUAGE','NLS_TERRITORY');
Leave the remaining settings, including the username setting, as they appear in the previous example.
Save and exit the wdbsvr.app file.
You need to modify the httpd.conf file to include an alias that points to the file system path where you copied the images directory and add two new MIME types to support SQL Workshop.
See Also:
"Copying the Images Directory When Upgrading" and "Installing the Oracle HTML DB Software"To modify httpd.conf file:
Use a text editor and open the httpd.conf file
For UNIX and Linux based systems, the file is located at:
ORACLE_BASE/ORACLE_HOME/Apache/Apache/conf/httpd.conf
For Windows based systems:
ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf\httpd.conf
Add an alias entry that points to the file system path where you copied the images directory. The following examples assume you specified the image directory alias as /i/when you ran the htmldbins.sql script.
Windows based system example:
Alias /i/ "C:\oracle\ora92\Apache\Apache\images/"
Note you must include the forward slash (/) at the end of the path.
UNIX and Linux based system example:
Alias /i/ "/home/oracle/OraHome1/Apache/Apache/images/"
Next, you need to add two new MIME types to support SQL Workshop.
Add the following line if it does not currently exist:
AddType text/xml xbl
Add the following line if it does not currently exist:
AddType text/x-component htc
Save and exit the httpd.conf file.
Stop and restart Oracle HTTP Server.
For UNIX and Linux based systems, execute the following commands:
ORACLE_BASE/ORACLE_HOME/Apache/Apache/bin/apachectl stop ORACLE_BASE/ORACLE_HOME/Apache/Apache/bin/apachectl start
Note that if the Oracle HTTP Server is listening on a port less than 1024, the these commands must be executed as a privileged user (such as root).
For Windows based systems:
Stop Oracle HTTP Server - From the Start menu, select Programs, Oracle - OraHome, Oracle HTTP Server, and Stop HTTP Server.
Restart Oracle HTTP Server- From the Start menu, select Programs, Oracle - OraHome, Oracle HTTP Server, and Start HTTP Server.
See Also:
Oracle HTTP Server Administration GuideYou need to modify the marvel.conf file to include an alias that points to the file system path where you copied the images directory and add two new MIME types to support SQL Workshop.
See Also:
"Copying the Images Directory When Upgrading" and "Installing the Oracle HTML DB Software"To modify the marvel.conf file:
Use a text editor and open the marvel.conf file:
For UNIX and Linux based systems, the file is located at:
ORACLE_BASE/ORACLE_HOME/Apache/modplsql/conf/marvel.conf
For Windows based systems, the file is located at:
ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf\marvel.conf
Add the following line if it does not currently exist:
AddType text/xml xbl
Add the following line if it does not currently exist:
AddType text/x-component htc
Add an alias entry that points to the file system path where you copied the images directory.
Note you need to use the alias you specified in the fifth positional argument to htmldbins.sql. The following examples assume you specified the image directory alias as /i/.
Windows based system example:
Alias /i/ "C:\oracle\ora101\Apache\Apache\images/"
Note you must include the forward slash (/) at the end of the path.
UNIX and Linux based system example:
Alias /i/ "/home/oracle/OraHome1/Apache/Apache/images/"
Add an DAD entry for Oracle HTML DB using the following syntax. Replace the values PlsqlDatabasePassword, PlsqlDatabaseConnectString, and PlsqlNLSLanguage with values appropriate values for your environment.
<Location /pls/htmldb> SetHandler pls_handler Order deny,allow Allow from all AllowOverride None PlsqlDatabaseUsername HTMLDB_PUBLIC_USER PlsqlDatabasePassword htmldb PlsqlDatabaseConnectString localhost:1521:htmldbdv ServiceNameFormat PlsqlDefaultPage htmldb PlsqlDocumentTablename wwv_flow_file_objects$ PlsqlDocumentPath docs PlsqlDocumentProcedure wwv_flow_file_mgr.process_download PlsqlAuthenticationMode Basic PlsqlNLSLanguage AMERICAN_AMERICA.AL32UTF8 </Location>
If either the territory portion or the language portion of the NLS settings contain a space, you must wrap the value in double quotes, like the following example:
PlsqlNLSLanguage "ENGLISH_UNITED KINGDOM.AL32UTF8"
Save and exit the marvel.conf file.
(Oracle Application Server only) Execute the following commands:
For UNIX and Linux based systems:
ORACLE_BASE/ORACLE_HOME/dcm/bin/dcmctl updateConfig -ct ohs
For Windows based systems:
ORACLE_BASE\ORACLE_HOME\dcm\bin\dcmctl updateConfig -ct ohs
Stop and restart Oracle HTTP Server.
For UNIX and Linux based systems, execute the following commands:
ORACLE_BASE/ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server ORACLE_BASE/ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=HTTP_Server
For Windows based systems:
ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl stopproc ias-component=HTTP_Server ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=HTTP_Server
The Oracle HTML DB interface is translated into German, Spanish, French, Italian, Japanese, Korean, Brazilian Portuguese, Simplified Chinese, and Traditional Chinese. A single instance of Oracle HTML DB can be installed with one or more of these translated versions. At runtime, each user's Web browser language settings determine the specific language version.
The translated version of Oracle HTML DB should be loaded into a database that has a character set that can support the specific language. If you attempt to install a translated version of Oracle HTML DB into a database that does support the character encoding of the language, the installation may fail or the translated Oracle HTML DB instance may appear corrupt when run. The database character set AL32UTF8 supports all the translated versions of Oracle HTML DB.
You can manually install translated versions of Oracle HTML DB using SQL*Plus. The installation files are encoded in UTF8.
Note:
Regardless of the target database character set, to install a translated version of Oracle HTML DB you must set the character set value of theNLS_LANG environment variable to AL32UTF8 prior to starting SQL*Plus.The following examples illustrates valid NLS_LANG settings for loading Oracle HTML DB translations:
American_America.AL32UTF8 Japanese_Japan.AL32UTF8
To install a translated version of Oracle HTML DB:
Set the NLS_LANG environment variable, making sure that the character set is AL32UTF8. For example:
Bourne or Korn shell:
NLS_LANG=American_America.AL32UTF8 export NLS_LANG
C shell:
setenv NLS_LANG American_America.AL32UTF8
For Windows based systems:
set NLS_LANG=American_America.AL32UTF8
Start SQL*Plus and connect to the target database as SYS.
Execute the following statement:
ALTER SESSION SET CURRENT_SCHEMA = FLOWS_020000;
Execute the appropriate language specific script. For example:
@load_de.sql
The installation scripts are located in subdirectories identified by a language code in the unzipped distribution /htmldb/builder. For example, the German version is located in /htmldb/builder/de and the Japanese version is located in /htmldb/builder/ja. Within each of these directories, there is a language loading script identified by the language code (for example, load_de.sql or load_ja.sql).
JOB_QUEUE_PROCESSES determine the maximum number of concurrently running jobs. In Oracle HTML DB release 2.0, transactional support and SQL scripts require jobs. If JOB_QUEUE_PROCESSES is not enabled and working properly, you cannot successfully execute a script.
Topics in this section include:
There are currently three ways to view the number of number of JOB_QUEUE_PROCESSES:
In the installation log file
On the About HTML DB page in Oracle HTML DB
From SQL*Plus
After installing or upgrading Oracle HTML DB to release 2.0, you can view the number of JOB_QUEUE_PROCESSES in the installation log files.
You can also view the number of JOB_QUEUE_PROCESSES on the About HTML DB page.
To access the About HTML DB page:
Log in to Oracle HTML DB. See "Logging in to Oracle HTML DB".
Click the Administration icon.
From the Tasks list, select About HTML DB.
The current number JOB_QUEUE_PROCESSES displays at the bottom of the page.
You can change the number of JOB_QUEUE_PROCESSES by running a SQL statement in SQL*Plus:
To update the number of JOB_QUEUE_PROCESSES:
Log into the database as SYSDBA using SQL*Plus.
In SQL*Plus run the following SQL statement:
ALTER SYSTEM SET JOB_QUEUE_PROCESSES = <number>
For example, running the statement ALTER SYSTEM SET JOB_QUEUE_PROCESSES = 20 sets JOB_QUEUE_PROCESSES to 20.
The PlsqlDatabasePassword parameter specifies the password for logging in to the database. You can use the dadTool.pl utility to obfuscate passwords in the dads.conf file.
You can find the dadTool.pl utility in the following directory:
For UNIX and Linux based systems:
ORACLE_BASE/ORACLE_HOME/Apache/modplsql/conf
For Windows based systems:
ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf
In a new installation, the PlsqlDatabasePassword parameter is found in the dads.conf file. To obfuscate passwords in a new installation, run the dadTool.pl utility by following the instructions in the dadTool.README file.
If you have upgraded from a previous release, the DAD information is in the file marvel.conf. Before you can run the dadTool.pl utility, you must copy the DAD entry from the marvel.conf file to the dads.conf file.
To obfuscate passwords when upgrading:
Use a text editor and copy the entry for /pls/htmldb from the marvel.conf file into the dads.conf file.
For UNIX and Linux based systems, these files are located in:
ORACLE_BASE/ORACLE_HOME/Apache/modplsql/conf/dads.conf
For Windows based systems, these files are located in:
ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf\dads.conf
Run dadTool.pl by following the instructions in the dadTool.README file.
Copy the entry for /pls/htmldb from the dads.conf file back into marvel.conf.
Remove the entry for /pls/htmldb from the dads.conf file.
You open the Oracle HTML DB home page in a Web browser. To view or develop Oracle HTML DB applications, the Web browser must support JavaScript and the HTML 4.0 and CSS 1.0 standards. The following browsers meet this requirement:
Microsoft Internet Explorer 6.0 or higher (Windows only)
Netscape Communicator 7.0 or higher
Mozilla 1.2 or higher
Firefox 1.0 or higher
To log in to Oracle HTML DB, open the following URL in a Web browser:
http://hostname:port/pls/database_access_descriptor/
Where:
hostname is the name of the system where Oracle HTTP Server is installed.
port is the is the port number assigned to Oracle HTTP Server.
In a default installation, this number is 7777. You can find information about your Oracle HTTP Server installation's port number from the httpd.conf file, located in ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf, by searching for Port.
You can also find the port number in the portlist.ini file, located in ORACLE_BASE\ORACLE_HOME\install. However, be aware that if you change a port number, it is not updated in the portlist.ini file, so you can only rely on this file immediately after installation.
database_access_descriptor describes how Oracle HTTP Server connects to the database server so that it can fulfill an HTTP request. The default value is htmldb.
See Also:
ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf\dads.readme for more information on database access descriptorsThe Oracle HTML DB Login page appears.
In the Oracle HTML DB development environment, users log in to a shared work area called a workspace. Users are divided into three primary roles:
Developers create and edit applications.
Workspace administrators perform administrator tasks specific to a workspace such as managing user accounts, monitoring workspace activity, and viewing log files.
Oracle HTML DB administrator are superusers that manage an entire hosted instance using the Oracle HTML DB Administration Services application.
If you are a developer, an administrator must grant you access to a workspace. If you are an Oracle HTML DB administrator, you need to:
Log into Oracle HTML DB Administration Services. Oracle HTML DB Administration Services is a separate application for managing an entire Oracle HTML DB instance.
Specify a provisioning mode. In Oracle HTML DB Administration Services you need to determine how the process of creating (or provisioning) a workspace will work in your development environment.
Create a Workspace. A workspace is a shared work area within the Oracle HTML DB development environment that has a unique ID and name. An Oracle HTML DB administrator can create a workspace manually or have users submit requests.
Log in to a Workspace. Once you create a workspace in Oracle HTML DB Administration Services, return to the Oracle HTML DB Login page and log in to that workspace.
See Also:
"Quick Start" and "Managing an Oracle HTML DB Hosted Service" in Oracle HTML DB User's Guide
|
 Copyright © 2004, 2005, Oracle. All rights reserved. Legal Notices |
|