When you create a domain, you also create an Administration Server, which runs the Administration Console and distributes configuration changes to other servers in the domain. In a typical production environment, you create one or more Managed Servers in the domain to host business applications and use the Administration Server only to configure and monitor the Managed Servers.
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.
Note: If you are using the demo certificates in a multi-server domain, Managed Server instances will fail to boot if you specify the fully-qualified DNS name. For information about this limitation and suggested workarounds, see Limitation on CertGen Usage in Administering Security for Oracle WebLogic Server.
If you run multiple server instances on a single computer, each server must use its own listen port.
If this server is part of a cluster:
See Create a cluster.