Logger Definition Not Found!

Question

Hi,
I created a logger.xml file like this:
<Logger name="Test" loggerInterface="com.sapportals.portal.prt.logger.ILogger" locationName="Test" isActive="true">
<LoggerClass className="com.sapportals.portal.prt.logger.SimpleFileLogger" level="ALL">
<param filename="logs/test.log" append="true" />
</LoggerClass>
</Logger>
In my code I get the logger like this:
ILogger logger = PortalRuntime.getLogger("Test");
The default trace writes:
<b>[LoggerManager] Logger Test - definition not found!</b>
Why?
Any help is greatly appreciated. Please do not post links to other threads without explaining how to solve the problem.
Thanks.
/ Elvez

Answer 1

I assume you've seen the warning:
<b>Important Changes in SAP NetWeaver Support Package Stack 04
The logging and tracing structure was changed in the SAP NetWeaver Support Package Stack 04 release. In the past, the settings were stored in file logger.xml in the portal application and displayed and configured with the Logging Console in the portal. With Support Package Stack 04, the Logging Console was removed from the portal. Information is read from the file logger.xml and the locations are created directly in the Log Configurator Service of the J2EE Engine.
The assignment of the information from logger.xml to the Log Configurator Service takes place according to fixed rules. If the location defined in logger.xml does not exist, a new location is created in the Log Configurator Service by placing the prefix com.sap.portal in front of the existing location name.
Location in logger.xml = mylogger  is changed to a location in Log Configurator Service com.sap.portal.mylogger. The display in the Log Viewer of the J2EE Engine also appears under com.sap.portal.mylogger.
Note that some parameters in the previous PRT Logger definition are no longer valid and some parameters were changed:
The location severity now depends on two parameters: „is active“ and „level“. Only if the parameter is set to „is active“ (true) can the location severity be defined with parameter „level“. If „is active“ is not true, the location severity is not defined („None“).
Parameters „filename“, „pattern“, „append“ and „limit“ are ignored. The portal application only uses the portal destination service_com.sap.portal.prt.sapj2ee_portalTrace and a predefined log formatter.</b>
Sounds like you need to use the Log Configurator service...
Cheers