As an administrator, you can use log files to diagnose problems. This section includes information about various log files that help you troubleshoot CA SOI. You can search the contents of many log files on the SA Manager Debug Console and the UI Server Debug Console.
Helps you troubleshoot reporting import errors. This file is available at SOI_HOME\Reports.
Contains information specific to CA Catalyst transactions. This file is available at SOI_HOME\tomcat\logs.
Tracks the Logic Server installation. Use this file to troubleshoot Logic Server installation problems. This CA Catalyst log file is available at SOI_HOME\log.
Tracks the Registry installation. Use this file to troubleshoot Registry installation problems. This CA Catalyst log file is available at SOI_HOME\log.
Tracks the USM Web View installation. This file is available at SOI_HOME\log.
Includes Event connector-related installation information such as installation errors related to the file copies and configuration settings. This Event connector log file is located in the root of the installation directory.
Tracks the details about CIs with duplicate sheets. If you do not see a CI in CA SOI, check this file to see if it is a duplicate sheet and the limit for duplicates has been reached for that reconciled sheet. This file is available at SOI_HOME\tomcat\logs.
Contains an entry for every UI Server that is connected to the SA Manager and records for each user connection. This file is available at SOI_HOME\tomcat\webapps\sam\console\logs. The Client Log page lets you view the contents of the client.log file. You can also use this page to clear the log and remove old entries.
Traces data that the SA Manager receives from the connectors. The Connector Manager option on the Administration UI debug page controls this log file. This file is available at SOI_HOME\tomcat\logs.
Note: For more information about the improved SA Manager logs reorganization, see the Reorganization of the SA Manager Logs section.
Tracks the CA SOI Domain connector installation. This file is created when you click Done after the CA SOI Domain connector installation finishes. This file is available at SOI_HOME\log.
Contains information about all policy operations (such as parse, normalize, and format) included in your connector policy. You can find the eitransform.log file at SOI_HOME\log after it is enabled.
Includes Event Management information. By default, the log level in the file is set to INFO. This file is available at SOI_HOME\log. Use this file to troubleshoot the Event Management-related errors.
Example: Search on the Universal connector unexpectedly returning no events
This example considers an example search on the Universal connector that unexpectedly returned no events. After configuring a DEBUG log level and running the search again, the following search information is logged in the file:
INFO | jvm 1 | 2011/04/05 10:02:51 | 10:02:51,063 INFO SDOFactory:208 -
com.ca.eventmanager.operations.EventManagerImpl.getEvents: Incoming Map:key=(Connectors) Value=(CA:09997_server01.ca.com@server01.ca.com)
INFO | jvm 1 | 2011/04/05 10:02:51 | 10:02:51,063 INFO SDOFactory:208 - com.ca.eventmanager.operations.EventManagerImpl.getEvents: Incoming Map:key=(MdrProduct) Value=(CA:09997)
INFO | jvm 1 | 2011/04/05 10:02:51 | 10:02:51,063 INFO SDOFactory:208 - com.ca.eventmanager.operations.EventManagerImpl.getEvents: Incoming Map:key=(scope.query.operator) Value=(OR)
INFO | jvm 1 | 2011/04/05 10:02:51 | 10:02:51,063 INFO SDOFactory:208 - com.ca.eventmanager.operations.EventManagerImpl.getEvents: Incoming Map:key=(scope.query.timelast) Value=(1)
...
INFO | jvm 1 | 2011/04/05 10:02:51 | 10:02:51,141 DEBUG XQueryHelper:95 - com.ca.eventmanager.common.XQueryHelper.setTimeLast: timelast=1 qp.timestart=1302008571 qp.timeend=1302012171
INFO | jvm 1 | 2011/04/05 10:02:51 | 10:02:51,141 DEBUG XQueryHelper:96 - com.ca.eventmanager.common.XQueryHelper.setTimeLast: qp.timestart.epoch=Apr 5, 2011 9:02:51 AM qp.timeend.epoch=Apr 5, 2011 10:02:51 AM
INFO | jvm 1 | 2011/04/05 10:02:51 | total reccount=0
INFO | jvm 1 | 2011/04/05 10:02:51 | timescoped files: 0
INFO | jvm 1 | 2011/04/05 10:02:51 | recordscoped files:
INFO | jvm 1 | 2011/04/05 10:02:51 | final-query: let $a := doc('file:/C:/Program%20Files/CA/SOI/resources/Core/EventStore/temp/results27890.xml0.xml')/results/normal return if (count($a)>0) then (<group id='0'>{$a}</group>) else ()
INFO | jvm 1 | 2011/04/05 10:02:51 | resultsfile: C:\Program Files\CA\SOI\resources\Core\EventStore\temp\results27890.xml
...
INFO | jvm 1 | 2011/04/05 10:02:52 | 10:02:52,219 INFO SDOFactory:208 - com.ca.eventmanager.operations.EventManagerImpl.getEvents: Returning from DataSource:SSA key=(Result) Value=(<results scopedeventcount='0' returnedeventcount='0' warning='' error='pattern_not_matched'> set log4j level to TRACE to log entire result set.)
Note: For more information about this example, see the Administration Guide.
Contains status details of the CA SAM Event Management service. This file is available at SOI_HOME\jsw\logs.
Tracks web services transactions that the Universal connector client makes. This file is available at SOI_HOME\log. The SOI_HOME\lib\generic\log4j.xml file controls this log. The default level is ERROR. Set to DEBUG to trace transactions.
Contains connector processing details. This file is available at SOI_HOME\log. By default, the debug level is set to ERROR. The IFW appender in SOI_HOME\resources\log4j.xml controls the log levels. If you set a log level, you do not need to restart the system. In general, the log levels produce this type of information:
When the IFW appender is set to DEBUG, the SOI_HOME\log\debugData folder contains the following types of files:
Includes detailed logging for the CA SAM Store Indexer service. This file is available at SOI_HOME\jsw\logs. The SOI_HOME\indexer\log4j.properties file controls this log.
Includes Event connector-related pre- or post-installation errors such as database creation failure and connector registration problems. This log file is available at EI_HOME\logs.
Includes IFW installation errors. Use this file to troubleshoot the IFW installation issues. This file is available at SOI_HOME\log.
Tracks installation errors that are related to the Mid-tier connector installation. This file is available at SOI_HOME\log.
Tracks the Registry activity. Use this file to troubleshoot the Registry problems. This CA Catalyst log file is available at SOI_HOME\tomcat\logs.
Tracks installation errors that are related to the Sample connector. This file is created when you click Done after the Sample connector installation finishes. The file is available at SOI_HOME\log.
Contains status and general information regarding the Integration Services process and the connectors. This file is available at SOI_HOME\jsw\logs. This log file acts as a primary runtime log file and includes basic runtime informational messages. Anything that is written to stdout is captured in this file. You can check the file to determine the following information:
Example: AMQ connection failure
This example shows the ActiveMQ server connection failure information that is logged in the file:
INFO | jvm 1 | 2009/03/20 09:24:57 | AMQPublisher@server1.ca.com: Trying to establish connection with AMQ.
INFO | jvm 1 | 2009/03/20 09:24:58 | AMQPublisher@server1.ca.com: AMQ Connection failed. User name or password is invalid.
Includes status information and general processing details from the CA SAM Application Server service. This file is available at SOI_HOME\jsw\logs.
Includes status information and general processing details from the CA SAM User Interface Server service. This file is available at SOI_HOME\jsw\logs.
Includes status information and general processing details from the CA SAM Store Indexer service. This file is available at SOI_HOME\\jsw\logs.
Tracks CA SOI and CA Catalyst activity. This file also contains all lifecycle (or heartbeat) messages information.
The file soimgr.log at SOI_HOME\tomcat\logs contains SA Manager-specific information. The file soiuis.log that is available at SOI_HOME\SamUI\logs contains UI Server-specific information.
Note: For more information about the SA Manager logs reorganization, see the Reorganization of the SA Manager Logs section.
Tracks all debug messages. The soimgr-debug.log file that is available at SOI_HOME\tomcat\logs contains SA Manager-specific information. The file soiuis-debug.log at SOI_HOME\SamUI\logs contains UI Server-specific information.
Note: For more information about the SA Manager logs reorganization, see the Reorganization of the SA Manager Logs section.
Includes a consolidated error log that contains errors from several product components. This file is available at SOI_HOME\tomcat\logs. When you encounter a problem with the product, reference this log file first. The file is accessible from the Operations Console Connection Status dialog and the Connector Configuration page of the Administration UI.
Includes CA SOI installation error information. This file is available at SOI_HOME\log.
Includes information about whether USM schema validation failures have occurred. This file is available at SOI_HOME\log.
Tracks the Mobile Dashboard information. This file is available at SOI_HOME\SAMUI\logs.
Includes information that is associated with CA Catalyst USM Web View. This file is available at SOI_HOME\SamUI\logs.
Tracks the Service Discovery processing. This file is available at SOI_HOME\log. The SD appender in the SOI_HOME\resources\log4j.xml file controls this log.
Tracks the installation of Service Discovery. This file is available at SOI_HOME\log.
Includes the Reconciler activity. This CA Catalyst log file is available at SOI_HOME\tomcat\logs.
Tracks the UCF Broker activity. Use this file to troubleshoot synchronization problems that are not occurring in the Logic Server. This CA Catalyst log file is available at SOI_HOME\log.
Includes information about general UCF Broker status and processing. This file is available at SOI_HOME\jsw\logs.
|
Copyright © 2013 CA.
All rights reserved.
|
|