Sun Java System Application Server Enterprise Edition 8 2004Q4 Beta Administration Guide |
Chapter 13
Managing Named ConfigurationsThis chapter describes adding, changing, and using named server configurations in Application Server. It contains the following sections:
About Named ConfigurationsNamed Configurations
A named configuration is a set of server configuration information. This information includes configuration 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 a 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 two types of clusters and instances, depending on the way the clusters or instances use configurations:
- Standalone. A standalone server instance or cluster doesn't share its configuration with another server instance; that is, no other server instance or cluster references the named configuration. The standalone instance or cluster's configuration carries its name, for example, instance_name
-config
.- Shared. A shared server instance or cluster shares a configuration with another server instance or cluster; that is, multiple instances or clusters reference the same named configuration.
In addition, a clustered server instance is part of a cluster and inherits the cluster's configuration.
The default-config Configuration
The
default-config
configuration is a special configuration that acts as a template for creating standalone server instance or standalone cluster configurations. No unclustered server instances or clusters are allowed to refer to thedefault-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.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
.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:
- Port numbers for individual server instances are initially inherited from the configuration.
- If the port is already in use when you create a server instance, override the inherited default value at the instance level to prevent port conflicts.
- If you change the port number of the configuration, a server instance inheriting that port number automatically inherits the changed port number.
- If you changed an instance's port number and you subsequently change the configuration's port number, the instance's port number remains unchanged.
Admin Console Tasks for Named ConfigurationsCreating a Named Configuration
To create a named configuration:
- In the tree component, select the Configurations node.
- On the Configurations page, click New.
- On the Create Configurations page, enter a unique name for the configuration.
- Select a configuration to copy.
The configuration
default-config
is the default configuration used when creating standalone server instance or standalone cluster.Equivalent
asadmin
command:copy-config
.Editing a Named Configuration's Properties
To edit a named configuration's properties:
- In the tree component, expand the Configurations node.
- Select the node for a named configuration.
- On the Configuration System Properties page, add properties, change current values for properties, or delete properties.
The properties that are already defined are ports. If more than one server instance exists on a system, the port numbers must be unique.
Table 13-1 contains a list of predefined properties and their descriptions.
Equivalent
asadmin
command:set
.Editing Port Numbers for Instances Referencing a Configuration
Each instance referencing a named configuration initially inherits its port numbers from that configuration. Since port numbers must be unique on the system, you might need to override the inherited port numbers.
- In the tree component, expand the Configurations node.
- Select the node for a named configuration.
- On the Configuring System Properties page, click Instance Values next to the port number you want to edit.
For example, if you click Instance Values next to the SSL-port property, you see the value of SSL-port for every server instance that references that configuration.
- Change the port values and click Save.
Equivalent
asadmin
command:set
.Viewing a Named Configuration's Targets
To view a named configuration's targets:
- In the tree component, expand the Configurations node.
- Select a node for the named configuration.
- On the Configuration System Properties page, click the Targets tab.
The Configuration Targets page displays a list of all targets using the configuration. For a cluster configuration, those targets are clusters. For an instance configuration, those targets are instances.
Deleting a Named Configuration
To delete a named configuration:
Equivalent
asadmin
command:delete-config
.