Oracle9i Application Server Migrating From WebSphere Release 2 (9.0.2) Part Number A95110-01 |
|
This chapter compares WebSphere Advanced Edition 3.5.3 to Oracle9iAS OC4J in the following areas:
Oracle9iAS OC4J takes only a few minutes to install and start.
OC4J uses standard, easy-to-configure .xml
files for server configuration and J2EE applications deployment. An administration repository (Oracle9iAS infrastructure) is not required unless a cluster with more than one Oracle9iAS instance is required.
OC4J is fully complaint with the latest Servlet 2.3 API
OC4J is fully complaint with EJB 1.1 and also supports advanced features of EJB 2.0 (WebSphere 4.0 does not support the EJB 2.0 spcification).
Table A-1 shows the level of J2EE support provided by versions of WebSphere and OC4J.
OC4J supports more than one prepared SQL statement simultaneously. This significantly improves database access performance in OC4J as compared to WebSphere.
CallerInRole
does not work (a NotImplemented
exception is thrown).
OC4J is fully compliant with J2EE 1.2 security APIs.
OC4J uses a very efficient and optimized RMI (ORMI).
InitialContext
nor the EJBhome
objects. As a framework, it uses lookups extensively through the homes, with each home lookup equal in performance cost to executing 4 DB "SELECTs". It is recommended that you build a caching "HomeFactory" for application use as well as make changes to the association framework so that it also uses the caching "HomeFactory". These functionalities should be addressed by the EJB server itself (as they are by OC4J).
OC4J requires very minimal tuning as compared to WebSphere. The latest release of WebSphere, version 4.0, replaces support for multiple transport protocols with a single HTTP-IIOP protocol to commnicate between the HTTP server and application server.
|
Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|