There are several files, in various directory locations, related to ACM as well as Oracle that may need to be reviewed or provided to Aveksa Technical Support while diagnosing problem tickets.

Here is a list of those which may be requested or referenced:

Related to Oracle:

ACM 3.6.x and 4.x, using Oracle 10g

Oracle AVDB Alert log: This file contains runtime information related to the Oracle 10g AVDB instance

/u01/app/oracle/product/admin/AVDB/bdump/alert_AVDB.log

Oracle ASM Alert log: This file contains runtime information related to the Oracle 10g +ASM instance

u01/app/oracle/product/admin/+ASM/bdump/alert_+ASM.log

Oracle ACM startup and shutdown logs: These files contain ONLY the startup or shutdown messages for the Oracle instance

/u01/app/oracle/product/10.2.0/db_1/startup.log

/u01/app/oracle/product/10.2.0/db_1/shutdown/log

ACM 5.x, 6.x with Oracle 11g, as well as RSA Via L&G with Oracle 12:

Oracle AVDB Alert log: This file contains runtime information related to the Oracle 11g AVDB instance

/u01/app/oracle/diag/rdbms/avdb/AVDB/trace/alert_AVDB.log

Oracle ASM Alert log: This file contains runtime information related to the Oracle 11g +ASM instance

/u01/app/oracle/diag/asm/+asm/+ASM/trace/alert_+ASM.log

Related to ACM:

3.6.x ACM Tomcat Server:

Tomcat Server Log: This file contains runtime information posted by the Tomcat Server

/usr/bin/tomcat/logs/catalina.out

Tomcat ACM Version file: This file contains the ACM product version information currently installed

/usr/bin/tomcat/webapps/aveksa/WEB-INF/classes/version.properties

4.0.x Jboss ACM Server (For V4, 5 and 6)

Jboss Server Log: This file contains runtime information for the Jboss Server and Aveksa Agent

/home/oracle/jboss/server/default/log/server.log

4.0.1 Jboss ACM Version Properties file: This file contains ACM product version information currently installed

/home/oracle/jboss/server/default/deploy/aveksa.ear/aveksa.war/WEB-INF/classes/version.properties

4.1 Jboss ACM Version Properties file: This file contains ACM product version information currently installed

/home/oracle/jboss/server/default/deploy/aveksa.ear/aveksa.war/WEB-INF/classes/aveksa-version.properties

4.1 Jboss ACM Aveksa Server log: This file contains the ACM runtime logging information:

/home/oracle/jboss/server/default/deploy/aveksa.ear/aveksa.war/log/aveksaServer.log

4.1 Jboss ACM Aveksa Info  log: This file contains the ACM version information:

/home/oracle/jboss/server/default/deploy/aveksa.ear/aveksa.war/log/aveksaServerInfo.log

For Wildfly (V8):  RSA Via L&G V7

Wildfly server information:
/home/oracle/wildfly-8.2.0.Final/standalone/log/server.log

Aveksa Server log: This file contains the RSA Via L&G  runtime logging information:
/home/oracle/wildfly-8.2.0.Final/standalone/log/aveksaServer.log

Aveksa Info  log: This file contains the ACM version information:
/home/oracle/wildfly-8.2.0.Final/standalone/log/aveksaServerInfo.log

4.x ACM UI log:

4.1 Jboxx ACM UI log file: This file contains ACM UI information. It is a link to the actual log file

/home/oracle/jboss/server/default/deploy/aveksa.ear/aveksa.war/log/aveksaUI.log --> gui_log.log

4.x ACM logging levels

aveksa-log4j.properties: This file controls the logging levels for ACM - you can adjust DEBUG/ERROR/INFO etc

/home/oracle/jboss/server/default/deploy/aveksa.ear/aveksa.war/WEB-INF/classes/aveksa-log4j.properties

3.6.x ACM Agent Logs:

Aveksa Agent: This contains runtime information from the Aveksa Agent

