|
|
|
CA Service Catalog includes several log4j.xml files that control the output of the most frequently used log files. Each log4j.xml file controls the log file of one or more CA Service Catalog services, as summarized in the following table:
|
Service Logged |
Location of Log4j File |
Log Files Controlled |
Log file Location |
|---|---|---|---|
|
Service View |
%USM_HOME%\view\conf |
seeddata.log |
%USM_HOME%\logs\install |
|
CA Service Fulfillment |
%USM_HOME%\fulfillment\conf |
tomcat_fulfillment.log |
%USM_HOME%\logs\fulfillment |
|
CA Service Accounting |
%USM_HOME%\accounting\conf |
accounting.log |
%USM_HOME%\logs\accounting |
|
Repository Agent |
%USM_HOME%\repagent\config |
repagent.log |
%USM_HOME%\repagent\log |
|
ixutil import\export utility |
%USM_HOME%\scripts |
ixutil.log |
%USM_HOME%\logs\install |
Logging messages generated by CA Service Catalog components, such as the Event Manager and the Rule Engine, are written to the log file of the calling service. For example, if the Service View service calls the Event Manager, the log for the call is written in the view.log file. Similarly, calls from the CA Service Accounting service to the Event Manager are written to the accounting.log file.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |