OTN XML DB Sample: Standalone SAX Loader Application - Install

Table of Contents

• Required Software
• Installation and Configuration
  
• Extracting the Source Code
• Configuring the Application
• Compiling and Running the Application
  
• Compiling and Running the Application with Oracle9i JDeveloper
• Compiling and Running the Application with JDK 1.3
• Description of the Application related Files

Following software are required for running this application

• Oracle9i Database (Oracle 9.2.0.2 or later release)
• Oracle9i JDeveloper downloadable from OTN
  (or)
  JDK(Java Developer's Kit)1.3 or higher downloadable from http://java.sun.com
  
  Note: SAX Loader application has been certified with Red Hat Linux Advanced Server 2.1, Solaris 5.6 and Windows NT 4.0, 2000.

Refer below for step-by-step instructions on extracting files, installing and configuring other systems to successfully run this application.

Extracting the Source Code

The application files are stored in an archive named SAXLoader.jar. Download the archive and extract it to a convenient directory. Execute following command to extract the files:

 jar xvf SAXLoader.jar

Note: You will find jar.exe in JDK_HOME\bin. Ensure JDK_HOME\bin is present in your system path.
(JDK_HOME is the root directory of the JDKx.x installation).

The archive SAXLoader.jar extracts the files that implement the application. All the files are extracted into the SAXLoader directory.

Details of the individual files extracted that are related to this application can be viewed in the Application files description section .

Configuring the Application

1. Login to SQL*Plus in your Oracle9i database using the Scott user account.

2. The XML Schema (to which the XML documents being inserted need to conform to) should be registered in the database for successful running of this application. Refer here for more details on XML schema registration. For example:

declare
  doc varchar2(2000) := '<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb">
    <xs:element name="ACCOUNT">
      <xs:complexType xdb:SQLType="XML_ACCOUNT">
        <xs:sequence>
          <xs:element name="ACC_NO" type="xs:float" nillable="false"/>
          <xs:element name="CST_ID" type="xs:float"/>
          <xs:element name="ACC_BALANCE" type="xs:float" default="0" nillable="false"/>
          <xs:element name="ACC_CREDITLIMIT" type="xs:float"/>
          <xs:element name="ACC_CREATEDATE" type="xs:date"/>
          <xs:element name="ACC_CARDTYPE" type="xs:string"/>
          <xs:element name="ACC_ENABLED" type="xs:boolean"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:schema>';
begin
  dbms_xmlschema.registerSchema('/xmldb/account.xsd', doc);
end;
/

3. The Schema based XMLType table into which the XML content will be inserted should also exist in the database for successful running of this application. If the table does not exist, please create XMLType table based on the XML Schema. For example , say if your XML schema URL is /xmldb/account.xsd and you wish to create an XMLType table ACCOUNTS_TABLE based on this schema, you can create one by executing SQL statement as:

CREATE TABLE accounts_table OF XMLType
  XMLSCHEMA "/xmldb/account.xsd"
  ELEMENT "ACCOUNT";

4. Edit the SAXLoader.xml file extracted under SAXLoader\config directory. The following parameters in the SAXLoader.xml should be modified as described below:

a. Your database schema details. For example the following Elements tag value needs to be modified to reflect the connecting database schema details: 

b. The details of the source file from which the data needs to be inserted into the database. Also the node name in the file which denotes the start of an XML document needs to be specified. For example: the following Elements tag value need to be modified to reflect the required values:

c. Details for the number of threads that need to be spawned and count of the INSERTS after which the database commit needs to take place, during the insertion operation also needs to be specified. For example the following Elements tag value need to be modified to reflect the the required values:

d. The logging mode for the application log that will be generated during the execution of the program. This application provides for logging the trace output onto the system console or write the same output into a log file. The following element tag value needs to be modified to specify the logging mode:

5. Edit the BaseApplication.java file extracted under SAXLoader\src\oracle\otnsamples\xmldb\saxloader\common\baseApp directory. Modify the DEFAULT_CONNECTION_SETTINGS static variable value so that it points to the location where SAXLoader.xml has been extracted. For doing this substitute c:\\temp\\xml\\SAXLoader.xml path in the following line with the directory path where SAXLoader.xml has been extracted. Please specify the directory path in accordance with the Operating System.

public static final String DEFAULT_CONNECTION_SETTINGS = "c:\\temp\\xml\\SAXLoader.xml";

6. JDBC OCI Configuration

For running the application with the OCI driver, the system should have the Oracle database or Oracle database client installed. Also, ensure that the following environment variables are set:

On Windows, ensure the following:

i) ORACLE_HOME\lib directory is in the PATH
ii) ORACLE_HOME\bin directory is in the PATH

On Solaris and Linux, (in Korn shell) :
Set LD_LIBRARY_PATH as follows:

export LD_LIBRARY_PATH=$ORACLE_HOME/lib