Sun Java System Application Server Enterprise Edition 8.1 2005Q2 High Availability Administration Guide

About Named Configurations

Named Configurations

A named configuration is a set of server configuration information, including settings for things such as HTTP listeners, ORB/IIOP listeners, JMS brokers, the EJB container, security, logging, and monitoring. Applications and resources are not defined in named configurations.

Configurations are created in the administration domain. Multiple server instances or clusters in the domain can reference the same configuration, or they can have separate configurations.

For clusters, all server instances in the cluster inherit the cluster’s configuration so that a homogenous environment is assured in a cluster’s instances.

Because a named configuration contains so many required configuration settings, create a new configuration by copying an existing named configuration. The newly-created configuration is identical to the configuration you copied until you change its configuration settings.

There are three ways in which clusters or instances use configurations:

The default-config Configuration

The default-config configuration is a special configuration that acts as a template for creating stand-alone server instance or stand-alone cluster configurations. No unclustered server instances or clusters are allowed to refer to the default-config configuration; it can only be copied to create new configurations. Edit the default configuration to ensure that new configurations copied from it have the correct initial settings.

For more information, see:

Configurations Created when Creating Instances or Clusters

When creating a new server instance or a new cluster, either:

By default, new clusters or instances are created with configurations copied from the default-config configuration. To copy from a different configuration, specify it when creating a new instance or cluster.

For a server instance, the new configuration is named instance_name-config . For a cluster, the new configuration is named cluster-name -config.

For more information, see:

Unique Port Numbers and Configurations

If multiple instances on the same host machine reference the same configuration, each instance must listen on a unique port number. For example, if two server instances reference a named configuration with an HTTP listener on port 80, a port conflict prevents one of the server instances from starting. Change the properties that define the port numbers on which individual server instances listen so that unique ports are used.

The following principles apply to port numbers: