JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle GlassFish Server 3.1 Administration Guide
search filter icon
search icon

Document Information


1.  Overview of GlassFish Server Administration

Default Settings and Locations

Configuration Tasks

Administration Tools

Instructions for Administering GlassFish Server

Part I Runtime Administration

2.  General Administration

3.  Administering Domains

4.  Administering the Virtual Machine for the Java Platform

5.  Administering Thread Pools

6.  Administering Web Applications

7.  Administering the Logging Service

8.  Administering the Monitoring Service

9.  Writing and Running JavaScript Clients to Monitor GlassFish Server

10.  Administering Life Cycle Modules

11.  Extending and Updating GlassFish Server

Part II Resources and Services Administration

12.  Administering Database Connectivity

13.  Administering EIS Connectivity

14.  Administering Internet Connectivity

About Internet Connectivity

About HTTP Network Listeners

About Virtual Servers

Administering HTTP Network Listeners

To Create an Internet Connection

Administering HTTP Protocols

To Create a Protocol

To List Protocols

To Delete a Protocol

Administering HTTP Configurations

To Create an HTTP Configuration

To Delete an HTTP Configuration

Administering HTTP Transports

To Create a Transport

To List Transports

To Delete a Transport

Administering HTTP Network Listeners

To Create an HTTP Network Listener

To List HTTP Network Listeners

To Update an HTTP Network Listener

To Delete an HTTP Network Listener

To Configure an HTTP Listener for SSL

To Delete SSL From an HTTP Listener

To Assign a Default Virtual Server to an HTTP Listener

Administering Virtual Servers

To Create a Virtual Server

To List Virtual Servers

To Update a Virtual Server

To Delete a Virtual Server

To Assign a Default Web Module to a Virtual Server

To Assign a Virtual Server to an Application or Module

To Set JSESSIONIDSSO Cookie Attributes

15.  Administering the Object Request Broker (ORB)

16.  Administering the JavaMail Service

17.  Administering the Java Message Service (JMS)

18.  Administering the Java Naming and Directory Interface (JNDI) Service

19.  Administering Transactions

Part III Appendixes

A.  Subcommands for the asadmin Utility


About Internet Connectivity

The HTTP service provides functionality for deploying web applications and for making deployed web applications accessible by Internet clients, either in a single application server instance or in a cluster of multiple server instances. HTTP services are provided by two kinds of related objects: listeners and virtual servers.

For more information about clusters, see the Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide.

The following topics are addressed here:

About HTTP Network Listeners

An HTTP listener, also known as a network listener, is a listen socket that has an Internet Protocol (IP) address, a port number, a server name, and a default virtual server. Each virtual server provides connections between the server and clients through one or more listeners. Each listener must have a unique combination of port number and IP address. For example, an HTTP listener can listen for a host on all configured IP addresses on a given port by specifying the IP address Alternatively, the listener can specify a unique IP address for each listener while using the same port.

Because an HTTP listener is a combination of IP address and port number, you can have multiple HTTP listeners with the same IP address and different port numbers, or with different IP addresses and the same port number (if your host was configured to respond to these addresses). However, if an HTTP listener uses the IP address, which listens on all IP addresses on a port, you cannot create HTTP listeners for additional IP addresses that listen on the same port for a specific IP address. For example, if an HTTP listener uses (all IP addresses on port 8080), another HTTP listener cannot use The host running the GlassFish Server typically has access to only one IP address. HTTP listeners typically use the IP address and different port numbers, with each port number serving a different purpose. However, if the host does have access to more than one IP address, each address can serve a different purpose.

To access a web application deployed on GlassFish Server, use the URL http://localhost:8080/ (or https://localhost:8081/ for a secure application), along with the context root specified for the web application.

To access the Administration Console, use the URL https://localhost:4848/ or http://localhost:4848/asadmin/ (console default context root).

About Virtual Servers

A virtual server, sometimes called a virtual host, is an object that allows the same physical server to host multiple Internet domain names. All virtual servers hosted on the same physical server share the IP address of that physical server. A virtual server associates a domain name for a server (such as with the particular server on which GlassFish Server is running. Each virtual server must be registered with the DNS server for your network.

Note - Do not confuse an Internet domain with the administrative domain of GlassFish Server.

For example, assume that you want to host the following domains on your physical server:,, and Assume that these domains are respectively associated with web modules web1, web2, and web3. This means that the following URLs are handled by your physical server:

The first URL is mapped to virtual server, the second URL is mapped to virtual server, and the third is mapped to virtual server For this mapping to work,,, and must all resolve to your physical server’s IP address and each virtual server must be registered with the DNS server for your network. In addition, on a UNIX system, add these domains to your /etc/hosts file (if the setting for hosts in your /etc/nsswitch.conf file includes files).