/home/oracle/AveksaAgent/logs/aveksaAgent.log

ITIM Agent: This file contains runtime information from the Aveksa ITIM Agent

/home/oracle/ITIMAgent/logs/aveksaAgent.log

4.x ACM Agent Logs:

Aveksa Agent: This information is now written to the Aveksa Jboss Server log (see above)

ITIM Agent: This file contains runtime information from the Aveksa ITIM Agent

/home/oracle/ITIMAgent/logs/aveksaAgent.log

4.1.x WebLogic logs:

Aveksa logs are pointed to in the Weblogic EAR file aveksa-log4j.properties file. In the event that these log files need to be renamed or have their default location changed, then the ear file must be unpacked, the properties file modified and the ear file recreated. NOTE that if changes like this are made, then these types of site specific changes may need to be re-applied whenever a new EAR file is distributed.

The absolute path for the actual location for the Aveksa log4j properties file in a WebLogic directory may vary from installation to installation.. however the eventual 'sub-directory' location will remain the same.. and will be in this location: ../../aveksa.war/WEB-INF/classes/aveksa-log4j.properties.

There is an additional file referenced in the EAR file, located at:

../../aveksa.war/WEB-INF/LocalAgent/conf/log4j.properties

However, this file is not usually needed with 4.x Aveksa installations.

The Aveksa Server log, will typically be found at a location similiar to that shown below, however, it may be different depending on the site specific installation:

.../../user_projects/domains/aveksaDomain/servers/AdminServer/tmp/_WL_user/aveksa/ldedze/aveksa.war/log/aveksaServer.log

4.2.x WebSpere ACM logs: note that the NODE name below may be different for each system

logs are located at:
/home/oracle/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/

-rw-r--r-- 1 oracle oinstall 0 Mar 7 15:19 native_stderr.log
-rw-r--r-- 1 oracle oinstall 0 Mar 7 15:19 native_stdout.log
-rw-r--r-- 1 oracle oinstall 4 Mar 21 10:19 server1.pid
-rw-rw-r-- 1 oracle oinstall 24405 Mar 21 10:19 startServer.log
-rw-rw-r-- 1 oracle oinstall 46975 Mar 21 10:09 stopServer.log
-rw-r--r-- 1 oracle oinstall 404363 Mar 18 14:35 SystemErr.log
-rw-r--r-- 1 oracle oinstall 1050158 Mar 18 10:59 SystemOut_11.03.18_10.59.57.log
-rw-r--r-- 1 oracle oinstall 701941 Mar 22 12:39 SystemOut.log

/home/oracle/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/vm-support-11Node01Cell/aveksa.ear/aveksa.war/log

-rw-r--r-- 1 oracle oinstall 11534 Mar 22 00:30 aveksaAudit.log
-rw-r--r-- 1 oracle oinstall 100026 Mar 22 12:17 aveksa.log
-rw-r--r-- 1 oracle oinstall 310273 Mar 22 12:39 aveksaServer.log
-rw-r--r-- 1 oracle oinstall 12521001 Mar 18 17:00 create_migrate.log
-rw-r--r-- 1 oracle oinstall 33355 Mar 21 10:29 GeneralMonitor.log
-rw-r--r-- 1 oracle oinstall 3151 Mar 21 10:19 WorkPoint.log

ACM Installation/Migration logs

Install:

/tmp/aveksa-install.log

Upgrade:

/home/oracle/upgrade/log/cleanup_schema.log

/home/oracle/upgrade/log/data_migration.log

/home/oracle/upgrade/log/post_schema_migration.log

/home/oracle/upgrade/log/pre_schema_migration.log

/home/oracle/upgrade/log/verification.log

Migration:

4.0.1

4.0.1 migrate logs - These files are created when the migration is started from the command line:

/home/oracle/upgrade/log/

/home/oracle/upgrade/log/cleanup_schema.log

