Cisco Cisco Prime Service Catalog 10.0 Technical References
5-21
Cisco Prime Service Catalog 10.0 Configuration Guide
OL-31034-01
Chapter 5 System Administration
Managing the Application
System performance of logging may be an issue. With full DEBUG level enabled, logs get very large
very quickly, so logging at full debug and trace levels should be enabled only for short periods. System
performance will likely slow down significantly, so logging on a Production system should be kept to a
minimum, and only for the length of time required to reproduce an issue. For more information, see
very quickly, so logging at full debug and trace levels should be enabled only for short periods. System
performance will likely slow down significantly, so logging on a Production system should be kept to a
minimum, and only for the length of time required to reproduce an issue. For more information, see
.
Sample Log File Entries
There are four types of log entries: E (Error), W (Warning), I (Info), D (Debug), listed in decreasing
order of severity. A sample section of the log might look like the following:
order of severity. A sample section of the log might look like the following:
[8/22/05 8:58:39:279 CDT] 4643aa LDAPEntryBean
E
com.newscale.bfw.ldap.LDAPEntryBean
Error matching expression, there might be an open parenthesis in expr
[8/22/05 8:58:39:290 CDT] 4643aa LDAPEntryBean
E
com.newscale.bfw.ldap.LDAPEntryBean
TRAS0014I: The following exception was logged
org.apache.oro.text.perl.MalformedPerl5PatternException: Invalid option: N
at org.apache.oro.text.perl.Perl5Util.substitute
at org.apache.oro.text.perl.Perl5Util.substitute
at com.newscale.bfw.ldap.LDAPEntryBean.processExpression(LDAPEntryBean.java:328)
at com.newscale.bfw.ldap.LDAPEntryBean.getRegexpAttrValue(LDAPEntryBean.java:296)
[9/11/05 15:01:10:217 EST] 4715bea8 MessagequeueC
W
com.celosis.logger.MessagequeueChannel TRAS0014I: The following exception was logged
java.sql.SQLException: [newScale][Oracle JDBC Driver]There is no process to read data
written to a pipe.
[9/11/05 10:26:22:934 EST] 76b9beb7 UdKernelUtil
W
com.newscale.bfw.udkernel.util.UdKernelUtil The Cubic's value is NULL
[9/11/05 10:26:22:944 EST] 76b9beb7 OrgUnitDataso
I
com.newscale.comps.orgunit.dao.OrgUnitDatasource Searching Organizational units for
cleaned pattern <%> for PersonID <298 >
WebSphere Logging
Cisco Prime Service Catalog routes most messages to STDOUT which WebSphere logs to the
SystemOut.log. The SystemErr.log contains any WebSphere errors and information about Cisco Prime
Service Catalog timing and memory usage. Both logs can usually be found at a path like:
SystemOut.log. The SystemErr.log contains any WebSphere errors and information about Cisco Prime
Service Catalog timing and memory usage. Both logs can usually be found at a path like:
/apps/WebSphere/AppServer/profiles/cisco/logs/server1
You can enable traces to focus in on a specific area of the application. The trace log for the server can
be enabled on a particular Java class or package. General logging and tracing is enabled on any of the
exposed classes that appear in WebSphere. Other nonexposed classes can be added as well (although the
specific class names would need to be provided by the Cisco Technical Assistance Center (TAC) on a
case by case basis depending on the situation under which the logging is required).
be enabled on a particular Java class or package. General logging and tracing is enabled on any of the
exposed classes that appear in WebSphere. Other nonexposed classes can be added as well (although the
specific class names would need to be provided by the Cisco Technical Assistance Center (TAC) on a
case by case basis depending on the situation under which the logging is required).