The best place to get technical information about OC4J is on the OC4J home page on OTN -- http://otn.oracle.com/tech/java/oc4j.

OC4J standalone is the Oracle9iAS Containers for J2EE distribution which can be run outside of the complete Oracle9iAS environment. OC4J standalone is typically used for development and testing purposes, and could be used for simple small scale Web solutions.

Documentation for all Oracle products is available from the Oracle Technology Network (OTN) -- http://otn.oracle.com/documentation/content.html. The specific documentation set for OC4J is available at http://otn.oracle.com/documentation/appserver10g.html. A User's Guide for OC4J standalone is supplied with the OC4J standalone distribution. The Readme.txt file in the root directory of the OC4J standalone distribution provides a set of basic information on how to install and use the product.

OC4J standalone comes with a command line utility, admin.jar. This enables you to perform a set of administrative functions from the command line. Also, you may directly modify the XML configuration files in the OC4J standalone environment.

You define OC4J datasources in an XML file known as data-sources.xml. If you're using Oracle9iAS, please use Enterprise Manager(EM) to create and configure datasources. With OC4J standalone use admin.jar or edit the data-sources.xml. Refer to the OC4J standalone user's guide

Remote Method Invocation (RMI) in enables developers to build distributed applications in java. However RMI calls are normally blocked by firewalls. RMI HTTP tunneling is a RMI implementation to provide a way for RMI to get through firewalls using HTTP. Your global-web-application.xml should have this entry: <servlet> <servlet-name>rmi</servlet-name> <servlet-class>com.evermind.server.rmi.

All official certification information for Oracle products is available on the Oracle support Web site, http://metalink.oracle.com.

The best place to get technical information about OC4J is on the OC4J home page on OTN -- http://otn.oracle.com/tech/java/oc4j. The OC4J Feature Overview lists the features available in the OC4J 10g (9.0.4) release.

To instal OC4J standalone, unzip the oc4j_extended.zip file using the archive utility of your choice. The jar utility in your J2SE installation can also be used. To complete the installation of OC4J change to the <install-dir>j2ee/home directory, and issue the following command: > cd <install-dir>/j2ee/home The installation prompts you to enter and verify an administration password, which is used for the administration console command-line tool.

a) To start OC4J using the default configuration files (recommended), which are located in the j2ee/home/config directory. > cd <J2EE_HOME> The server outputs an initialization string with the version number when it is ready to accept requests, for example: Oracle Application Server Containers for J2EE 10g (9.0.4.0.0) initialized

You can stop OC4J by pressing ^c (Ctrl+c) in the window where the process was started, or by using the shutdown command in the admin.jar command-line utility, or by using the process termination command (for example "kill" on UNIX/Linux) for your operating system.

The default HTTP port of OC4J standalone is 8888. This is specified in the configuration file <J2EE_HOME>/config/http-web-site.xml. If you have installed one of the Oracle Application Server distributions instead of OC4J standalone, then you must access Web applications deployed on OC4J via Oracle HTTP Server. The default port of Oracle HTTP Server is 7777.

OC4J uses data sources to define connections to databases. When OC4J starts, it creates DataSource objects based on it's configuration information. These DataSource objects act as connection factories, and allow applications to obtain a connection without knowing the physical details of the database being used. Data sources are defined by default in the file J2EE_HOME/config/data-sources.xml.

The features of OC4J 9.0.3 are described in the feature overview document available at /tech/java/oc4j/index.html

In Oracle9iAS Release 2, OC4J is started as a managed process by Oracle Process Management Notification (OPMN). This provides automatic startup, shutdown and death detection functionalities for OC4J processes. For environments which require the use of OC4J as a service, Oracle9iAS should be used. Create a service for the this command file using NT/Win2k Resource Kit. You can use the following Microsoft article how to create a service: http://support.microsoft.com/support/kb/articles/q137/8/90.

The command line deployment tool (admin.jar) requires an EAR file as it's deployment archive. To deploy a WAR file using this, you must package the WAR file within a EAR file. You can manually deploy a WAR file to OC4J However following are the steps involved in deploying a WAR file in OC4J. Open the default-web-site.

Assuming your OC4J home is $J2EE_HOME, the resource adapter is packaged in standalone_ra.rar, and you'd like to name the resource adapter "standalone". Then you need to create a directory named "standalone" in $J2EE_HOME/connectors, copy standalone_ra.rar to $J2EE_HOME/connectors/standalone, add the following to J2EE_HOME/config/oc4j-connectors.xml: <connector name="standalone" path="standalone_ra.

Assuming your OC4J home is $J2EE_HOME, the resource adapter is packaged in embedded_ra.rar. You need to assemble the resource adapter (embedded_ra.rar) into an application module (EAR file) along with other application components, add the following to the application deployment descriptor of your application module (/META-INF/applicatoin.xml): ... <application> ... <module> <connector>embedded_ra.rar</connector> </module> ..

The following example on Oracle Technology Network shows you how to deploy a resource adapter on OC4J: If you see an error saying config-property "connectionURL" does not exit, you need to modify the resource adapter descriptor ra.xml (located at $J2EE_HOME/connectors/standalone/standalone_ra/META-INF/ra.xm for standalone resource adapter and $J2EE_HOME/applications/your_application_name/embedded_ra/META-INF/ra.xml for embedded resource adapter).