Configuring trace file size and number in WebCenter Content 11g

Lately I've been doing a lot of debugging using the System Output tracing in WebCenter Content 11g.  This is built-in tracing in the content server which provides a great level of detail on what's happening under the hood.  You can access the settings as well as a view of the tracing by going to Administration -> System Audit Information.  From here, you can select the tracing sections to include.  Some of my personal favorites are searchquery,  systemdatabase, userstorage, and indexer.  Usually I'm trying to find out some information regarding a search, database query, or user information.  Besides debugging, it's also very helpful for performance tuning.

One of the nice tricks with the tracing is it honors the wildcard (*) character.  So you can put in 'schema*' and gather all of the schema related tracing.  And you can notice if you select 'all' and update, it changes to just a *.  

To view the tracing in real-time, you simply go to the 'View Server Output' page and the latest tracing information will be at the bottom. This works well if you're looking at something pretty discrete and the system isn't getting much activity.  But if you've got a lot of tracing going on, it would be better to go after the trace log file itself.  By default, the log files can be found in the <content server instance directory>/data/trace directory. You'll see it named 'idccs_<managed server name>_current.log.  You may also find previous trace logs that have rolled over.  In this case they will identified by a date/time stamp in the name.  By default, the server will rotate the logs after they reach 1MB in size.  And it will keep the most recent 10 logs before they roll off and get deleted.  If your server is in a cluster, then the trace file should be configured to be local to the node per the recommended configuration settings.

If you're doing some extensive tracing and need to capture all of the information, there are a couple of configuration flags you can set to control the logs.

#Change log size to 10MB and number of logs to 20
FileSizeLimit=10485760
FileCountLimit=20

This is set by going to Admin Server -> General Configuration and entering them in the Additional Configuration Variables: section.  Restart the server and it should take on the new logging settings. 

Update - Sept. 27, 2012

 Kevin Smith has a nice blog post that describes some of these trace sections in detail.

Comments:

How does this relate to the UseRedirectedOutput=true setting?

http://docs.oracle.com/cd/E21043_01/doc.1111/e10726/c08_config_ref329.htm

Posted by Jonathan on September 24, 2012 at 04:13 PM CDT #

Hey Jonathan,

This was used in the 10g version and earlier when running the content server as a service. It would write the output from the JVM and any tracing to the <stellent_dir>/bin/IdcServerNT.log file. See the 10g Troubleshooting guide (http://docs.oracle.com/cd/E10316_01/cs/cs_doc_10/documentation/admin/troubleshooting_10en.pdf). This no longer applies in 11g when running on the application server, so it should probably be removed from the reference guide.

Thanks,
-Kyle

Posted by guest on September 26, 2012 at 10:47 AM CDT #

UseRedirectedOutput=true only applied to Windows. When running on Linux the trace output was always written to a file called log in the etc directory under the Content Server install directory for a single instance or in the stub directory on clusters.

Posted by Kevin Smith on September 27, 2012 at 06:22 AM CDT #

Hi kyle,

Can you tell me if we can add a new tracing section, If yes then please let me know the steps.

Thaniks in advance,,

Posted by guest on November 05, 2012 at 07:04 AM CST #

For creating a new tracing section, you simply need to import the intradoc.common.Report class and then call the method as such: Report.trace("name_of_section", "message to output", null);

Then in they Active Sections, you simply add the name of your new section and it will appear in the output.

Thanks,
-Kyle

Posted by Kyle Hatlestad on November 19, 2012 at 10:52 AM CST #

For creating the trace section in the dropdown menu, this blog post should be of some help: http://stellentpmp.blogspot.com/2011/03/create-your-own-tracing-section.html

Note: Putting the trace section into the dropdown menu is not required. You can, as Kyle said, simply put the section name in the input box.

Jonathan

Posted by Jonathan Hult on November 19, 2012 at 11:01 AM CST #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Kyle Hatlestad is a Solution Architect in the WebCenter Architecture group (A-Team) who works with WebCenter Content and other products in the WebCenter & Fusion Middleware portfolios. The WebCenter A-Team blog can be found at: https://blogs.oracle.com/ ateam_webcenter/

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today