Column Display Related Tasks Related Topics
This page summarizes each server template that has been configured in the current WebLogic Server domain.
A server template contains common, non-default attributes that you can apply to a set of server instances, which then inherit the template configuration. Server templates enable you to easily manage configuration for a group of server instances in one centralized location.
You can show fewer or additional data points on this page by expanding Customize this table and modifying the Column Display list. Each data point displays in its own table column.
The following table lists all of the data points that you can display in columns on this page.
Name Description Name
The alphanumeric name for this server instance.
The cluster, or group of WebLogic Server instances, to which this server belongs.
If set, the server will listen for cluster multicast events.
The WebLogic Server host computer (machine) on which this server is meant to run.
If you want to use Node Manager to start this server, you must assign the server to a machine and you must configure the machine for Node Manager.
You cannot change this value if a server instance is already running.
The default TCP port that this server uses to listen for regular (non-SSL) incoming connections.
Administrators must have the right privileges before binding to a port or else this operation will not be successful and it will render the console un-reachable.
If this port is disabled, the SSL port must be enabled. Additional ports can be configured using network channels. The cluster (multicast) port is configured separately.
The IP address or DNS name this server uses to listen for incoming connections.
Servers can be reached through the following URL:
Any network channel that you configure for this server can override this listen address.
If a server's listen address is undefined, clients can reach the server through an IP address of the computer that hosts the server, a DNS name that resolves to the host, or the localhost string. The localhost string can be used only for requests from clients that are running on the same computer as the server.
If you want to limit the valid addresses for a server instance, specify one of the following:
IP address. If you provide an IP address, clients can specify either the IP address or a DNS name that maps to the IP address. Clients that specify an IP address and attempt to connect through an SSL port must disable hostname verification.
DNS name. If you provide a DNS name, clients can specify either the DNS name or the corresponding IP address.
Do not leave the listen address undefined on a computer that uses multiple IP address (a multihomed computer). On such a computer, the server will bind to all available IP addresses.
To resolve a DNS name to an IP address, WebLogic Server must be able to contact an appropriate DNS server or obtain the IP address mapping locally. Therefore, if you specify a DNS name for the listen address, you must either leave a port open long enough for the WebLogic Server instance to connect to a DNS server and cache its mapping or you must specify the IP address mapping in a local file. If you specify an IP address for ListenAddress and then a client request specifies a DNS name, WebLogic Server will attempt to resolve the DNS name, but if it cannot access DNS name mapping, the request fails.
Note also that 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.
- Create server templates
- Configure server templates
- Apply a server template
- Delete server templates
- Clone server templates
- Create dynamic clusters