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
About the Author
About the Reviewers


In this chapter, we learned that for global security to work, we need a repository of users, and groups of users, who are authorized to access the Administrative console. WAS uses three main types of registries, which can be used to store the users and groups that are given access to log in and configure the server. On large systems used by businesses and other organizations, there will likely be several system administrators and application servers dispersed across more than one machine and, if you use a local OS user registry, each machine would have its own user registry and it would be hard to keep them all up-to-date and secure. Hence LDAP is a better option. We also learned that it is possible to federate multiple repositories together, allowing user searches to be done across multiple mixed repositories. We covered security domains that allow different security attributes configured to separate security concerns as might be required in a real-world WAS installation. LTPA keys...