This one comes courtesy of Fabien Sanglier, a WCI guru of epic proportions (no, he didn’t make me say that…).
At our client site, we noticed that Analytics was logging gigs worth of data to the weblogic.out file – a catch-all file for logging reported via the standard out pipe. Note that IIS doesn’t record logs on this stream, so this is a Weblogic-only problem. The line recorded over and over (one for each hit):
OPENUSAGE(INFO ): ==> Event sent to: //UsageTracking@openusage/ wci-analyticscollector| port=31314/ BYTEARR
To prevent these events from being logged, he suggests updating %PT_HOME%/settings/configuration.xml to reduce logging and turn off console logging:
<component name="analytics-communication:config" type="http://www.plumtree.com/config/component/types/analytics-communication"> <setting name="logging:level"> <value xsi:type="xsd:string">WARN</value> </setting> <setting name="console-logging:enabled"> <value xsi:type="xsd:boolean">false</value> </setting> </clients> </component>
In my own insignificant way, I’ll add a little bit to this tip: These settings, like most of the configuration settings in configuration.xml, can (and should, if possible) be updated in the Oracle Configuration Manager:
