Sun Java System Application Server 9.1 Administration Guide

Application Server Overview

The Sun Java System Application Server provides a Java EE compatible server for the development and deployment of Java EE applications and Java Web Services. Key features include scalable transaction management, container-managed persistence runtime, performant web services, clustering, high availability, security, and integration capabilities. This section contains the following topics:

Usage Profiles

Every administrative domain is associated with a usage profile, which identifies the capabilities of that domain. Application Server provides the following profiles:

Note –

Upgrade from Application Server 8.x Enterprise Edition is supported only by the enterprise profile. Use the developer profile if you are upgrading from Application Server 8.x Platform Edition. For more information on the Upgrade process, see Chapter 2, Upgrading an Application Server Installation, in Sun Java System Application Server 9.1 Upgrade and Migration Guide.

The domain provides a preconfigured runtime for the user applications. Usage profiles facilitates the distinction between the Application Server binaries and the runtime configuration. Profiles enable you to use the same installation of Application Server to create different domains with profiles that suit specific needs. For example, a developer may want to use the Application Server to get to know the latest Java EE specifications. This developer does not need stringent security settings. Another user who wants to deploy applications in a production environment needs an inherently secure environment.

Table 1–1 lists the features available with each profile:

Table 1–1 Features Available for Each Profile


Developer Profile 

Cluster Profile 

Enterprise Profile 

Security store 




Clustering/Standalone instances 

Not available 



Security Manager 





Not available 

Not available 


Load balancing 

Not available 



Node agents 

Not available 



Using the Enterprise Profile

To use the enterprise profile, perform the following tasks:

  1. Download and install NSS and HADB separately.

  2. Modify the asenv.conf file as follows:

    • AS_HADB points to the folder where HADB is installed.

    • AS_NSS points to the folder where NSS shared objects are available.

    • AS_NSS_BIN points to the folder where NSS binaries, such as certutil, are stored.

Upgrading an Earlier Domain to Application Server 9.1

You can use the start-domain command to upgrade Application Server 8.x or 9.0 domains to Application Server 9.1. Use one of the following ways to upgrade your domain:

What is the Application Server?

The Application Serveris a platform that supports services from Web publishing to enterprise-scale transaction processing while enabling developers to build applications based on JavaServer Pages (JSPTM), Java servlets, and Enterprise JavaBeansTM (EJBTM) technology.

The Application Server 9.1 Clustering and Enterprise profiles provide advanced clustering and failover technologies. These features enable you to run scalable and highly available Java EE applications.

Application Server Architecture

This section describes Figure 1–1, which shows the high-level architecture of the Application Server.

Figure 1–1 Application Server Architecture

Figure shows high-level architecture, including containers,
services, tools, and communication with outside systems such as databases.

Access to External Systems

The Java EE platform enables applications to access systems that are outside of the application server. Applications connect to these systems through objects called resources. One of the responsibilities of an administrator is resource configuration. The Java EE platform enables access to external systems through the following APIs and components:

Tools for Administration

The Application Server provides the following administration tools and APIs:

Admin Console

The Admin Console is a browser-based tool that features an easy-to-navigate interface and online help. The administration server (also called the Domain Administration Server or DAS) must be running to use the Admin Console. To, launch the Administration Console, you must know the administration server hostname and port number. When the Application Server was installed, you chose a port number for the server, or used the default port of 4848. You also specified a user name and master password.

To start the Admin Console, in a web browser type:


For example:

If the Admin Console is running on the machine on which the Application Server was installed, specify localhost for the host name.

On Windows, start the Application Server Admin Console from the Start menu.

The installation program creates the default administrative domain (named domain1). . After installation, additional administration domains can be created. Each domain has its own domain administration server, which has a unique port number. When specifying the URL for the Admin Console, be sure to use the port number for the domain to be administered.

If your configuration includes remote server instances, create node agents to manage and facilitate remote server instances. It is the responsibility of the node agent to create, start, stop, and delete a server instance. Use the command line interface (CLI) commands to set up node agents.

Command-line Interface (asadmin Utility)

The asadmin utility is a command-line interface for the Sun Java System Application Server. Use the asadmin utility and the commands associated with it to perform the same set of administrative tasks offered by the Admin Console. The default installation root directory on Solaris is /opt/SUNWappserver.

To start the asadmin utility, go to the as-install/bin directory and enter:

$ ./asadmin

To list the commands available within asadmin:

asadmin> help

It is also possible to issue an asadmin command at the shell’s command prompt:

$ asadmin help

To view a command’s syntax and examples, type help followed by the command name. For example:

asadmin> help create-jdbc-resource

The asadmin help information for a given command displays the UNIX man page of the command. These man pages are also available in HTML and PDF format in the Sun Java System Application Server 9.1 Reference Manual.


In the Java 2, Platform Standard Edition 5.0, the Java Monitoring and Management Console (JConsole) was introduced. JConsole is used to monitor the Sun Java System Application Server. You can use either the JConsole remote tab, or the advanced tab to connect to the Application Server.

Application Server Management Extension (AMX)

The Application Server Management eXtension is an API that exposes all of the Application Server configuration and monitoring JMX managed beans as easy-to-use client-side dynamic proxies implementing the AMX interfaces.

For more information on using the Application Server Management Extension, see Chapter 20, Using the Application Server Management Extensions, in Sun Java System Application Server 9.1 Developer’s Guide.