SSIM service and servlet debug logging switches

Article:TECH85647  |  Created: 2007-01-08  |  Updated: 2011-07-26  |  Article URL http://www.symantec.com/docs/TECH85647
Article Type
Technical Solution


Issue



How to turn on debug logging for different services and servlets on SSIM 4.5.

 


Solution



Debug logging can put a significant load on the SSIM environment and may have a significant impact on SSIM performance. We recommend turning debug logging off as soon as the log information has been created.

 

Service Name
SSIM 4.5 Log File location
SSIM 4.6 Log File location
Log 4j File location
sesmanager /opt/Symantec/sesa/logs/manager.log /opt/Symantec/sesa/servletengine/webapps/sesa/WEB-INF/classes/log4j.properties
sesevents /opt/Symantec/sesa/logs/eventservice.log /opt/Symantec/sesa/eventservice/webapps/sesa/WEB-INF/classes/log4j.properties
rxregistry /opt/Symantec/simserver/rxregistry/rxregistry.log /opt/pubscribe/webapps/pubscribe/WEB-INF/classes/log4j.properties
simdbmu /opt/Symantec/simserver/logs/simdbmu.log /opt/Symantec/simserver/simdbmu/simdbmu-log4j.properties
dimserver /opt/Symantec/simserver/logs/dimserver.log /opt/Symantec/simserver/dim/log4j.properties
simserver /opt/Symantec/simserver/logs/simcm.log /opt/Symantec/simserver/simcm/log4j.properties
icesvc /opt/Symantec/simserver/logs/icesvc.log /opt/Symantec/simserver/icesvc/log4j.properties
assetsvc /opt/Symantec/simserver/logs/assetsvc.log /opt/Symantec/simserver/assetsvc/log4j.properties
kbsvc /opt/Symantec/simserver/logs/kbsvc.log /opt/Symantec/simserver/kbsvc/kb-log4j.properties
querysvc /opt/Symantec/simserver/logs/querysvc.log /opt/Symantec/simserver/querysvc/query-log4j.properties
rulesvc /opt/Symantec/simserver/logs/rulesvc.log /opt/Symantec/simserver/rulesvc/log4j.properties
configurationsvc /opt/Symantec/simserver/logs/configurationsvc.log /opt/Symantec/simserver/configurationsvc/log4j.properties
notificationsvc /opt/Symantec/simserver/logs/notification.log /opt/Symantec/simserver/notification/notification-log4j.properties
schedulersvc /opt/Symantec/simserver/logs/scheduler.log /opt/Symantec/simserver/scheduler/scheduler-log4j.properties
ticketsvc /opt/Symantec/simserver/logs/ticketsvc.log /opt/Symantec/simserver/ticketsvc/ticket-log4j.properties
eventfindersvc /opt/Symantec/simserver/logs/eventfindersvc.log /opt/Symantec/simserver/log4j.properties
statsvc /opt/Symantec/simserver/logs/statsvc.log /opt/Symantec/simserver/statsvc-log4j.properties
wsrf /opt/pubscribe/logs/catalina.out /opt/pubscribe/webapps/pubscribe/WEB-INF/classes/log4j.properties


Log file: /opt/Symantec/sesa/logs/eventservice.log

Log Service: com.symantec.sim.eventservice.EventServlet

Functions: Receiving events

Debug Logging:

service sesevents stop
vi /opt/Symantec/sesa/eventservice/webapps/sesa/WEB-INF/classes/log4j.properties

Remove the # from this line:
#log4j.logger.com.symantec.sim.eventservice=DEBUG

service sesevents start

Note: The EventServlet also accesses the data mungers. To debug the EventServlet's data munger accesses, in the same file change these lines:

# set datamunge to DEBUG to see exhaustive debugging information
# (this will creates a flood of log messages and will affect performance)
#log4j.logger.com.symantec.sim.datamunge=INFO
#log4j.logger.com.symantec.sim.datamunge.BaseMungerImpl=DEBUG
#log4j.logger.com.symantec.sim.datamunge.MungeDispatcher=DEBUG

Note: Do not leave EventServlet's debugging on as it will impact EPS performance.


Log file: /opt/Symantec/sesa/servletengine/logs/imr.log

Log Service:

Functions: Web pages

Debug Logging:

service ibmhttpd stop
vi /opt/Symantec/sesa/servletengine/webapps/imr/WEB-INF/classes/log4j.properties

Change log4j.rootCategory=ERROR to log4j.rootCategory=DEBUG

service ibmhttpd start




 



Legacy ID



2007100807224354


Article URL http://www.symantec.com/docs/TECH85647


Terms of use for this information are found in Legal Notices