IBM Support

Collecting Data: ITCAM for J2EE

Question & Answer


Question

How do I collect the J2EE DC and TEMA logs?

Answer


1. Please Collect "yj" and/or "ht" version from TEMS, TEPS, TEMA, and send the output.

Commandon Windows : <ITM_HOME>\bin\kincinfo -i
on UNIX/Linux : <ITM_HOME>/bin/cinfo -i

2. Collect MS, DC, TEMA data using following instruction and send the ouptut.



Note : Since the J2EE agent is composed by two parts, Data Collector and TEMA, you can separately collect data from them by invoking the two following scripts as "root":

=====>Data Collector (DC)
LocationWindows: <ITM_HOME>\TMAITM6\j2eedc\7.1.1.0.0\itcamdc\bin\cyn_collector.cmd
Unix : <ITM_HOME>/<architecture>/yj/j2eedc/7.1.1.0.0/itcamdc/bin/cyn_collector.sh

* example:
- Windows platform :
C:\IBM\ITM\TMAITM6\j2eedc\7.1.1.0.0\itcamdc\bin\cyn_collector.cmd
- Linux 64 bit platform :
opt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/itcamdc/bin/cyn_collector.sh
Usage/
Output		Windows : %TEMP%\CYN\*.zip
Unix : <ITM_HOME>/tmp/CYN/<hostname>-CYNenv.jar
=====>TEMA
LocationWindows : <ITM_HOME>\TMAITM6\kyjcollect.cmd
Unix : <ITM_HOME>/<architecture>/yj/bin/kyjcollect.sh

* example:
- Windows platform : C:\IBM\ITM\TMAITM6\kyjcollect.cmd
- Linux 64 bit platform : opt/IBM/ITM/lx8266/yj/bin/kyjcollect.sh
Usage/
Output		Windows : %TEMP%\kyj\*.jar
Unix : $HOME/tmp/kyj/kyjcollect-$HOSTNAME.tar.gz

* example:
- Linux : /root/tmp/kyj/kyjcollect-<hostname>.tar.gz
- AIX, Solaris, HPUX : /tmp/kyj/kyjcollect-<hostname>.tar.gz



=============>Managing Server (MS)
Locationon Window/Unix/Linux : <MS_HOME>/bin/MS_Gather_Data.sh

Note: On Windows, the user must run the script in a Korn Shell environment.
Usage/
Output		on Windows/Unix/Linux :
<MS_HOME>/bin/MS_Gather_Data.sh [pmr][was_home][appServer]

Note: [was_home] = directory where the MS Visualization Engine is installed

=============>Data Collector (DC)
Locationon Windows : <DC_HOME>\itcamdc\bin\cyn_collector_j2.cmd
on Unix/Linux : <DC_HOME>/itcamdc/bin/cyn_collector_J2.sh
Outputon Windows : <DC_HOME>\collect.jar
on Unix/Linux : <DC_HOME>/collect.tar.gz
=============>TEMA
Locationon Windows : <ITM_HOME>\TMAITM6\kyjcollect.cmd
on Unix/Linux : <ITM_HOME>/<arch>/yj/bin/kyjcollect.sh
where <arch>= location that indicates the platforms
(ex: sol283 for Solaris, aix513 for AIX, and hp11 for HP-UX).
Usageon Windows : <ITM_HOME>\TMAITM6\kyjcollect.cmd
on Unix/Linux : <ITM_HOME>/<arch>/yj/bin/kyjcollect.sh
Outputon Windows : %TEMP%\kyj\*.jar
on Unix/Linux : $HOME/tmp/kyj/kyjcollect-<hostname>.tar.gz



Back to top



* Window and Unix
Location <MS_HOME>/logs/am_stderr.log
<MS_HOME>/logs/am_stdout.log
<TIVOLI_LOGS>/msg-<component>.log
<TIVOLI_LOGS>/trace-<component>.log
<TIVOLI_LOGS>/audit-ms.log



* Windows and Unix