/home/oracle/upgrade/log/data_migration.log

/home/oracle/upgrade/log/post_schema_migration.log

/home/oracle/upgrade/log/pre_schema_migration.log

/home/oracle/upgrade/log/verification.log

/home/oracle/database/log - This directory contains many logs specific to the database migration itself.

4.1

4.1 UI migrate log - This file is created when the migration is started from the UI (user interface) of the ACM application:

/home/oracle/jboss-4.2.2.GA/server/default/deploy/aveksa.ear/aveksa.war/log/create_migrate.log

5.0.x, 5.1.x

/home/oracle/database/log/create.log

/home/oracle/database/log/migrate.log

5.5.x, 6.x

/home/oracle/jboss/server/default/deploy/aveksa.ear/aveksa.war/WEB-INF/database/log/migrate.log

(also note, the migrate will be flagged in the /tmp/aveksa-install.log, if the migration is selected during install)

4.1 UI WebSphere - This file is created when the WebSphere ACM migration is started from the UI of the ACM application. Note that the directory path will vary from system to system, due to the hostname that is part of the directory structure (in this example, its: vm-support-11)

/home/oracle/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/vm-support-11Node01Cell/aveksa.ear/aveksa.war/log/migrate.log

4.1 Command line migrate log - This file is created when the migration is started from migrate.sh command line script: /home/oracle/database/log/createMigrateTool.log

WorkPoint logs:

4.1 WorkPoint-Work Flow logs: These files contain information about the WorkPoint workflow tasks

for jboss:

/home/oracle/jboss/server/default/deploy/aveksa.ear/aveksa.war/log/WorkPoint.log

/home/oracle/jboss/server/default/deploy/aveksa.ear/aveksa.war/log/GeneralMonitor.log

for WebSphere (note that the install home directories may depend on each site, but will be similiar to)

/home/oracle/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/vm-support-11Node01Cell/aveksa.ear/aveksa.war/log/WorkPoint.log

/home/oracle/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/vm-support-11Node01Cell/aveksa.ear/aveksa.war/log/GeneralMonitor.log

for WebLogic (note that the install home directories may depend on each site, but will be similiar to)
/home/oracle/Oracle/Middleware/user_projects/domains/aveksaDomain/servers/AdminServer/tmp/

_WL_user/aveksa/ldedze/aveksa.war/log/GeneralMonitor.log

/home/oracle/Oracle/Middleware/user_projects/domains/aveksaDomain/servers/AdminServer/tmp/

_WL_user/aveksa/ldedze/aveksa.war/log/WorkPoint.log

4.1 WorkPoint-Logging files: These files contain the file name and logging level for the log4j logging:

For Jboss:

/home/oracle/jboss/server/default/deploy/aveksa.ear/GeneralMonitor.properties

/home/oracle/jboss/server/default/deploy/aveksa.ear/workpoint-server.properties

For Websphere:

/home/oracle/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/vm-support-11Node01Cell/aveksa2.ear/GeneralMonitor.properties

/home/oracle/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/vm-support-11Node01Cell/aveksa2.ear/workpoint-server.properties

For Weblogic:

/home/oracle/Oracle/Middleware/user_projects/domains/aveksaDomain/servers/AdminServer/tmp/

_WL_user/aveksa/ldedze/workpoint-server.properties

/home/oracle/Oracle/Middleware/user_projects/domains/aveksaDomain/servers/AdminServer/tmp/

_WL_user/aveksa/ldedze/GeneralMonitor.properties

Various:

ACM 6.0.1, 5.5.7

aveksaServerInfo.log - ACM configuration info in a OS level flat file that can be referenced when the UI Server is not running.

Jboss:

/home/oracle/jboss/server/default/deploy/aveksa.ear/aveksa.war/log/aveksaServerInfo.log

For machines built via internal 'kickstart'

/var/log/postinstall.out for kickstarted machines..

/tmp/aveksa-install.log for 'installed' machines