R12 AND OC4J STANDARD

1)OC4J is used for executing Servlets,Java Server Pages (JSP), Enterprise Java B
eans (EJB)
2)OC4J replaces the older JServ implementation for running servlets on the web s
erver
3)Oracle Application Server 10gR3 (10.1.3) is the latest production version
OC4J is based on J2EE standards:Specific directory structure,File requirements (
content & naming conventions),XML file definitionOC4J instances run in JVM s and c
ommunicate through mod_oc4j / Apache
R12 creates 3 OC4J instances:
**************************************
Oacore: runs OA Framework-based applications
Forms: runs Forms-base applications
OAFM: runs web services, mapviewer, ascontrol
Number of OC4J instances for each group will be determined by corresponding npro
cs context variable ( s_oacore_nprocs, s_forms_nprocs/s_frmsrv_nprocs, s_oafm_np
rocs).
Servlets deployed to OC4J server adhere to J2EE specification
Deployment is through an Enterprise Archive (EAR) file, which contains the appli
cation definition and Web Application (WAR) files, which in turn includes the we
b application code (JAR), and associated configuration files (servlet definition
s), JSP code,HTML
Forms.EAR 10.1.2 is deployed to the OC4J container in Application Server 10.1.3A
utoConfig is used for configuration management similar to Release 11i.
Important files used for configuation of OC4J instances
Oc4j.properties : defines basic Apps directory aliasing,dbc file location is def
ined in this fileServer.xml : defines J2EE applications and their shared librari
es for runtime OC4J.
Orion-application.xml : defines location of Java classes of all J2EE web modules
deployed under J2EE. applicationOrion-web.xml : defines servlet level parameter
s for J2EE web modules.
These files are synomynous with jserv.conf,jserv.properties in 11i.
Oracle Process Manager and Notification server (OPMN) manages AS components and
consists of:
Oracle Notification Server (ONS):
Delivers notifications between components
OHS<->OPMN<->OC4J
Process Manager (PM) start,stop, restart, death detection
($ADMIN_SCRIPTS_HOME contains the Apps equivalent scripts called ad*)
Single configuration file(opmn.xml) is used OPMN to manage the services.
Config file location is given as $ORA_CONFIG_HOME/10.1.3/opmn/conf/opmn.xmlServi
ces managed by opmn are 1) HTTP_Server
2) oacore
3) forms
4) oafm
R12 Various LogFiles Locations :
Startup/Shutdown Log files for Application Tier in R12
$LOG_HOME/appl/admin/log/
Service Logfile Name
TNS Listener Start/Stop log adalnctl.txt
Fulfillment Server Start/Stop log jtffmctl.txt
Oracle HTTP Server start/stop log adapcctl.txt
Concurrent Managers and ICM start/stop log adcmctl.txt
Forms OC4J start/stop log adformsctl.txt
OACore OC4J start/stop log adoacorectl.txtq
OAFM OC4J start/stop log adoafmctl.txt
OPMN start/stop log adopmnctl.txtTech Stack 10.1.3 (Web/HTTP Server) Logs
Log File Name Log File Location
AD script log files (e.g.from adapcctl.sh) $INST_TOP/logs/appl/admin/log
CM Log Files ($APPLCSF/$APPLLOG) $INST_TOP/logs/appl/conc/log
AD tools log files (e.g. ADPATCH) $APPL_CONFIG_HOME/admin/$TWO_TASK/log
OPMN Log Files (text and ODL) $ORA_CONFIG_HOME/10.1.3/opmn/logs (may move to
$INST_TOP/logs/10.1.3/opmn)
Apache Log Files (text and ODL) $INST_TOP/logs/10.1.3/Apache/
OC4J Log Files (text) $INST_TOP/logs/10.1.3/j2ee/oacore/
OC4J Log Files (ODL) $INST_TOP/logs/10.1.3/j2ee/oacore/log/oacore_default_gro
up_1/oc4jLog files related to cloning in R12:
Preclone log files in source instance
Database Tier /$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/(StageDBTier_MMDDHHMM.log
)
Application Tier $INST_TOP/apps/$CONTEXT_NAME/admin/log/ (StageAppsTier_MMDDHHMM
.log)
Clone log files in target instance
Database Tier $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTier_.log
Apps Tier $INST_TOP/apps/$CONTEXT_NAME/admin/log/ApplyAppsTier_.log
Patching related log files in R12
Application Tier adpatch log $APPL_TOP/admin/$SID/log/
Developer (Developer/Forms & Reports 10.1.2) Patch $ORACLE_HOME/.patch_storage
Web Server (Apache) patch $IAS_ORACLE_HOME/.patch_storage
Database Tier opatch log $ORACLE_HOME/.patch_storage
Autoconfig related log files in R12
Database Tier Autoconfig log :
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/MMDDHHMM/adconfig.log
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/MMDDHHMM/NetServiceHandler.log
Application Tier Autoconfig log :
$INST_TOP/apps/$CONTEXT_NAME/admin/log/$MMDDHHMM/adconfig.log
Autoconfig context file location in R12
$INST_TOP/apps/$CONTEXT_NAME/appl/admin/$CONTEXT_NAME.xml
Other log files in R12
Database Tier
Relink Log files :
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME /MMDDHHMM/ make_$MMDDHHMM.log
Alert Log Files:
$ORACLE_HOME/admin/$CONTEXT_NAME/bdump/alert_$SID.log
Network Logs:
$ORACLE_HOME/network/admin/$SID.log
OUI Logs
OUI Inventory Logs :
$ORACLE_HOME/admin/oui/$CONTEXT_NAME/oraInventory/logs
Application Tier
$ORACLE_HOME/j2ee/DevSuite/log
$ORACLE_HOME/opmn/logs
$ORACLE_HOME/network/logs