Weblogic

by Avinash Chugh and Jon Mountjoy

Book Overview

BEA's WebLogic Server implements the full range of J2EE technologies, and includes many additional features such as advanced management, clustering, and web services. Widely adopted, it forms the core of the WebLogic platform, providing a stable framework for building scalable, highly available, and secure applications. In fact, in the long list of WebLogic's strengths and features, only one shortcoming stands out: the documentation that comes with...

• Format: Paperback
• Language: English
• ISBN: 059600432X
• ISBN13: 9780596004323
• Release Date: March 2004
• Publisher: O'Reilly Media
• Length: 828 Pages
• Weight: 2.65 lbs.
• Dimensions: 1.5" x 7.0" x 9.3"

Customer Reviews

Easily the best WebLogic book ever

Don't be fooled by the bad reviews here...if you need to learn WebLogic in "21 days" or want a "kick start", then perhaps this book is not for you. But if you are an experienced developer that needs information one notch better than the BEA docs, then this book should be on your bookshelf. Mine stays at work, dog-eared and always ready to explain some detail to help solve a problem. Node Manager? Clustering? Domains configuration? SSL? It's all covered, in depth. Note that this book covers BEA WebLogic Server 8.1, not Portal, Integration, or WorkShop.

Good Book: Very Comprehensive :

Hi, Though a good book but it is simplly a cut and paste of online weblogic documents. if you want to carry all the online doc in one book then buy this book. But still, I would recommend this book to all interested in weblogic admin. Thanks deepak

A comprehensive and useful overview of WebLogic

WebLogic has become a very popular tool for integrating and managing applications in multi-tier environments. Implemented as an application server, it remains one of the leaders in J2EE compliance. There is a lot to WebLogic, and so it is unlikely that any one person would need to be in a situation where expertise in all of its properties and capabilities would be required. Because of its popularity though, for those who must confront it via Web applications, a good general familiarity with it is essential. This book gives a comprehensive overview of WebLogic, and readers who need a particular set of questions answered or need an in-depth review will find it useful. The interest of this reviewer was in performance issues in WebLogic, and so the review will be confined to these issues as they are discussed in the book, as space permits. The book devotes an entire chapter to the performance tuning of WebLogic applications, but some of the other performance issues discussed in the book outside of this chapter include: 1. The Enterprise Java Bean (EJB) container supports checking on value changes so that only persistent fields that have been modified are written to the database. This results in enhanced performance for the EJB. 2. WebLogic provides flow control mechanisms that allow the suppression of messages during times of peak messaging. This ensures that the performance of other WebLogic services will not be affected adversely. 3. The use of cache filters, which enhance application performance by caching various portions of the application without needing code changes. 4. Client-server interactions are optimized when the client is operating within the same virtual machine (VM) as the Remote Method Invocation (RMI) object. Java pass-by-reference semantics when the client and the server object are collocated. 5. The Java Database Connectivity (JDBC) connection pools enhance the performance and scalability of an application by allowing the same physical connection to be shared by multiple applications. Connection testing however can cause delays, since WebLogic will execute the test whenever the connection pool receives a connection request from a client. 6. Although by default WebLogic allows one to retrieve the physical connection associated with a logical connection, it cannot reuse a physical connection, but will instead discard it and replace it with a new connection in the pool. The performance of an application will be degraded if it depends on the physical connections, since any statement cache might not be valid for the new connection in the pool. One can change this default however to allow physical connections to be returned to the pool when they are closed, if one really desires to do so. 7. The performance of JDBC applications can be improved by configuring WebLogic so that it maintains a statement cache for each connection in a connection pool. When a callable statement is created using a connection obtained from the poo

Fantastic resource for J2EE developers

This is a must-have book for J2EE engineers. Chapter five, on JDBC, is thorough and excellent. The JMS chapter, number eight, is very in-depth and worth the price of admission. Chapter twelve, on deployment, has fine coverage of both the theory and the execution of web application deployment. Chapters thirteen and fourteen on domain management and cluster are fantastic. Chapter seventeen on security is also great.That's the good news. The book isn't perfect. Some chapters are way too brief. For example the chapter on transactions is just an overview. And the chapter on XML is completely superfluous. Negatives aside, this is a great book. The chapters on JDBC, EJB, Deployment, and Clustering are worth the price alone.