Release 2 (9.0.2)
Part Number A95879-01
 Home |
 Solution Area |
 Contents |
 Index |
| Oracle9iAS Containers for J2EE Services Guide Release 2 (9.0.2) Part Number A95879-01 |
|
Oracle9iAS Containers for J2EE (OC4J) supports the following technologies, each of which has its own chapter(s) in this book:
The remainder of this chapter gives a brief overview of each technology in the above list.
JNDI provides naming and directory functionality for Java applications. JNDI is defined independently of any specific naming or directory service implementation. As a result, JNDI enables Java applications to access different, possibly multiple, naming and directory services using a single API. Different naming and directory service provider interfaces (SPIs) can be plugged in behind this common API to handle different naming services. For information about the Oracle implementation, see Chapter 2, "Java Naming and Directory Interface".
RMI is one Java implementation of the remote procedure call paradigm, in which distributed applications communicate by invoking procedure calls and interpreting the return values. OC4J supports invoking RMI over HTTP, a technique known as "RMI tunneling." For information about the Oracle implementation, see Chapter 3, "Remote Method Invocation".
JAAS enables applications to authenticate and enforce access control. Oracle9iAS supports JAAS by implementing a JAAS provider. The JAAS provider provides application developers with user authentication, authorization, and delegation services to integrate into their application environments. Instead of devoting resources to developing these services, application developers can focus on the presentation and business logic of their applications.
For information about the Oracle implementation, see Chapter 4, "Overview of JAAS in Oracle 9iAS", Chapter 5, "Quick Start JAAS Provider Demo", Chapter 6, "Integrating the JAAS Provider with Java2 Applications", Chapter 7, "Managing the JAAS Provider", Chapter 8, "Developing Secure J2SE Applications", Chapter 9, "Developing Secure J2EE Applications", Appendix A, "JAAS Provider APIs" and Appendix B, "JAAS Provider Standards and Samples".
JTA supplies a standard interface to support communications among the parties to a distributed transaction. These parties include the resource manager, the application server, and the transactional applications. For information about the Oracle implementation, see Chapter 10, "Java Transaction API".
JMS provides a common way for Java programs to access enterprise messaging products. JMS is a set of interfaces and associated semantics that define how a JMS client accesses the facilities of an enterprise messaging product. For information about the Oracle implementation, see Chapter 11, "Java Message Service".
JCA defines a standard architecture for connecting the J2EE platform to heterogeneous Enterprise Information Systems (EISs). Examples of EISs include ERP, mainframe transaction processing, database systems, and legacy applications not written in the Java programming language.
For information about the Oracle implementation, see Chapter 12, "Java Connector Architecture".
The Java Object Cache (formerly OCS4J) is a set of Java classes designed to manage Java objects within a process, across processes, and on local disk. The primary goal of the Java Object Cache is to provide a powerful, flexible, easy to use service that will significantly improve server performance by managing local copies of objects that are expensive to retrieve or create. There are no restrictions on the type of object that can be cached or the original source of the object. The management of each object in the cache is easily customized. Each object has a set of attributes associated with it to control such things as how the object is loaded into the cache, where the object is stored, (in memory, on disk or both), how it is invalidated, (based on time or by explicit request) and who should be notified when the object is invalidated. Objects can be invalidated as a group or individually.
For information about the Oracle implementation, see Chapter 13, "Working With Java Object Cache".
HTTPS is vital to securing client-server interactions. Java applications that act as a clients, such as servlets that initiate connections to other Web servers, need their own HTTPS implementation to make requests and to receive information securely from the server. Java application developers who are familiar with the HTTP package, HTTPClient, or the Sun Microsystems, Inc., java.net package can easily use Oracle HTTPS to secure client interactions with a server. For information about the Oracle implementation, see Chapter 14, "Oracle HTTPS for Client Connections".
A data source, which is the instantiation of an object that implements the javax.sql.DataSource interface, enables you to retrieve a connection to a database server. For information about the Oracle implementation, see Chapter 15, "Data Sources".
|
 Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|
