Edit C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\odbc\7.0.1\help\troubleshooting\diagnostic.3.5.html
<?xml version="1.0" encoding="utf-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xml:lang="en" lang="en" xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8" /> <meta http-equiv="Content-Style-Type" content="text/css" /> <!-- MOTW-DISABLED saved from url=(0014)about:internet --> <title>Logging (Salesforce Driver)</title> <link rel="StyleSheet" href="css/diagnostic.css" type="text/css" media="all" /> <link rel="StyleSheet" href="css/webworks.css" type="text/css" media="all" /> <script type="text/javascript" language="JavaScript1.2" src="wwhdata/common/context.js"></script> <script type="text/javascript" language="JavaScript1.2" src="wwhdata/common/towwhdir.js"></script> <script type="text/javascript" language="JavaScript1.2" src="wwhdata/common/wwhpagef.js"></script> <script type="text/javascript" language="JavaScript1.2"> <!-- var WebWorksRootPath = ""; // --> </script> <script type="text/javascript" language="JavaScript1.2"> <!-- // Set reference to top level help frame // var WWHFrame = WWHGetWWHFrame("", true); // --> </script> <script type="text/javascript" language="JavaScript1.2" src="scripts/expand.js"></script> </head> <body class="" style="background-color: #FFFFEE;" onload="WWHUpdate();" onunload="WWHUnload();" onkeydown="WWHHandleKeyDown((document.all||document.getElementById||document.layers)?event:null);" onkeypress="WWHHandleKeyPress((document.all||document.getElementById||document.layers)?event:null);" onkeyup="WWHHandleKeyUp((document.all||document.getElementById||document.layers)?event:null);"> <br /> <div class="WebWorks_Breadcrumbs" style="text-align: left;"> <a class="WebWorks_Breadcrumb_Link" href="diagnostic.3.1.html#111095">1 Diagnostic Tools</a> : Logging (Salesforce Driver)</div> <hr align="left" /> <blockquote> <div class="head_1"><a name="111095">Logging (Salesforce Driver)</a></div> <div class="Body"><a name="111096">The Salesforce driver provides a flexible and comprehensive logging mechanism of its Java </a>components that allows logging to be incorporated seamlessly with the logging of your application or enabled and configured independently from the application. The logging mechanism can be instrumental in investigating and diagnosing issues. It also provides valuable insight into the type and number of operations requested by the application from the driver and requested by the driver from the remote data source. This information can help you tune and optimize your application.</div> <div class="head_2"><a name="112716">Logging Components</a></div> <div class="Body"><a name="117206">The Salesforce driver uses the Java Logging API to configure and control the loggers </a>(individual logging components) used by the driver. The Java Logging API is built into the JVM.</div> <div class="Body"><a name="120526">The Java Logging API allows applications or components to define one or more named </a>loggers. Messages written to the loggers can be given different levels of importance. For example, errors that occur in the driver can be written to a logger at the ERROR level, while progress or flow information can be written to a logger at the INFO or FINER level. Each logger used by the driver can be configured independently. The configuration for a logger includes what level of log messages are written, the location to which they are written, and the format of the log message. </div> <div class="Body"><a name="120527">The Java Logging API defines the following levels:</a></div> <div class="list_bulleted_outer" style="margin-left: 0pt;"> <table border="0" cellspacing="0" cellpadding="0" summary=""> <tr style="vertical-align: baseline;"> <td> <div class="list_bulleted_inner" style="width: 18pt; white-space: nowrap;">â? </div> </td> <td width="100%"> <div class="list_bulleted_inner"><a name="120528">SEVERE</a></div> </td> </tr> </table> </div> <div class="list_bulleted_single_outer" style="margin-left: 0pt;"> <table border="0" cellspacing="0" cellpadding="0" summary=""> <tr style="vertical-align: baseline;"> <td> <div class="list_bulleted_single_inner" style="width: 18pt; white-space: nowrap;">â? </div> </td> <td width="100%"> <div class="list_bulleted_single_inner"><a name="120529">CONFIG</a></div> </td> </tr> </table> </div> <div class="list_bulleted_single_outer" style="margin-left: 0pt;"> <table border="0" cellspacing="0" cellpadding="0" summary=""> <tr style="vertical-align: baseline;"> <td> <div class="list_bulleted_single_inner" style="width: 18pt; white-space: nowrap;">â? </div> </td> <td width="100%"> <div class="list_bulleted_single_inner"><a name="120530">FINE</a></div> </td> </tr> </table> </div> <div class="list_bulleted_single_outer" style="margin-left: 0pt;"> <table border="0" cellspacing="0" cellpadding="0" summary=""> <tr style="vertical-align: baseline;"> <td> <div class="list_bulleted_single_inner" style="width: 18pt; white-space: nowrap;">â? </div> </td> <td width="100%"> <div class="list_bulleted_single_inner"><a name="120531">FINER</a></div> </td> </tr> </table> </div> <div class="list_bulleted_single_outer" style="margin-left: 0pt;"> <table border="0" cellspacing="0" cellpadding="0" summary=""> <tr style="vertical-align: baseline;"> <td> <div class="list_bulleted_single_inner" style="width: 18pt; white-space: nowrap;">â? </div> </td> <td width="100%"> <div class="list_bulleted_single_inner"><a name="120532">FINEST</a></div> </td> </tr> </table> </div> <div class="Body"><a name="117256">NOTE: Log messages logged by the driver only use the CONFIG, FINE, FINER, and </a>FINEST logging levels.</div> <div class="Body"><a name="117257">Setting the log threshold of a logger to a particular level causes the logger to write log </a>messages of that level and higher to the log. For example, if the threshold is set to <span class="Syntax">FINE</span>, the logger writes messages of levels FINE. CONFIG, and SEVERE to its log. Messages of level FINER or FINEST are not written to the log.</div> <div class="Body"><a name="117248">The driver exposes loggers for the following functional areas:</a></div> <div class="list_bulleted_outer" style="margin-left: 0pt;"> <table border="0" cellspacing="0" cellpadding="0" summary=""> <tr style="vertical-align: baseline;"> <td> <div class="list_bulleted_inner" style="width: 18pt; white-space: nowrap;">â? </div> </td> <td width="100%"> <div class="list_bulleted_inner"><a name="112727">Driver to SQL Communication</a></div> </td> </tr> </table> </div> <div class="list_bulleted_single_outer" style="margin-left: 0pt;"> <table border="0" cellspacing="0" cellpadding="0" summary=""> <tr style="vertical-align: baseline;"> <td> <div class="list_bulleted_single_inner" style="width: 18pt; white-space: nowrap;">â? </div> </td> <td width="100%"> <div class="list_bulleted_single_inner"><a name="112728">SQL Engine</a></div> </td> </tr> </table> </div> <div class="list_bulleted_single_outer" style="margin-left: 0pt;"> <table border="0" cellspacing="0" cellpadding="0" summary=""> <tr style="vertical-align: baseline;"> <td> <div class="list_bulleted_single_inner" style="width: 18pt; white-space: nowrap;">â? </div> </td> <td width="100%"> <div class="list_bulleted_single_inner"><a name="112730">Web service adapter</a></div> </td> </tr> </table> </div> <div class="head_3"><a name="119183">Driver to SQL Communication Logger</a></div> <div class="gutter_text_right"><a name="120548">Name</a></div> <div class="Body"><a name="120549">com.ddtek.cloud.drivercommunication</a></div> <div class="gutter_text_right"><a name="120550">Description</a></div> <div class="Body"><a name="120551">Logs all calls made by the driver to the SQL Engine and the responses from the SQL </a>Engine back to the driver.</div> <div class="gutter_text_right"><a name="120552">Message Levels </a></div> <div class="Body"><a name="120553">CONFIG - Errors and Warnings encountered by the communication protocol are logged at </a>this level.</div> <div class="Body"><a name="120554">FINER - The message type and arguments for requests and responses sent between the </a>driver and SQL Engine are logged at this level. Data transferred between the driver and SQL Engine is not logged.</div> <div class="Body"><a name="120555">FINEST - Data transferred between the driver and SQL Engine is logged at this level.</a></div> <div class="gutter_text_right"><a name="120556">Default</a></div> <div class="Body"><a name="120557">OFF</a></div> <div class="head_3"><a name="119212">SQL Engine Logger</a></div> <div class="gutter_text_right"><a name="117997">Name</a></div> <div class="Body"><a name="117998">com.ddtek.cloud.sql.level</a></div> <div class="gutter_text_right"><a name="117999">Description</a></div> <div class="Body"><a name="118000">Logs the operations that the SQL engine performs while executing a query. Operations </a>include preparing a statement to be executed, executing the statement, and fetching the data, if needed. These are internal operations that do not necessarily directly correlate with Web service calls made to the remote data source.</div> <div class="gutter_text_right"><a name="118001">Message Levels </a></div> <div class="Body"><span class="Syntax"><a name="118002">CONFIG</a></span> - Any errors or warnings detected by the SQL engine are written at this level.</div> <div class="Body"><span class="Syntax"><a name="118003">FINE</a></span> - In addition to the same information logged by the CONFIG level, SQL engine operations are logged at this level. In particular, the SQL statement that is being executed is written at this level.</div> <div class="Body"><span class="Syntax"><a name="118004">FINER</a></span> - In addition to the same information logged by the CONFIG and FINE levels, data sent or received in the process of performing an operation is written at this level.</div> <div class="head_3"><a name="117391">Web Service Adapter Logger</a></div> <div class="gutter_text_right"><a name="120536">Name</a></div> <div class="Body"><a name="120537">com.ddtek.cloud.adapter.level</a></div> <div class="gutter_text_right"><a name="120538">Description</a></div> <div class="Body"><a name="120539">Logs the Web service calls the driver makes to the remote data source and the responses it </a>receives from the remote data source.</div> <div class="gutter_text_right"><a name="120540">Message Levels </a></div> <div class="Body"><span class="Syntax"><a name="120541">CONFIG</a></span> - Any errors or warnings detected by the Web service adapter are written at this level.</div> <div class="Body"><span class="Syntax"><a name="120542">FINE</a></span> - In addition to the information logged by the CONFIG level, information about Web service calls made by the Web service adapter and responses received by the Web service adapter are written at this level. In particular, the Web service calls made to execute the query and the calls to fetch or send the data are logged. The log entries for the calls to execute the query include the Salesforce-specific query being executed. The actual data sent or fetched is not written at this level.</div> <div class="Body"><span class="Syntax"><a name="120543">FINER</a></span> - In addition to the information logged by the CONFIG and FINE levels, this level provides additional information.</div> <div class="Body"><span class="Syntax"><a name="120544">FINEST</a></span> - In addition to the information logged by the CONFIG, FINE, and FINER levels, data associated with the Web service calls made by the Web service adapter is written.</div> <div class="gutter_text_right"><a name="119986"> </a></div> <div class="head_2"><a name="117583">Configuring Logging</a></div> <div class="Body"><a name="117585">You can configure logging using a standard Java properties file in either of the following </a>ways:</div> <div class="list_bulleted_outer" style="margin-left: 0pt;"> <table border="0" cellspacing="0" cellpadding="0" summary=""> <tr style="vertical-align: baseline;"> <td> <div class="list_bulleted_inner" style="width: 18pt; white-space: nowrap;">â? </div> </td> <td width="100%"> <div class="list_bulleted_inner"><a name="117588">Using the properties file that is shipped with your JVM. See </a><span class="Cross_ref_"><a href="javascript:WWHClickedPopup('troubleshooting', 'diagnostic.3.5.html#117595', '');">â??Using the JVMâ??</a></span> for details.</div> </td> </tr> </table> </div> <div class="list_bulleted_outer" style="margin-left: 0pt;"> <table border="0" cellspacing="0" cellpadding="0" summary=""> <tr style="vertical-align: baseline;"> <td> <div class="list_bulleted_inner" style="width: 18pt; white-space: nowrap;">â? </div> </td> <td width="100%"> <div class="list_bulleted_inner"><a name="117593">Using the driver. See </a><span class="Cross_ref_"><a href="javascript:WWHClickedPopup('troubleshooting', 'diagnostic.3.5.html#117602', '');">â??Using the Driverâ??</a></span> for details.</div> </td> </tr> </table> </div> <div class="head_3"><a name="117595">Using the JVM</a></div> <div class="Body"><a name="117597">If you want to configure logging using the properties file that is shipped with your JVM, use a </a>text editor to modify the properties file in your JVM. Typically, this file is named logging.properties and is located in the JRE/lib subdirectory of your JVM. The JRE looks for this file when it is loading.</div> <div class="Body"><a name="117598">You can also specify which properties file to use by setting the java.util.logging.config.file </a>system property. At a command prompt, enter:</div> <div class="syntax_first"><a name="117599">java -Djava.util.logging.config.file=</a><span class="EquationVariables">properties_file</span></div> <div class="Body"><a name="117600">where </a><span class="EquationVariables">properties_file</span> is the name of the properties file you want to load.</div> <div class="head_3"><a name="117602">Using the Driver</a></div> <div class="Body"><a name="117603">If you want to configure logging using the driver, you can use either of the following </a>approaches:</div> <div class="list_bulleted_outer" style="margin-left: 0pt;"> <table border="0" cellspacing="0" cellpadding="0" summary=""> <tr style="vertical-align: baseline;"> <td> <div class="list_bulleted_inner" style="width: 18pt; white-space: nowrap;">â? </div> </td> <td width="100%"> <div class="list_bulleted_inner"><a name="117604">Use a single properties file for all Salesforce connections.</a></div> </td> </tr> </table> </div> <div class="list_bulleted_outer" style="margin-left: 0pt;"> <table border="0" cellspacing="0" cellpadding="0" summary=""> <tr style="vertical-align: baseline;"> <td> <div class="list_bulleted_inner" style="width: 18pt; white-space: nowrap;">â? </div> </td> <td width="100%"> <div class="list_bulleted_inner"><a name="117605">Use a different properties file for each embedded database. For example, if you have </a>two embedded databases (johnsmith.xxx and pattijohnson.xxx, for example), you can load one properties file for the johnsmith.xxx database and load another properties file for the pattijohnson.xxx database.</div> </td> </tr> </table> </div> <div class="Body"><a name="118077">NOTE: By default, the name of the embedded database is the user ID specified for the </a>connection. You can specify the name of the embedded database using the DatabaseName property. Refer to <span class="Cross_ref_"><a href="javascript:WWHClickedPopup('ODBC', 'salesforce.27.04.html#917084', '');">â??Connection Option Descriptionsâ??</a></span> in <span class="Cross_ref_"><a href="javascript:WWHClickedPopup('ODBC', 'salesforce.27.01.html#1222348', '');">Chapter 21</a></span> of the <span class="Emphasis">DataDirect </span><span class="Emphasis">Connect Series for ODBC Userâ??s Guide</span> for details on using LogConfigFile and other connection options.</div> <div class="Body"><a name="117611">By default, the driver looks for the file named ddlogging.properties in the current working </a>directory to load for all Salesforce connections. If the SQLEngineMode connection option is set to Server, the driver uses the ddlogging.properties file that is specified by the Server DB Directory connection option.</div> <div class="Body"><a name="117612">If a properties file is specified for the LogConfigFile connection option, the driver uses the </a>following process to determine which file to load:</div> <div class="list_procedure_first_outer" style="margin-left: 0pt;"> <table border="0" cellspacing="0" cellpadding="0" summary=""> <tr style="vertical-align: baseline;"> <td> <div class="list_procedure_first_inner" style="width: 18pt; white-space: nowrap;"> <span class="Numbers">1 </span> </div> </td> <td width="100%"> <div class="list_procedure_first_inner"><a name="117614">The driver looks for the file specified by the LogConfigFile connection option.</a></div> </td> </tr> </table> </div> <div class="list_procedure_outer" style="margin-left: 0pt;"> <table border="0" cellspacing="0" cellpadding="0" summary=""> <tr style="vertical-align: baseline;"> <td> <div class="list_procedure_inner" style="width: 18pt; white-space: nowrap;"> <span class="Numbers">2 </span> </div> </td> <td width="100%"> <div class="list_procedure_inner"><a name="117619">If the driver cannot find the file in </a><span class="Cross_ref_"><a href="javascript:WWHClickedPopup('troubleshooting', 'diagnostic.3.5.html#117614', '');">Step 1</a></span>, it looks for a properties file named <span class="Syntax">database_name</span>.logging.properties in the directory containing the embedded database for the connection, where <span class="EquationVariables">database_name</span> is the name of the embedded database.</div> </td> </tr> </table> </div> <div class="list_procedure_outer" style="margin-left: 0pt;"> <table border="0" cellspacing="0" cellpadding="0" summary=""> <tr style="vertical-align: baseline;"> <td> <div class="list_procedure_inner" style="width: 18pt; white-space: nowrap;"> <span class="Numbers">3 </span> </div> </td> <td width="100%"> <div class="list_procedure_inner"><a name="117624">If the driver cannot find the file in </a><span class="Cross_ref_"><a href="javascript:WWHClickedPopup('troubleshooting', 'diagnostic.3.5.html#117619', '');">Step 2</a></span>, it looks for a properties file named ddlogging.properties in the current working directory.</div> </td> </tr> </table> </div> <div class="list_procedure_outer" style="margin-left: 0pt;"> <table border="0" cellspacing="0" cellpadding="0" summary=""> <tr style="vertical-align: baseline;"> <td> <div class="list_procedure_inner" style="width: 18pt; white-space: nowrap;"> <span class="Numbers">4 </span> </div> </td> <td width="100%"> <div class="list_procedure_inner"><a name="117628">If the driver cannot find the file in </a><span class="Cross_ref_"><a href="javascript:WWHClickedPopup('troubleshooting', 'diagnostic.3.5.html#117624', '');">Step 3</a></span>, it abandons its attempt to load a properties file.</div> </td> </tr> </table> </div> <div class="Body"><a name="117629">If any of these files exist, but the logging initialization fails for some reason while using that </a>file, the driver writes a warning to the standard output (System.out), specifying the name of the properties file being used.</div> <div class="Body"><a name="120160">A sample properties filenamed ddlogging.properties is installed in the </a><span class="EquationVariables">install_dir</span>\<span class="EquationVariables">samples</span> subdirectory of your product installation directory, where <span class="EquationVariables">install_dir</span> is your product installation directory. For example, you can find the ddlogging.properties file in <span class="EquationVariables">install_dir</span>\Samples\Bulkstrm, <span class="EquationVariables">install_dir</span>\Samples\Bulk, and <span class="EquationVariables">install_dir</span>\Samples\Example. You can copy this file to the current working directory of your application or embedded database directory, and modify it using a text editor for your needs.</div> <script type="text/javascript" language="JavaScript1.2"> <!-- // Clear related topics // WWHClearRelatedTopics(); document.writeln(WWHRelatedTopicsInlineHTML()); // --> </script> </blockquote> <script type="text/javascript" language="JavaScript1.2"> <!-- document.write(WWHRelatedTopicsDivTag() + WWHPopupDivTag() + WWHALinksDivTag()); // --> </script> </body> </html>
Ms-Dos/Windows
Unix
Write backup
jsp File Browser version 1.2 by
www.vonloesch.de