These are the common log locations for various components under Application Server 10g.
Sr. | Component | Log Location | Comments |
1 | HTTP Server | $OH/Apache/Apache/logs | Contains Access log and Error logs. Logging can be controlled using LogLevel parameter in httpd.conf file under $OH/Apache/Apache/conf |
2 | OPMN | $OH/opmn/logs | Has start/stop logs for all components installed. E.g. HTTP, OID, SOA etc |
3 | SSO Server | $OH/sso/log/ssoServer.log | Has detailed logs of SSO server. Will also give information for user authentication failure etc. Can configure the log level in policy.properties under $OH/sso/conf |
4 | LDAP Server (OID) | $OH/ldap/log | Contains logging information about the ldap processes, syncrhronization processes (odisrv) and monitor process (oidmon). The logs for LDAP and ODISRV will have their PIDs suffixed to their name (oidldapd01s966746.log) |
5.1 | OC4J | $OH/j2ee/<instance_name>/log/oc4j/log.xml | This file contains all generic information about the specific J2EE instance. This is common for all J2EE versions (10.1.2.x, 10.1.4.x and 10.1.3.x). This is particularly useful in debugging ESB applications. |
5.2 | OC4J | $OH/j2ee/<instance_name>/log | This location has various different logs (jms, rmi, default-web-access, global-application etc). Dig under this folder to find out logging information related to jms/rmi issues. For example, if there is an issue in two systems interacting to each other using rmi protocol (which is mostly the case), you can check the rmi.log for information related to that.This is also common for all versions of Application Server. |
5.3 | OC4J | $OH/j2ee/<instance_name>/application-deployments/<application><instance_name_default_island_num> | An instance will have many applications deployed to it viz. sso, oiddas, esb-dt, bpel, ccore (wsm). The application specific logs are generated in this folder. For versions 10.1.2.x and 10.1.4.x an example of the location can be "$OH/j2ee/OC4J_SECURITY/application-deployments/oiddas/OC4J_SECURITY_default_island_1" (for OIDDAS application) and for version 10.1.3.x it would be "$OH/j2ee/oc4j_esbdt/application-deployments/esb-dt/oc4j_esbdt_SOA_ESBDT_1" (for ESB DT application). |
5.3 | OC4J | $OH/j2ee/<instance_name>/application-deployments/<application><instance_name_group_name> |
|
6 | DCM Server | $OH/dcm/logs | Contains logs for dcmctl commands. |
7 | IAS Console (10.1.2.x & 10.1.4.x) | $OH/sysman/log | Contains logging information about the iascontrol application used in versions 10.1.2.x and 10.1.4.x. For version 10.1.3.x there is no iascontrol instead there is em console (the application name is ascontrol). The log for that can be accessed as mentioned in point 5.3. |
8 | Webcache Server | $OH/webcache/logs | Has access and error logs for webcache. |
9 | Report Server | $OH/reports/logs/<report_server_name>/rwserver.log | All startup/shutdown information of reports server as well the engines is logged in this along with any other error messages. |
10 | Forms Server | $OH/forms/trace | If the trace is enabled for forms then this directory will contain all the trace dumps. You can get the name of the trace file from the iasconsole when you enable the trace for a form session. For information on formapps application check location at 5.3 (substitue formapps for application) |
11 | Portal Server | $OH/portal/logs | This directory contains only logging information from ptlconfig file. For a detailed portal application log check point 5.3. |
12.1 | BPEL Server | $OH/bpel/system/logs | This is basic directory having all BPEL specific logs. This will have system wide logs. |
12.2 | BPEL Server | $OH/bpel/domains/<domain_name>/logs | This directory contains only domain specific logs. |
