Create Managed Servers

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.

To create a Managed Server in an existing domain:

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.
In the Servers table, click New.
On the Create a New Server: Server Properties page:
1. Enter the name of the server in the 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.
  
  For more information on server naming conventions, see Server Name Restrictions
2. In Listen Address, if you want to limit the valid addresses for a server instance, enter an IP address or DNS name. For example, enter 12.34.5.67 or mymachine, respectively. 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. The value you specify for the listen address is not the URL to the host machine and it does not include the communication protocol, listen port, or channel.
  See Configuration Options.
  
  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.
3. In Listen Port, enter the port number from which you want to access the server instance.
  If you run multiple server instances on a single computer, each server must use its own listen port.
4. Specify whether or not this server will be a stand alone server or will belong to a cluster.
  If this server is part of a cluster:
  - Select an existing cluster from the drop down list.
  - Select the button to create a new cluster
  See Create a cluster.
5. Click Next.
6. Review the configuration options you have chosen.
7. Click Finish.
To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Not all changes take effect immediately—some require a restart (see Use the Change Center).

Result

The Administration Console updates the domain's config.xml file with the new server configuration data.

Note: In the file system, the Managed Server directory structure becomes populated upon its inital startup.

After you finish

(Optional) Do any of the following:

Administration Console Online Help

Create Managed Servers