Before you begin
Not all Oracle Fusion Middleware environments support how WebLogic Server clones managed servers, for example Reports Managed servers. For more information, see the Oracle Fusion Middleware High Availability Guide and review the sections for your environment.
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
The Servers table displays all the servers defined in the domain.
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.
If you run multiple server instances on a single computer, each server must use its own listen port.
The server appears in the Summary of Servers table.