jplumey 's List: IBM

IBM DB2 Content Management Information Center 2

Nov 19, 10

publib.boulder.ibm.com/...index.jsp ibm content manager ecm
- Logging and tracing for DB2 Content Manager
 
 You can enable different levels of logging. You can also enable a trace on various components of the content management system.
 
 You can enable the logging and tracing for the following components or services of IBM® DB2® Content Manager Enterprise Edition,DB2 Content Manager for z/OS®, and DB2 Information Integrator for Content:
 Installation
 
 Library server
 
 Resource manager
 
 System administration client
 
 Client for Windows®
 
 eClient
 
 LDAP
 
 Java™ and C++ APIs
 
 HTTP server requests
 
 You can configure logging and tracing for many of these components by using the common log control utility from the system administration client.
 
 Specifying log settings for DB2 Content Manager components
 You can configure logging and tracing for many of the components by using the common log control utility from the system administration client.
 
 Enabling tracing in DB2 Content Manager
 You can enable tracing using the system administration client.
 
 Enabling tracing in DB2 Content Manager for z/OS
 
 Enabling the DSNTRACE resource manager DB2 trace facility
 
 Enabling the HTTP Server trace facility
 
 Event logging
 DB2 Content Manager can log system administration and item events for audit purposes. Logging is optional.
- <h1 tabindex="6" id="vcc_sp_h1_31" class="topictitle1">Log file locations</h1> <div tabindex="7" id="vcc_sp_div_32">By default, the installation log files are in the <var id="vcc_sp_var_34" class="varname">IBMCMROOT</var>/log/<var id="vcc_sp_var_35" class="varname">PRODUCT</var> directory. <div tabindex="9" id="vcc_sp_div_36" class="section">This section contains information about the logs for the various components of an installed and configured content management system. <div tabindex="11" id="vcc_sp_div_38" class="p"><div tabindex="12" id="vcc_sp_div_39" class="tablenoborder"><table summary="" cellpadding="4" frame="hsides" tabindex="13" border="1" rules="rows" cellspacing="0" id="vcc_sp_table_40"><caption id="vcc_sp_caption_41">Table 1. Log locations in <var id="vcc_sp_var_42" class="varname">IBMCMROOT</var>\log</caption><thead align="left" id="vcc_sp_thead_43"><tr id="vcc_sp_tr_44"><th tabindex="14" valign="top" width="22.962962962962962%" id="d23240e40" class="nocellborder">Product</th> <th tabindex="15" valign="top" width="25.185185185185183%" id="d23240e42" class="nocellborder">Install log</th> <th tabindex="16" valign="top" width="25.185185185185183%" id="d23240e44">Configuration log</th> <th tabindex="17" valign="top" width="26.666666666666668%" id="d23240e46">Uninstall log</th> </tr> </thead> <tbody id="vcc_sp_tbody_45"><tr id="vcc_sp_tr_46"><td tabindex="18" valign="top" headers="d23240e40 " width="22.962962962962962%" id="vcc_sp_td_47" class="nocellborder">DB2® Content Manager</td> <td tabindex="20" valign="top" headers="d23240e42 " width="25.185185185185183%" id="vcc_sp_td_49" class="nocellborder">cminstall.log </td> <td tabindex="22" valign="top" headers="d23240e44 " width="25.185185185185183%" id="vcc_sp_td_51">cmconfig.log</td> <td tabindex="24" valign="top" headers="d23240e46 " width="26.666666666666668%" id="vcc_sp_td_53">cmuninstall.log</td> </tr> <tr id="vcc_sp_tr_55"><td tabindex="26" valign="top" headers="d23240e40 " width="22.962962962962962%" id="vcc_sp_td_56" class="nocellborder">DB2 Information Integrator for Content </td> <td tabindex="28" valign="top" headers="d23240e42 " width="25.185185185185183%" id="vcc_sp_td_58" class="nocellborder">ii4cinstall.log </td> <td tabindex="30" valign="top" headers="d23240e44 " width="25.185185185185183%" id="vcc_sp_td_60">ii4cconfig.log </td> <td tabindex="32" valign="top" headers="d23240e46 " width="26.666666666666668%" id="vcc_sp_td_62">ii4cuninstall.log</td> </tr> <tr id="vcc_sp_tr_64"><td tabindex="34" valign="top" headers="d23240e40 " width="22.962962962962962%" id="vcc_sp_td_65" class="nocellborder">eClient</td> <td tabindex="35" valign="top" headers="d23240e42 " width="25.185185185185183%" id="vcc_sp_td_66" class="nocellborder">ecinstall.log </td> <td tabindex="37" valign="top" headers="d23240e44 " width="25.185185185185183%" id="vcc_sp_td_68">ecconfig.log </td> <td tabindex="39" valign="top" headers="d23240e46 " width="26.666666666666668%" id="vcc_sp_td_70">ecuninstall.log</td> </tr> <tr id="vcc_sp_tr_72"><td tabindex="41" valign="top" headers="d23240e40 " width="22.962962962962962%" id="vcc_sp_td_73" class="nocellborder">VideoCharger™</td> <td tabindex="42" valign="top" headers="d23240e42 " width="25.185185185185183%" id="vcc_sp_td_74" class="nocellborder">vcinstall.log </td> <td tabindex="44" valign="top" headers="d23240e44 " width="25.185185185185183%" id="vcc_sp_td_76">n/a</td> <td tabindex="45" valign="top" headers="d23240e46 " width="26.666666666666668%" id="vcc_sp_td_77">vcuninstall.log</td> </tr> </tbody> </table> </div> </div> </div> <div tabindex="47" id="vcc_sp_div_79" class="section"><h2 tabindex="48" id="vcc_sp_h2_80" class="sectiontitle">Client for windows log files</h2>Log files from the Client for Windows® are kept on the individual client for Windows systems. The location is a user preference, so it might vary from one system to another. <div tabindex="50" id="vcc_sp_div_82" class="p"><ol tabindex="51" id="vcc_sp_ol_83"><li tabindex="52" id="vcc_sp_li_84">Connect the Client for Windows to the library server.</li> <li tabindex="53" id="vcc_sp_li_85">Select Options > Preferences.</li> <li tabindex="57" id="vcc_sp_li_89">Select General. The Log File Directory identifies the location of the client for Windows logs:<ul tabindex="60" id="vcc_sp_ul_92"><li tabindex="61" id="vcc_sp_li_93">ICMClient.log</li> <li tabindex="63" id="vcc_sp_li_95">ICMClient.err</li> <li tabindex="65" id="vcc_sp_li_97">ICMClientLog.ini</li> </ul> </li> </ol> </div> </div> <div tabindex="67" id="vcc_sp_div_99" class="section"><h2 tabindex="68" id="vcc_sp_h2_100" class="sectiontitle">System administration client logging</h2>The system administration client logs error-level information to the cmadmerr.log file, which is located in the system administration client directory. You can change the default parameters of the cmadmin.log file by using the common log control utility in the system administration client. The DB2 Information Integrator for Content component of the system administration client logs error information to the dklog.log file.</div></div>

1 - 1 of 1

20 items/page

List Comments (0)

List Info

jplumey

1 items | 2 visits

Updated on Nov 19, 10
Created on Nov 19, 10

Category: Computers & Internet

URL:

jplumey 's List: IBM

IBM DB2 Content Management Information Center 2

Logging and tracing for DB2 Content Manager

List Info