Red Hat Training
A Red Hat training course is available for Red Hat JBoss Enterprise Application Platform
5.4. Logging Profiles
5.4.1. About Logging Profiles
Logging profiles are only available in version 6.1.0 and later. They cannot be configured using the management console.
Logging profiles are independent sets of logging configuration that can be assigned to deployed applications. As with the regular logging subsystem, a logging profile can define handlers, categories and a root logger but cannot refer to configuration in other profiles or the main logging subsystem. The design of logging profiles mimics the logging subsystem for ease of configuration.
The use of logging profiles allows administrators to create logging configuration that are specific to one or more applications without affecting any other logging configuration. Because each profile is defined in the server configuration, the logging configuration can be changed without requiring that the affected applications be redeployed.
Each logging profile can have the following configuration:
- A unique name. This is required.
- Any number of log handlers.
- Any number of log categories.
- Up to one root logger.
An application can specify a logging profile to use in its
MANIFEST.MFfile, using the
5.4.2. Specify a Logging Profile in an Application
An application specifies the logging profile to use in its
- You must know the name of the logging profile that has been setup on the server for this application to use. Ask your server administrator for the name of the profile to use.
Procedure 5.3. Add Logging Profile configuration to an Application
MANIFEST.MFIf your application does not have a
MANIFEST.MFfile: create one with the following content, replacing NAME with the required profile name.
Manifest-Version: 1.0 Logging-Profile: NAMEIf your application already has a
MANIFEST.MFfile: add the following line to it, replacing NAME with the required profile name.
If you are using Maven and the
maven-war-plugin, you can put your MANIFEST.MF file in
src/main/resources/META-INF/and add the following configuration to your
<plugin> <artifactId>maven-war-plugin</artifactId> <configuration> <archive> <manifestFile>src/main/resources/META-INF/MANIFEST.MF</manifestFile> </archive> </configuration> </plugin>
When the application is deployed it will use the configuration in the specified logging profile for its log messages.