README for OracleJSP 1.1.0.0.0 samples
**************************************


Steps for running the JSP samples on iAS, Oracle HTTP Server, and 
standard web servers:

- Copy the WEB-INF and demo directory to the doc root or application root
  of your web server
- Make sure all the related jar files are in your web server classpath; 
  they include ojsp.jar, ojsputil.jar, and the JDBC and SQLJ libraries
  if you are doing SQL operations.  For the XML demos, you will also 
  need xmlparserv2.jar and xsu12.jar. 

**************************************

Steps for running the JSP samples on Oracle Servlet Engine (OSE) in 8.1.7:

- loadjava jar files under WEB-INF/lib
- loadjava class files under WEB-INF/classes
- publishjsp all jsp and sqljsp files
- Copy all the static files (gif/jpg/htm files) to the doc root of 
  the context defined in OSE.

The $ORACLE_HOME/jsp/demo/Makefile illustrates these steps.
It deploys the samples as scott/tiger, assuming a certain context
and doc root.

*** You may need to change the parameters appropriately for your system. *** 

Below are some steps that you could follow in order to deploy and run
the JSP demos in Scott's schema:


[1] Run the OSE demo under ${ORACLE_HOME}/javavm/demo/examples/web/service/
(type make in this directory).  This demo will set up a service, webdomain, 
and context for Scott. 

[2] To hotload the literals in JSP source, you must grant the hotload
    permission to SCOTT. You can use the following commands in SQL*Plus
    to grant this permissions:

    % sqlplus /nolog

      connect sys/change_on_install as sysdba
      call dbms_java.grant_permission('SCOTT',
           'SYS:oracle.aurora.security.JServerPermission',
           'HotLoader', null);


[3] Then, you can run the JSP demo Makefile simply as :
    % cd ${ORACLE_HOME}/jsp/demo
    % make

 If you want to use different parameters, for example if you define your 
 own context, then you must invoke make with the appropriate arguments.  
 For example,

    % make USER=myuser PASSWORD=mypwd SERVICE=http://myhost:8080 \ 
                       CONTEXT=mycontext DOC_ROOT=mydocroot


[4] The JSP "events" demo requires Scott to create a public synonym
    for the globals.jsa class. You can use the following commands in
    SQL*Plus to do this:

    % sqlplus /nolog

      connect sys/change_on_install as sysdba
      grant create public synonym to scott;

      connect scott/tiger
      grant execute on "_demo/_ojspext/_events/_globals" to public ;
      create public synonym "_demo/_ojspext/_events/_globals" 
                        for "_demo/_ojspext/_events/_globals" ;


[5] Finally, you can invoke the JSP programs from your browser, for example
      http://localhost:8088/groove/demo/index.html

Here, groove is the virtual path specified for scottContext. Substitute the
name of your machine in the URL if it is not the local machine. 

**************************************

NOTE: To run the "helloxml" demo on OSE/8i, you will need to change   
      the following line in the file demo/xml/helloxml/hello.jsp
      from:  <jml:transform href="style/hello.xsl" >
        to:  <jml:transform href="/groove/demo/xml/helloxml/style/hello.xsl" >  

      This is a known limitation (bug #1399032) which will be fixed in a
      future release.

**************************************

Steps for running the CallEJB.jsp sample on OSE:

First, load and deploy the EJB in Oracle8i, including the generated
classes. If you are running on OSE, you must then load and publish the
JSP page in 8i/OSE. The steps are outlined below:

[1] Deploy the EJB object in 8i. On a UNIX system, commands such as the 
    following are required:
    # deploy the EJB
    % cd $ORACLE_HOME/javavm/demo/examples/ejb/basic/sqljimpl
    % make

[2] Now load and publish your JSP. You can use the demo Makefile:
    % cd $ORACLE_HOME/jsp/demo/
    % make compileJsp2EJB
    
    If you are using different servlet context, change the Makefile
    appropriatety. 

    Check the status of the deployed JSP class through SQL*Plus. It should
    be valid.

[3] To run CallEJB.jsp, you must consider the user privileges.
    The EJB is deployed as SCOTT. To access it from JSPs deployed as  
    SYS on OSE (as in the sample Makefile), you can either:
        a) Define a table synonym in SQL*Plus as follows:
           CREATE PUBLIC SYNONYM EMP FOR SCOTT.EMP;
    Or, b) Publish and run the JSP in schema SCOTT. Refer to the steps
           outlined earlier for the general make. 

[4] To hotload the JSP in schema SCOTT, you must first grant the hotload
    permission to SCOTT. You can use the following command in SQL*Plus
    to do this (as system/manager):

    call dbms_java.grant_permission('SCOTT',
      'SYS:oracle.aurora.security.JServerPermission',
      'HotLoader', null);

    Then, you can use the 'publishjsp -hotload -schema SCOTT ... CallEJB.jsp'
    command in session shell.
  
**************************************

Steps for running the CallCORBA.jsp sample on OSE:

[1] Deploy the CORBA object in 8i. On a UNIX system, commands like the 
    following are required:
    % cd $ORACLE_HOME/javavm/demo/examples/corba/basic/helloworld
    % make

[2] After the CORBA object has been deployed, you can use the 
    JSP demo Makefile to load and publish your JSP:
    % cd $ORACLE_HOME/jsp/demo
    % make compileJsp2CORBA

To hotload the JSP literals, refer to Step [4] above for CallEJB.jsp.


  *** Please be aware that the EJB and CORBA 'sqljimpl' samples 
      re-define the same Java types, so they cannot be deployed 
      simultaneously in 8i. ***

**************************************

The World of Books Example

This is a sample NLS application for an online Book store.  Please 
see the $ORACLE_HOME/javavm/examples/world-o-books directory for details.