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

Global security

In Chapter 1, WebSphere Application Server 8.0: Product Overview, during the installation process of the WebSphere Application Server, we opted not to turn on global security and thus did not have to supply a password to log in to the Administrative console. We logged in using the username wasadmin and we were not prompted for a password. The truth of the matter is that we could have actually used any name, as the console wasn't authenticating us at all. To protect our WAS from unauthorized access, we need to turn on global security.


It is important to secure the administration of WebSphere, even if the applications being installed are not using security. It is paramount to ensure we have control of our WebSphere environments. The larger your team is, the more important this becomes. In time, other people in your organization will get to know the URLs of your WebSphere servers and, if they are not secured, you cannot really know who is making changes without your approval...