Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering JBoss Enterprise Application Platform 7

You're reading from   Mastering JBoss Enterprise Application Platform 7 Core details of the Enteprise server supported by clear directions and advanced tips.

Arrow left icon
Product type Paperback
Published in Aug 2016
Publisher Packt
ISBN-13 9781786463630
Length 390 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Luigi Fugaro Luigi Fugaro
Author Profile Icon Luigi Fugaro
Luigi Fugaro
Francesco Marchioni Francesco Marchioni
Author Profile Icon Francesco Marchioni
Francesco Marchioni
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Installation and Configuration FREE CHAPTER 2. The CLI Management Tool 3. Managing EAP in Domain Mode 4. Deploying Applications 5. Load Balancing 6. Clustering EAP 7 7. Logging 8. Configuring Database Connectivity 9. Configuring EAP 7 for Java EE Applications 10. Messaging Administration 11. Securing the Application Server 12. New Security Features of EAP 7 13. Using EAP 7 with Docker 14. Running EAP 7 on the Cloud Using OpenShift

Managing your application logging


In the first part of this chapter, you learnt that the application server uses the JBoss LogManager to trace server activities. As far as applications are concerned, you have a wider set of options. For example, you can use the following:

  • Package any Java logging framework with your application (such as log4j), also known as per-deployment logging.

  • Define a logging profile in your EAP configuration, which is dedicated to your applications.

  • Define a specific logger (and associate it with a handler) to keep your application logs separate from your server logs. You can check the Defining new loggers section for an example of creating a new logger.

Per-deployment logging

As we said, per-deployment logging allows you to package a logging framework to your application, which includes its configuration file and (if not bundled into the application server) its libraries. If you are packaging an EAR, the configuration should be added in the META-INF directory. On the...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image