Book Image

IBM WebSphere Application Server 8.0 Administration Guide

By : Steve Robinson
Book Image

IBM WebSphere Application Server 8.0 Administration Guide

By: Steve Robinson

Overview of this book

Administrators require a secure, scalable, and resilient application infrastructure to support the development of JEE applications and SOA services. IBM’s WebSphere Application Server is optimized for this task, and this book will ensure that you can utilize all that this tool has to offer with the exciting new features of IBM WebSphere Application Server 8.0.IBM WebSphere Application Server 8.0 Administration Guide is fully revised with details of the new functionality of WebSphere Application Server 8.0, including the new installation GUI, managed deployment, and HPEL. With this book in hand, you will be equipped to provide an innovative, performance-based foundation to build, run, and manage JEE applications and SOA services.IBM WebSphere Application Server 8.0 has been tuned for higher performance out of the box, and numerous enhancements have been made to give you as an administrator more options for increasing runtime performance. This book will allow you to utilize all of these features, including HPEL logging and disabling WebSphere MQ Messaging. You will be taken through how to configure and prepare WebSphere resources for your application deployments, and by the end of IBM WebSphere Application Server 8.0 Administration Guide, you will be able to successfully manage and tune your WebSphere 8.0 implementation.
Table of Contents (19 chapters)
IBM WebSphere Application Server 8.0 Administration Guide
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Index

Security domains


As we learned earlier in the chapter, WebSphere Application Server security settings are defined in the global security section within the Administrative console. By default global security is specific to one cell and is applicable cell-wide. Since WebSphere Application Server V7, we now have the ability to define more than one security domain. Security domains allow segregation of security settings and can override a subset of the global security settings for a given domain. Domains can be used to provide customized security settings for applications and service integration buses. Each security domain is assigned a level of scope that defines where its settings are applicable. Settings that are not explicitly defined in a security domain, will default to the global security settings.

Since WAS provides a single-domain configuration by default, making administration easier for most security requirements. However, a single domain might not be the ideal configuration for certain...