Usage Profiles
Every administrative domain is associated with a usage profile, which
identifies the capabilities of that domain. Application 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.
-
Enterprise: Use this profile
if you need HADB and NSS. This profile is usable only if you install HADB
and NSS separately or if you install Application Server as part of the Java
Enterprise System (JES). For information on how you can use the enterprise
profile with Application Server 9.1, see Using the Enterprise Profile
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 Update 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
|
Feature
|
Developer Profile
|
Cluster Profile
|
Enterprise Profile
|
|
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
|
Using the Enterprise Profile
To use the enterprise profile, perform the following tasks:
-
Download and install NSS and HADB separately.
-
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:
-
Perform an in-place upgrade of the Application Server binaries.
When you run start-domain on the domains pointing
to the earlier version of Application Server, asadmin invokes
the asupgrade command , and the domains are automatically
upgraded in-place.
-
Perform a side-by-side upgrade of the Application Server binaries.
Run start-domain on the domains of your earlier
installation. The asupgrade command upgrades the domains
to the domains root of the latest Application Server installation. In this
scenario, the target directory for the upgrade is defined in the AS_DEF_DOMAINS_PATH in the asenv.conf.