How to enable loggingDebug for request scoped component?

Question

How to make loggingDebug = "true" for a request scoped component in /dyn/admin ?

score 0 · Answer 1 · answered Dec 11 '14 at 08:50

0

You cannot do this via /dyn/admin as the component is by its nature request scoped. What you can do is edit the component's properties file and it will pick this up for the next request.

answered Dec 11 '14 at 08:50

radimpe

3,197
2
27
46

We cannot do the same for upper environments like QA and production right? – anonymous Dec 11 '14 at 09:42
It depends. Do you have an exploded `EAR`? What about a configured `ATG-Data` folder? – radimpe Dec 11 '14 at 09:53

score 0 · Answer 2 · answered Feb 26 '15 at 23:12

yes you can actually do that. go the dyn/admin/nucleus/ and add the path after the nucleus.

check this link https://community.oracle.com/thread/2444056

so basically say I have the properties file in atg/userprofiling/myPropertiesFile.properties then just type http://localhost:port/dyn/admin/nucleus/atg/userprofiling/myPropertiesFile

HIH

score 0 · Answer 3 · answered Aug 07 '18 at 13:39

First you have to define a global component with a loggingDebug property.

Example:

LoggingConfiguration.properties

$class=com.example.configuration.LoggingConfiguration
$scope=global

loggingDebug=false

Now in your request scoped component, link the loggingDebug property to LoggingConfiguration.loggingDebug as follows:

loggingDebug^=/path/LoggingConfiguration.loggingDebug

So you can control the loggingDebug configuration from the dyn/admin using the property in global scoped component LoggingConfiguration.

Once the LoggingConfiguration.loggingDebug is set to true, you will have logging enabled in further requests.

How to enable loggingDebug for request scoped component?

3 Answers3