Book Image

GlassFish Administration

By : Xuekun Kou
Book Image

GlassFish Administration

By: Xuekun Kou

Overview of this book

To build a powerful production environment for your Java EE systems, you need a great application server, and the skills to manage it. This book gives you all that you are looking for. This book will help you gain the necessary skills to install, configure, tune, and troubleshoot GlassFish so that you can fully unleash its power. It will teach you how to use the GlassFish application server, with a special focus on administration tasks. It presents the GlassFish administrative tasks in a logical sequence, with each chapter focusing on a specific topic. Starting with installation and moving through configuration, this book takes a careful look at the administration console so that you get a complete understanding of GlassFish and its administrative features. It will help you understand how to deploy Java EE, Ruby on Rails and other supported applications to GlassFish, and how to configure the necessary resources for these applications. You will also learn how to maintain, tune, and troubleshoot your GlassFish server. Also includes a bonus chapter introducing Glassfish v3.
Table of Contents (17 chapters)
GlassFish Administration
Credits
About the Author
Acknowledgement
About the Reviewers
Preface

Custom and external JNDI resources


Besides the standard resource types, GlassFish also supports two additional types of resources—custom and external. In this section, we examine their applicability, and discuss how to configure them.

Working with custom resources

A custom resource is typically a Java object that is read-only, and shared by many components in the application server runtime environment. A custom instance is always created by a factory object that implement the javax.naming.spi.ObjectFactory interface. When a custom resource is requested by an application component, the factory object will return the resource object.

Note

Because a custom resource is typically shared among all the application components, and it is typically read-only, its capability is rather limited. Therefore, it is mostly used to provide some additional configuration data for an environment, and it is not very suitable for hosting complicated application logic.

Custom resources are configured in the local...