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
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Middleware Management with Oracle Enterprise Manager Grid Control 10g R5

You're reading from   Middleware Management with Oracle Enterprise Manager Grid Control 10g R5 Monitor, diagnose, and maximize the system performance of Oracle Fusion Middleware solutions using this book and eBook

Arrow left icon
Product type Paperback
Published in Dec 2009
Publisher Packt
ISBN-13 9781847198341
Length 332 pages
Edition 1st Edition
Concepts
Arrow right icon
Toc

Table of Contents (20) Chapters Close

Middleware Management with Oracle Enterprise Manager Grid Control 10g R5
Credits
1. Foreword
About the Authors
About the Reviewers
2. Preface
1. Enterprise Manager Grid Control FREE CHAPTER 2. Installing Enterprise Manager Grid Control 3. Enterprise Manager Key Concepts and Subsystems 4. Managing Oracle WebLogic Server 5. Managing Oracle Application Server 6. Managing Forms and Reports Services and Applications 7. SOA Management — BPEL Management 8. SOA Management — OSB (aka ALSB) Management 9. Managing Identity Manager Suite 10. Managing Coherence Cluster 11. Managing Non-Oracle Middleware 12. Java and Composite Applications Monitoring and Diagnostics 13. Building Your Monitoring Plug-in 14. Best Practices for Managing Middleware Components Using Enterprise Manager

Best practices for managing non-Oracle Java middleware


Now that we have concluded the management of non-Oracle Java middleware, here are some best practices that we recommend to get the best out of Enterprise Manager.

  • You can monitor multiple installs of non-Oracle middleware targets running on multiple hosts from a single agent. If you are monitoring a large number of application server targets, do not use the agent to monitor more than 25-30 application server instances.

  • Do not use an agent to monitor different types of Java targets, for example do not use an agent to monitor both JBoss Application Server and IBM WebSphere. The agent communicates with the application servers using JMX and requires client-side JAR files provided by application servers and there could be conflicting classes that could cause classloading errors at the agent side. This will result in metric collection error.

  • Avoid monitoring different versions of the same application server from the same agent, unless your...

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