Sun Microsystems 820433510 Server User Manual


  Open as PDF
of 256
 
carry out the requests. The DAS is sometimes referred to as the admin server or default server. It
is referred to as the default server because it is the only server instance that gets created on Sun
GlassFish Enterprise Server installation and can be used for deployments. The DAS is simply a
server instance with additional administration capabilities.
Each Admin Console session allows you to congure and manage a single domain. If you
created multiple domains, you must start an additional Admin Console session to manage the
other domains. When specifying the URL for the Admin Console, be sure to use the port
number of the DAS associated with the domain to be administered.
Usage Proles
Every administrative domain is associated with a usage prole, which identies the capabilities
of that domain. Enterprise Server provides the following proles:
■
Developer: Use this prole if you are running your domain in a development environment
and if your applications do not need the NSS keystore or clustering features, such as load
balancing, and session persistence.
■
Cluster: Use this prole if you need to create clusters but do not require the high-availability
database (HADB) or the NSS keystore.
■
Enterprise:: Use this prole if you need HADB and NSS. This prole is usable only if you
install HADB and NSS separately or if you install Enterprise Server as part of enterprise
oerings, such as Java Enterprise System (JES). For information on how you can use the
enterprise prole with Enterprise Server, see Using the Enterprise Prole
The domain provides a precongured runtime for the user applications. Usage proles
facilitates the distinction between the Application Server binaries and the runtime
conguration. Proles enable you to use the same installation of Enterprise Server to create
dierent domains with proles that suit specic needs. For example, a developer may want to
use the Enterprise Server to get to know the latest Java EE specications. 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 prole:
TABLE1–1 FeaturesAvailablefor Each Prole
Feature DeveloperProle ClusterProle
EnterpriseProle(not
availablewithSunGlassFish
CommunicationsServer)
Security store JKS JKS NSS
Clustering/Standalone instances Not available Available Available
EnterpriseServerConcepts
Chapter1 • EnterpriseServerOverview 27
 previous next