Sun Java System Application Server 9.1 High Availability Administration Guide

Chapter 7 Managing Configurations

This chapter describes adding, changing, and using named server configurations in Application Server. It contains the following sections:

Using Configurations


A 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 exist in an administrative 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 configuration contains so many required 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. Clusters and individual server instances cannot refer to default-config; 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:

Clustered Configuration Synchronization

When you create a clustered configuration, Application Server creates a cluster configuration directory on the domain administration server at domain-root/domain-dir/config/cluster-config. This directory is used to synchronize configurations for all instances in the cluster.

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:

Working with Named Configurations

ProcedureTo Create a Named Configuration

  1. In the tree component, select the Configurations node.

  2. On the Configurations page, click New.

  3. On the Create Configurations page, enter a unique name for the configuration.

  4. Select a configuration to copy.

    The configuration default-config is the default configuration used when creating stand-alone server instance or stand-alone cluster.

Equivalent asadmin command


See Also

Editing a Named Configuration’s Properties

The following table describes the properties predefined for a configuration.

The predefined properties are port numbers. Valid port values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges. If more than one server instance exists on a system, the port numbers must be unique.

Property Name 



Port number for http-listener-1. 


Port number for http-listener-2. 


ORB listener port for IIOP connections on which IIOP listener SSL listens.


ORB listener port for IIOP connections on which orb-listener-1 listens.


Port number on which the JMX connector listens. 


ORB listener port for IIOP connections on which the IIOP listener SSL_MUTUALAUTH listens.

ProcedureTo Edit a Named Configuration’s Properties

  1. In the tree component, expand the Configurations node.

  2. Select the node for a named configuration.

  3. On the Configuration System Properties page, choose whether to enable dynamic reconfiguration.

    If enabled, changes to the configuration are applied to the server instances without requiring a server restart.

  4. Add, delete, or modify properties as desired.

  5. To edit the current values of a property for all instances associated with the configuration, click Instance Values.

Equivalent asadmin command


See Also

ProcedureTo Edit 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.

  1. In the tree component, expand the Configurations node.

  2. Select the node for a named configuration.

    The Admin Console displays the Configuration System Properties page.

  3. Click Instance Values next to the instance variable you want to edit.

    For example, if you click Instance Values next to the HTTP-LISTENER-PORT instance variable, you see the value of HTTP-LISTENER-PORT for every server instance that references that configuration.

  4. Change the values as desired and click Save.

Equivalent asadmin command


See Also

ProcedureTo view a Named Configuration’s Targets

The Configuration System Properties page displays a list of all targets using the configuration. For a cluster configuration, the targets are clusters. For an instance configuration, the targets are instances.

  1. In the tree component, expand the Configurations node.

  2. Select a node for the named configuration.

See Also

ProcedureTo Delete a Named Configuration

  1. In the tree component, select the Configurations node.

  2. On the Configurations page, select the checkbox for the named configuration to delete.

    You cannot delete the default-config configuration.

  3. Click Delete.

Equivalent asadmin command


See Also