Uncover OC4J - Part 1

OC4J - Oracle Containers for Java

In this topic, I will be discussing the very basics of OC4J containers from Oracle. Although there are plethora of Java containers outside in the market, I always prefer the OC4J due to its architecture and modularity and the amount of flexibility in the maintenance.

OC4J is a Oracle developed propreitary module into the Apache Web server. Apache Web server is a Open Source web server which is picked up by Oracle and fine tuned Apache into Oracle Http Server (aka OHS).

Those who are new to OHS, OHS is Apache at its core. As Apache, OHS is also a module-based Webserver. Oracle has developed Java containers and incorporated this module into the OHS and called it OC4J (aka Oracle Containers for Java).

OC4J containers are based on J2EE specifications supported all the J2EE components like Servlets, JSPs, JAAS, JMS, Java Mail, JSFs, EJBs.

OC4J has multiple incarnations :) (aka versions)
- 1.0.2.2.x
- 9.0.2.x
- 9.0.3.x
- 9.0.4.x
- 10.2.2
- 10.1.3 - Most Recent version

There are 3 types of Deployment types for OC4J
- Standalone
- Embedded
- AS Component

Standalone OC4J
- comes as a ZIP file as oc4j_extended.zip file. You need not install anything. Simply uninstall the zip file and launch the process. This is purely written in Java from scratch and some options like JAZN-LDAP and SSO are not avaliable in this type of deployment. Generally used for quick testing and development of components.

AS Component
- comes with iAS installation CDs. Can be installed via OUI as a part of iAS installation. Have all the features enabled. Used in Production instances.

Embedded OC4J
- comes as a part of JDeveloper. Have all the features in it and also available at API level. Can be started and accessed via JDeveloper only.

Be there for some more stuff in Part II ....... :)