|
Oracle® Containers for J2EE Developer's Guide
10g Release 3 (10.1.3) Part No. B14433-01 |
|
 Previous |
 Next |
|
Oracle® Containers for J2EE Developer's Guide
10g Release 3 (10.1.3) Part No. B14433-01 |
|
|
Previous |
Next |
This chapter describes OC4J and demonstrates how to install OC4J with the Oracle Application Server installation.
This chapter includes the following topics:
Oracle Containers for J2EE 10g Release 3 (10.1.3), or OC4J, provides a complete Java 2 Enterprise Edition (J2EE) 1.4-compliant environment.
OC4J provides all the containers, APIs, and services that J2EE specifies. It is based on technology licensed from Ironflare Corporation, which develops the Orion server—one of the leading J2EE containers. As such, the product and some of the documentation still contains some reference to the Orion server.
OC4J is written entirely in Java and executes on the Java Virtual Machine (JVM) of the standard Java Development Kit (JDK). You can run OC4J on the standard JDK that exists on your operating system.
The Oracle Containers for J2EE Release 3 (10.1.3) includes a number of new features and enhancements, which are summarized below.
OC4J provides full support for Web Services in accordance with the J2EE 1.4 standard, including JAX-RPC 1.1. Web Services interoperability is also supported.
EJB 2.1 Web services end point model
JSR 109 client and server deployment model
CORBA Web services: Support for wrapping existing basic CORBA Servants as Web services and auto-generating WSDL from IDL
Support for source code annotations to customize Web services behavior such as invocation and ending styles (RPC/literal, RPC/encoded, Doc/literal); customizing the Java to XML mapping; enforcing security.
Database and JMS Web services
OC4J supports the following specifications and JSRs which define new standards for deploying and managing applications in a J2EE environment.
The Java Management Extensions (JMX) 1.2 specification, which allows standard interfaces to be created for managing resources, such as services and applications, in a J2EE environment. The OC4J implementation of JMX provides a JMX client that can be used to completely manage an OC4J server and applications running within it.
The J2EE Management Specification (JSR-77), which enables standard interfaces to be created for managing applications in a J2EE environment.
The J2EE Application Deployment API (JSR-88), which defines a standard API for configuring and deploying J2EE applications and modules into a J2EE-compatible environment. The OC4J implementation includes the ability to create and/or edit a deployment plan containing the OC4J-specific configuration data needed to deploy a component into OC4J.
Oracle Application Server TopLink is an advanced, object persistence framework for use with a wide range of Java 2 Enterprise Edition (J2EE) and Java application architectures. OracleAS TopLink includes support for the OC4J Container Managed Persistence (CMP) container and base classes that simplify Bean Managed Persistence (BMP) development.
The OracleAS Job Scheduler provides asynchronous scheduling services for J2EE applications. Its key features include capabilities for submitting, controlling and monitoring jobs, defined as a unit of work that executes when the work is performed.
The new Distributed Transaction Manager in OC4J can coordinate two-phase transactions between any type of XA resource, including databases from Oracle as well as other vendors and JMS providers such as IBM WebsphereMQ. Automatic transaction recovery in the event of a failure is also supported.
The Generic JMS Resource Adapter can now be used as an OC4J plug-in for OracleAS JMS that ships with the current version of OC4J as well as for IBM WebsphereMQ JMS version 5.3.
Support for lazy transaction enlistment has been added so that JMS connections can be cached and still be able to correctly participate in global transactions.
Finally, the Generic JMS Resource Adapter now has better error handling. Endpoints now automatically retry after provider or system failures, and onMessage errors are handled correctly.
OC4J supports and is certified for the standard J2EE APIs, as listed in Table 1-1.
Table 1-1 OC4J J2EE Support
| J2EE Standard APIs | Version Supported By OC4J |
|---|---|
| JavaServer Pages (JSP) | 2.0 |
| Servlets | 2.4 |
| Enterprise JavaBeans (EJB) | 2.1
3.0 (Requires JDK 5.0. Support is based on the Enterprise JavaBeans 3.0 Early Draft Review specification.) |
| Java Management Extensions (JMX) | 1.2 |
| J2EE Management | 1.0 |
| J2EE Application Deployment | 1.1 |
| Java Transaction API (JTA) | 1.0 |
| Java Message Service (JMS) | 1.1 |
| Java Naming and Directory Interface (JNDI) | 1.2 |
| Java Mail | 1.2 |
| Java Database Connectivity (JDBC) | 3.0 |
| Oracle Application Server Java Authentication and Authorization Service (JAAS) Provider
|
1.0 |
| J2EE Connector Architecture | 1.5 |
| Java API for XML-Based RPC (JAX-RPC) | 1.1 |
| SOAP with Attachments API for Java (SAAJ) | 1.2 |
| Java API for XML Processing (JAXP) | 1.2 |
| Java API for XML Registries (JAXR) | 1.0.5 |
Most of the location of J2EE subject matter is obvious. For example, you can find out how to implement and use servlets within the Oracle Containers for J2EE Servlet Developer's Guide. Table 1-2 shows each J2EE subject matter and where you can find the information in the OC4J documentation set.
Table 1-2 Location of Information for J2EE Subjects
| J2EE Subject | The Subject is Documented in this OC4J Documentation Book |
|---|---|
| JSP | Oracle Containers for J2EE Support for JavaServer Pages Developer's Guide |
| JSP Tag Libraries | Oracle Containers for J2EE JSP Tag Libraries and Utilities Reference |
| Servlet | Oracle Containers for J2EE Servlet Developer's Guide |
| EJB | Oracle Containers for J2EE Enterprise JavaBeans Developer's Guide |
| JTA | Oracle Containers for J2EE Services Guide |
| Data Source | Oracle Containers for J2EE Services Guide |
| JNDI | Oracle Containers for J2EE Services Guide |
| JMS | Oracle Containers for J2EE Services Guide |
| RMI and RMI/IIOP | Oracle Containers for J2EE Services Guide |
| Security | Oracle Containers for J2EE Security Guide |
| CSiV2 | Oracle Containers for J2EE Security Guide |
| JCA | Oracle Containers for J2EE Services Guide |
| Java Object Cache | Oracle Containers for J2EE Services Guide |
| Web Services | Oracle Containers for J2EE Web Services Developer's Guide |
| HTTPS | Oracle Containers for J2EE Services Guide |
OC4J is a lightweight container that is J2EE-compliant. It is configured with powerful and practical defaults and is ready to execute after installation. OC4J is installed with Oracle Application Server; therefore, see the Oracle Application Server Installation Guide for details on OC4J installation.
