Every administrative domain is associated with a usage profile, which identifies the capabilities of that domain. Communications Server provides the following profiles:
Developer: Use this profile 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 profile if you need to create clusters but do not require the high-availability database (HADB) or the NSS keystore.
In the cluster and developer profile, the DAS is set to be in non-secure mode, by default. While running asadmin commands, use --secure=false, wherever required. Do not use this flag if you have made changes to set DAS to secure mode.
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 Communications Server to create different domains with profiles that suit specific needs. For example, a developer may want to use the Communications 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
Feature |
Developer Profile |
Cluster Profile |
Enterprise Profile (not available with Sun GlassFish Communications Server) |
---|---|---|---|
Security store |
JKS |
JKS |
NSS |
Clustering/Standalone instances |
Not available |
Available |
Available |
Security Manager |
Disabled |
Enabled |
Enabled |
HADB |
Not available |
Not available |
Available |
Load balancing |
Not available |
Available |
Available |
Node agents |
Not available |
Available |
Available |