Oracle Application Server Containers for J2EE 10g (10.0.3.0.0) Developer Preview
Enterprise Web Services

Content

• Introduction
• Installation
• Environment Setup
• Running an OC4J instance
• New Features in the OC4J 10g (10.0.3) Developer Preview
• How To Examples for OC4J 10g (10.0.3) Developer Preview

Introduction

The Oracle Application Server 10g (10.0.3.0) Developer Preview includes the first version of Oracle's JAX-RPC Web Services implementation. It follows the J2EE 1.4 specification, which includes a JAX-RPC 1.1 runtime (see: http://java.sun.com/xml/jaxrpc/) as well as JSR 109 deployment (see http://www.jcp.org/en/jsr/detail?id=109). This document describes the installation steps for running the provided Web Services sample code, it outlines changes against earlier Oracle Web Services implementations, and it lists known restrictions and problems.

Please visit the Oracle Technology Network OTN Web Services Center at http://otn.oracle.com/tech/webservices for current information and to learn about the most recent updates. You can provide feedback and can get questions answered in the OTN Web Services forum at http://www.oracle.com/forums/forum.jsp?forum=97.

Please note that we are also providing the 9i Web Services stack (“Oracle J2EE Web Services”) for backward compatibility. This distribution does not include documentation or sample code for that implementation. Please refer to the original Oracle 9iAS (version 9.0.3 or later) documentation and examples for detailed information.

Installation

Software Requirements

Running the provided JAX-RPC Web Services samples requires the following software.

• Sun's JDK, version 1.4_01 or above must be used. It is available at http://java.sun.com/j2se/.
  Note: the demos require JDK 1.4.x and above to run.
  
• Jakarta Ant is required to build the application examples. It is available from http://jakarta.apache.org/ant/index.html.
  
• OC4J 10g (10.0.3) Developer Preview must be installed. It is available from the Oracle Technology Network (OTN) at http://otn.oracle.com/tech/java/oc4j/1003/content_preview.html.
  
  In order to install OC4J you need to expand the downloaded zip file into a directory that will become your oc4j root directory.
  
  Next you run the OC4J installation: java -jar OC4J_HOME/j2ee/home/oc4j.jar -install
  
  You will be prompted for a password. In the common.xml file it is assumed that this password is 'welcome'. If you are using a different admin password for OC4J, please modify the oc4j.admin.pwd property in common.xml accordingly.

Environment Setup

The following environment setup must be performed before running any of the examples.

• Set the ORACLE_HOME environment variable to your oc4j root directory.
  Example: set ORACLE_HOME=c:\oc4j
• Set the J2EE_HOME environment variable to your oc4j\j2ee\home directory.
  Example: set J2EE_HOME=c:\oc4j\j2ee\home
• Set the JAVA_HOME environment variable to your java installation directory.
  Example: set JAVA_HOME=c:\j2sdk1.4

Some of the examples, such as JMS Web Services, CORBA Web Services, and Database Web Services require additional installed software, as well as additional setup steps. Please make sure to follow the instructions provided by their respective how-to files.

Running an OC4J Instance

The OC4J instance must be running. It is recommended that OC4J be started as follows:
java -Xmx256M -jar oc4j.jar.

If OC4J is not running on localhost, port 8888, you will have to modify the ANT script (build.xml) in the respective sample directory to use the correct host and port to your server in the service.url property. In addition, you would need to modify this script if your Web Services connections are made through an HTTP proxy. Add the following two elements to the Java invocation in the "run-demo" target:
<java ...>
<jvmarg value="-Dhttp.proxyHost=your_proxy_host"/>
<jvmarg value="-Dhttp.proxyPort=your_proxy_port"/>
<arg .../> ... </java>

Once you have the server configured and running, just type ant from the top level directory of the example. The service artifacts and implementation class will be compiled and placed into a WAR which is then placed into an EAR. The EAR will be deployed to OC4J. Next the stubs and client will be compiled. Finally the service will be invoked by the client and you should see the output both in the server's message output and on the stdout of the client.

New Features in the OC4J 10g (10.0.3) Developer Preview

How To Examples for OC4J 10g (10.0.3) Developer Preview