For the version lower than ITCAM for J2EE 6.1 FixPack 4
Here are the logs required for each application server. The logs are from the following directory: <TIVOLI_LOGS>/nodename.instancename

Application Server
Logs to Collect
WebLogic, WASCE, J2SEmsg-dc.log, trace-dc.log, msg-dc-native.log, trace-dc-native.log
NetWeavermsg-dc-sap.log, trace-dc-sap.log, msg-dc-native.log, trace-dc-native.log
Tomcatmsg-dc-Standard.log, trace-dc-Standard.log, msg-dc-native.log, trace-dc-native.log
Oraclemsg-dc.log, trace-dc.log, trace-dc-bcm.log, msg-dc-native.log, trace-dc-native.log
JBossmsg-dc-Unified.log, trace-dc-Unified.log, trace-dc-bcm.log, msg-dc-native.log, trace-dc-native.log


For the version ITCAM for J2EE 6.1 FixPack 4 or higher
Here are the logs required for each application server. The logs are from the following directory: <TIVOLI_LOGS>/nodename.instancename

Application Server
Logs to Collect
WebLogicmsg-dc-ParentLast.log, trace-dc-ParentLast.log, msg-dc-native.log, trace-dc-native.log, msg-dc-bcm.log, trace-dc-bcm.log
WASCE, J2SEmsg-dc.log, trace-dc.log, msg-dc-native.log, trace-dc-native.log, msg-dc-bcm.log, trace-dc-bcm.log
NetWeavermsg-dc-sap.log, trace-dc-sap.log, msg-dc-native.log, trace-dc-native.log ,msg-dc-bcm.log, trace-dc-bcm.log
Tomcatmsg-dc-tomcat.log, trace-dc-tomcat.log, msg-dc-native.log, trace-dc-native.log, msg-dc-bcm.log, trace-dc-bcm.log
Oraclemsg-dc.log, trace-dc.log, trace-dc-bcm.log, msg-dc-native.log, trace-dc-native.log, msg-dc-bcm.log, trace-dc-bcm.log
JBossmsg-dc-jboss.log, trace-dc-jboss.log, msg-dc-native.log, trace-dc-native.log, msg-dc-bcm.log, trace-dc-bcm.log



* Windows
Location <ITM_HOME>/logs/kyj-tema-trace.log,
<ITM_HOME>/logs/kyj-tema-msg.log,
<ITM_HOME>/logs/KYJ.Primary.*.*JVM.log

* Unix
Location <ITM_HOME>/<PLATFORM>/logs/kyj-tema-trace.log,
<ITM_HOME>/<PLATFORM>/logs/kyj-tema-msg.log,
<ITM_HOME>/logs/KYJ.Primary.*.*JVM.log


Back to top




Managing Server Installation Error Logs (for all version)

Components
Logs to Collect
Managing Server specific logs* Windows : C:\Program Files\ibm\tivoli\common\CYN\logs
* Unix : /var/ibm/tivoli/common/CYN/logs
Embedded DB2 logs* Windows : <user's My Documents directory>\DB2LOG
* Unix : /tmp/db2setup.*
Embedded WebSphere Application Server** Windows and Unix :
<MS_HOME>/temp
<J2EEAPP_HOME>/logs
Embedded WebSphere Application Server Refresh Pack** Windows and Unix :
<J2EEAPP_HOME>/logs/update




* Window and Unix
Location <TIVOLI_LOGS>/trace-install.log
<TIVOLI_LOGS>/launchContainer/
<TIVOLI_LOGS>/platformUtils/
If you use NetWeaver, <TIVOLI_LOGS>/config.log

Back to top

[{"Product":{"code":"SSCH4B","label":"Tivoli Composite Application Manager for J2EE"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"ITCAM J2EE BASE","Platform":[{"code":"PF027","label":"Solaris"},{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"6.1;7.1.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

ITCAM for J2EE

Document Information

Modified date:
17 June 2018

UID

swg21321514

Page Feedback