test

Sun GlassFish Communications Server 2.0 Administration Guide

Communications Server Overview and Concepts

This section contains the following topics:

Communications Server Overview

Communications Server supports the Java EE 5 specification and the SIP Servlets 1.1 API. Communications Server based on the Sun GlassFish Enterprise Server 2.1. Communications Server is built on top of the core architecture and administrative infrastructure of GlassFish.Communications Server blends SIP Servlets technology with technologies such as EJB, Java Persistence API, JDBC, Web services, and reuse container services like JNDI, JMS, Dependency Injection, Security, and Transaction management.

Communications Server SIP protocol stack implemented using Grizzly (http://grizzly.dev.java.net). Incoming requests pass through a chain of handlers that perform specific functions. For example, the Overload Handler, if enabled, would send an appropriate error response, if the server is overloaded. The optional load balancer, if enabled, would apply the specified sticky load balancing logic and forward the request to the appropriate instance in the cluster, or pass it up the stack. Initial requests are matched with deployed applications and appropriately routed. Optionally, the default or user deployed Application Router is consulted to make the initial routing decisions. Many SIP listeners can be configured to accept TCP and or UDP traffic on multiple network interfaces. SIP over TLS is supported.

You can configure and monitor Communications Server instances and clusters securely and remotely, from a web-based central administration console. Administration in a carrier deployment environment can be automated in many ways. The command line interface (CLI) can be used to script and automate processes. A stable JMX API is made available to programmatically monitor the server, query configuration and change configuration data. Monitoring is supported through JMX and SNMP interfaces. Monitoring level may be varied dynamically from OFF to LOW and high, changing the amount of information that is collected.

You can configure and optimize Communications Server for a particular type of use by specifying the appropriate profile when you create the application server domain.

Communications Server includes the Metro web services stack (http://metro.dev.java.net). Metro implements important WS-* standards and WS-I standardized interoperability profiles in order to assure interoperability between Java and .NET web services.

Communications Server includes the implementation of Java Business Integration (JBI) specifications. JBI is a Java standard for structuring business systems according to a Service-Oriented Architecture (SOA).

Tools for Administration

The Communications 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 Communications 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:


http://hostname:port

For example:


http://kindness.sun.com:4848

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

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

The installation program creates the default administrative domain (named domain1) with the default port number 4848, as well as an instance separate from the domain administration server (DAS). 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 GlassFish Communications 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 GlassFish Communications Server 2.0 Reference Manual.

JConsole

JConsole is used to monitor the Sun GlassFish Communications Server. You can use either the JConsole remote tab, or the advanced tab to connect to the Communications Server.