Administration Console Online Help

Clone Servers

Cloning servers creates new servers based on existing ones. After
cloning, update the configuration of the cloned servers if needed.

You can select to clone the Administration Server, however, if you
start the cloned Administration Server from the Console, it will
function as a Managed Server. In order for the cloned server to function
as the Administration Server for a domain, you must have set the
AdminServerName attribute on the DomainMBean before
starting it. For more information on changing the Administration Server
for a domain, see Delete the Administration
Server.

To clone servers:

If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).

In the left pane
of the Console, select Environment > Servers.

The Servers table displays all the servers defined in the
domain.

Select the check box next to the name of the server you want to
clone and click Clone.

On the
Server Identity page:

Enter a name for the server in the Server
Name field.

Each server within a
domain must have a name that is unique for all configuration
objects in the domain. Within a domain, each server, machine,
cluster, JDBC connection pool, virtual host, and any other
resource type must be named uniquely and must not use the same
name as the domain.

The server name is not
used as part of the URL for applications that are deployed on
the server. It is for your identification purposes only. The
server name displays in the Administration Console, and if you
use WebLogic Server command-line utilities or APIs, you use this
name to identify the server.

In Listen Address, if you want to
limit the valid addresses for a server instance, enter an IP
address or DNS name. Otherwise, URLs to the server can specify any
of the host computer's IP address, any DNS name that maps to one
of the IP addresses, or the localhost
string.