Each session (virtual Java VM) executes the following items:

• Java Server Pages (JSP)
• Servlets
• Java Stored Procedures

OSE in Oracle 8.1.7 supports servlets 2.1 and JSPs 1.0.

OSE in Oracle 9.0.1 supports servlets 2.2 and JSPs 1.1.

OSE is no longer supported in Oracle 9.2.0.

1. By connecting to an OSE Web service directly through a dispatcher. (Connection Type #2)
2. By connecting to an Oracle listener that is configured to hand HTTP requests off to an OSE Web service (through a dispatcher). (Connection Type #3)
3. By connecting to the Oracle HTTP Server (powered by Apache), and routing HTTP client requests through mod_ose to the Oracle Servlet Engine in an Oracle (database) server. (Connection Type #4)

The first of these possibilities can be useful for debugging, or for quick testing of deployed servlets. But because it does not provide adequate scaling when multiple clients are involved, it should never be used when developing or testing production applications.

The second possibility can serve when your application consists solely of stateful servlets or JSPs. This, however, is true of few applications.

The third possibility is the one that Oracle recommends for all applications. Static HTML pages and other static data are served from the Oracle HTTP Server, and requests for dynamic content are routed through mod_ose to the OSE. To set up your application to run in this mode, there are additional configuration steps that you must perform. For example, you must configure the Apache mod_ose configuration file ose.conf to indicate which requests will be routed to the OSE.

It is also possible to use the Oracle HTTP Server with mod_ose to connect to OSE applications with a server configuration that does not normally use-shared servers

NOTE: Keep in mind that since OSE has a built-in web server. This web server allows direct access from an HTTP Client to the OSE, calling static HTML pages in the OS file system. In the detailed explanation below, this is considered as "Connection Type #1".

In the database initialization file (init.ora), create one or more dedicated dispatchers and servers with a specific service name. You can use any service name that follows the init.ora conventions as long as it differs from the database service name. The following examples use "MODOSE":

  mts_dispatchers="(PROTOCOL=tcp)(SERVICE_NAME=MODOSE)"

  mts_dispatchers="(PROTOCOL=tcps)(SERVICE_NAME=MODOSE)"

INST1_HTTP.IDEVELOPMENT.INFO =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)
                 (HOST = wwwdb3.idevelopment.info)
                 (PORT = 1521)
      )
    )
    (CONNECT_DATA =
      (SERVER = SHARED)
      (SERVICE_NAME = MODOSE)
      (PRESENTATION = http://admin)
    )
  )

# sess_sh
--Session Shell--
--type "help" at the command line for help message
$ createwebservice -root /iDevWebServer iDevWebServer

There are two types of WebService

• Single Domain Service
• Multi Domain Services

The Web domain identification for HTTP requests depends on OSE configuration:

Single Domain Services

The address part of the sent URL is actually ignored and the port that is used to connect to OSE solely determines the Web Domain. If that service is a Multi-Domain service, then the address part and server IP used to connect to the server are used to determine which domain to use.

This document does not explain Multi-domain service configuration.

# sess_sh
--Session Shell--
--type "help" at the command line for help message
$ createwebdomain -docroot /u01/app/oracle/oraweb /iDevWebServer

This example is based on a Single Domain Service configuration.

We have following options to connect to Oracle8i OSE using HTTP endpoints:

Before diving into the details of configuring OSE, there are a few requirements and installation steps that need to be taken.

• Make sure JServer is installed in the Oracle database server. This can be accomplished using the following:
  • Set the following instance parameters:

    parallel_automatic_tuning = false
    shared_pool_size          = 200000000
    java_pool_size            = 100000000

  • Run installation script:

    @$ORACLE_HOME/javavm/install/initjvm.sql

• Oracle HTTP Server (which can be installed as part of Oracle8i or Oracle9i database product set) installed under:

  $ORACLE_HOME/Apache

• Install correct JDK

  When you install the Oracle HTTP Server, you will be asked for the location of the JDK. This is usually not within the ORACLE_HOME path. We install the JDK in /usr/local/java for Linux and /usr/java for Solaris. All of my testing seems with have worked with Java 2 SDK 1.4.

• Install Oracle Servlet Engine

  $ORACLE_HOME/javavm/install/init_jis.sql

• Check and change if necessary the init.ora parameters for the Multi-Threaded Server (MTS) option:

  mts_dispatchers="(PROTOCOL=TCP)(DISPATCHERS=4)(CONNECTIONS=250)"

• Check and grant if necessary (as user SYS)

  SQL> GRANT JAVAUSERPRIV TO SCOTT;

At the command prompt, do the following to register endpoint for the admin service:

# cd $ORACLE_HOME\jis\install
# sess_sh -s jdbc:oracle:oci8:@ -u sys/change_on_install
--Session Shell--
--type "help" at the command line for help message
$ @serverendp.ssh admin 8080 9090 -register
$ exit

• Restart the listener.
• Restart the database.
• In the browser go to http://<your_machine name_OR_ip>:8080/
• This should give you the flying pig page verifying that you could reach the Oracle Servlet Engine.

This Web Service will be used throughout the remaining examples.

Here is a list of the variables and locations that will be set:

     Web Service Name           : iDevDemo
     Web Service Root Directory : iDevDemoRoot

• Invoke the session shell tool on the database server

  # sess_sh -u sys/change_on_install -s jdbc:oracle:oci8:@

• Create a Web Service and a Root Directory in the JNDI namespace

  sess> createwebservice -root /iDevDemoRoot iDevDemo

• Change the owners from SYS to SCOTT

  sess> chown -R SCOTT /iDevDemoRoot

• Define access rights

  sess> chmod -R +rwx SCOTT /iDevDemoRoot

• Create a Web Domain. The option -docroot defines the path of static HTML pages

  sess> createwebdomain -docroot /u01/app/oracle/oraweb/StaticPages /iDevDemoRoot

• Create a Context within the Web Domain

  sess> createcontext -virtualpath /iDevDemo -docroot /u01/app/oracle/oraweb/StaticPages /iDevDemoRoot iDevDemoContext

• Add a new Endpoint to the listener

  sess> addendpoint -port 7788 -register iDevDemo iDevEndpt01

• Setup access rights for the new objects

  sess> chmod -R +rwx SCOTT /iDevDemoRoot