When you create a new OracleAS instance under the Portal and Wireless middle-tier option (and also have the OracleAS Infrastructure instance installed), you automatically have the following OC4J instances:

• Home   This is the default OC4J instance that comes with every OracleAS installation.
   
• OC4J_Portal   This contains a servlet to support OracleAS Portal (middle tier).
  
• OC4J_Security  This supports Identity Management Services (infrastructure).
   
• OC4J_Wireless  This contains a servlet to support OracleAS Wireless (middle tier).
  
• oca   This supports the OracleAS Certificate Authority (infrastructure).

Although you can manage the OC4J process running inside OracleAS by editing the OC4J configuration files directly, that’s not the recommended way to manage OC4J when you use it as part of the OracleAS, as compared with using it in a standalone mode. The purpose behind including OC4J inside the OracleAS stack is to help manage J2EE enterprise systems. You must use the Oracle Application Server to manage all components of OracleAS, including OC4J.

Using the Application Server Control, it’s possible to manage and configure clustered OC4J processes across multiple OracleAS instances and hosts. Application Server Control provides clustering, high availability, load balancing, and failover capabilities to help you manage multiple OC4J instances.

on the job:  You must run OC4J with the JDK that is installed with Oracle Application Server Release 2 ( JDK 1.3.x) for optimal performance.

You can use either Application Server Control or command-line tools to start, stop, configure, and deploy applications. The two command-line tools you can use to manage OC4J instances are the familiar opmnctl and dcmctl utilities.

Please check back next week for the continuation of this article.