Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Servers: Configuration: General

Configuration Options Advanced Configuration Options Related Tasks Related Topics

Use this page to configure general features of this server such as default network communications.

#### Configuration Options

Name | Description
--- | ---
Name | An alphanumeric name for this server instance. This field will not accept spaces. The name must be 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. After you have created a server, you cannot change its name. Instead, clone the server and provide a new name for the clone. MBean Attribute: `ServerMBean.Name` Changes take effect after you redeploy the module or restart the server.
Machine | The WebLogic Server host computer (machine) on which this server is meant to run. If you want to use a Node Manager to start this server, you must assign the server to a machine and you must configure the machine for the Node Manager. You cannot change this value if a server instance is already running. MBean Attribute: `ServerMBean.Machine` Changes take effect after you redeploy the module or restart the server.
Cluster | The cluster, or group of WebLogic Server instances, to which this server belongs. If set, the server will listen for cluster multicast events. MBean Attribute: `ServerMBean.Cluster` Changes take effect after you redeploy the module or restart the server.
Listen Address | The IP address or DNS name this server uses to listen for incoming connections. Servers can be reached through the following URL: protocol://listen-address:listen-port 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 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: 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. 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 Windows computer that uses multiple IP address (a multihomed computer). On such a computer, the server will bind to all available IP addresses. Note: 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 will fail. MBean Attribute: `ServerMBean.ListenAddress` Changes take effect after you redeploy the module or restart the server.
Listen Port Enabled | Specifies whether this server can be reached through the default plain-text (non-SSL) listen port. If you disable this listen port, you must enable the default SSL listen port. You can define additional listen ports for this server by configuring network channels. MBean Attribute: `ServerMBean.ListenPortEnabled`
Listen Port | The default TCP port that this server uses to listen for regular (non-SSL) incoming connections. 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. MBean Attribute: `ServerMBean.ListenPort` Minimum value: `1` Maximum value: `65534`
Machine | The WebLogic Server host computer (machine) on which this server is meant to run. If you want to use a Node Manager to start this server, you must assign the server to a machine and you must configure the machine for the Node Manager. You cannot change this value if a server instance is already running. MBean Attribute: `ServerMBean.Machine` Changes take effect after you redeploy the module or restart the server.
Cluster | The cluster, or group of WebLogic Server instances, to which this server belongs. If set, the server will listen for cluster multicast events. MBean Attribute: `ServerMBean.Cluster` Changes take effect after you redeploy the module or restart the server.
SSL Listen Port Enabled | Indicates whether the server can be reached through the default SSL listen port. If the administration port is enabled for the WebLogic Server domain, then administrative traffic travels over the administration port and application traffic travels over the Listen Port and SSL Listen Port. If the administration port is disabled, then all traffic travels over the Listen Port and SSL Listen Port. MBean Attribute: `SSLMBean.Enabled` Secure value: `true`
SSL Listen Port | The TCP/IP port at which this server listens for SSL connection requests. MBean Attribute: `SSLMBean.ListenPort` Minimum value: `1` Maximum value: `65535`
Client Cert Proxy Enabled | Specifies whether the `HttpClusterServlet` proxies the client certificate in a special header. By default (or if you specify `false`), the `weblogic.xml` deployment descriptor for each web application that is deployed on this server determines whether the web application trusts certificates sent from the proxy server plugin. By default (or if the deployment descriptor specifies `false`), users cannot log in to the web application from a proxy server plugin. A value of `true` causes proxy-server plugins to pass identity certifications from clients to all web applications that are deployed on this server instance. A proxy-server plugin encodes each identify certification in the `WL-Proxy-Client-Cert` header and passes the header to WebLogic Server instances. A WebLogic Server instance takes the certificate information from the header, trusting that it came from a secure source, and uses that information to authenticate the user. If you specify `true`, use a `weblogic.security.net.ConnectionFilter` to ensure that this WebLogic Server instance accepts connections only from the machine on which the proxy-server plugin is running. Specifying `true` without using a connection filter creates a security vulnerability because the `WL-Proxy-Client-Cert` header can be spoofed. A cluster can also specify whether the `HttpClusterServlet` proxies the client certificate in a special header. The cluster-level setting overrides the setting in individual servers that are part of the cluster. MBean Attribute: `ServerMBean.ClientCertProxyEnabled` Changes take effect after you redeploy the module or restart the server.
Java Compiler | The Java compiler to use for all applications hosted on this server that need to compile Java code. MBean Attribute: `ServerMBean.JavaCompiler` Secure value: `javac`

#### Advanced Configuration Options

Name | Description
--- | ---
Startup Mode | The state in which this server should be started. If you specify `STANDBY`, you must also enable the domain-wide administration port. In the `RUNNING` state, a server offers its services to clients and can operate as a full member of a cluster. In the `ADMIN` state, the server is up and running, but available only for administration operations, allowing you to perform server and application-level administration tasks without risk to running applications. In the `STANDBY` state, a server instance does not process any request; its regular Listen Port is closed. The Administration Port is open. It only accepts life cycle commands that transition the server instance to either the `RUNNING` or the `SHUTDOWN` state. Other Administration requests are not accepted. A `STANDBY`server's only purpose is to resume into the `RUNNING` state quickly; it saves server startup time. MBean Attribute: `ServerMBean.StartupMode`
WebLogic Plug-In Enabled | Specifies whether this server uses the proprietary `WL-Proxy-Client-IP` header, which is recommended if the server instance will receive requests from a proxy plug-in. If the server instance is a member of a cluster that will receive proxied requests, enable the WebLogic plugin at the cluster level. For servers that are members of a cluster, the setting at the cluster level overrides the server's setting. When the WebLogic plugin is enabled, a call to `getRemoteAddr` will return the address of the browser client from the proprietary `WL-Proxy-Client-IP` header instead of the web server. MBean Attribute: `ServerMBean.WeblogicPluginEnabled` Changes take effect after you redeploy the module or restart the server.
Prepend to classpath | The options to prepend to the Java compiler classpath when compiling Java code. MBean Attribute: `ServerMBean.JavaCompilerPreClassPath` Changes take effect after you redeploy the module or restart the server.
Append to classpath | The options to append to the Java compiler classpath when compiling Java code. MBean Attribute: `ServerMBean.JavaCompilerPostClassPath` Changes take effect after you redeploy the module or restart the server.
Extra RMI Compiler Options | The options passed to the RMIC compiler during server-side generation. Each EJB component can override the compiler options that you specify here. MBean Attribute: `ServerMBean.ExtraRmicOptions` Changes take effect after you redeploy the module or restart the server.
Extra EJB Compiler Options | The options passed to the EJB compiler during server-side generation. Each EJB component can override the compiler options that you specify here. The following options are valid: -forcegeneration Forces generation of wrapper classes. Without this flag the classes may not be regenerated if it is determined to be unnecessary. -disableHotCodeGen Generate ejb stub and skel as part of ejbc. Avoid HotCodeGen to have better performance. -keepgenerated Keep the generated .java files. -compiler javac Java compiler to exec. If not specified, the -compilerclass option will be used. -compilerclass com.sun.tools.javac.Main Specifies the compiler class to invoke. -g Compile debugging info into class file. -normi Passed through to Symantec's sj. -classpath path Classpath to use. -source source Source version. -Joption Flags passed through to java runtime. MBean Attribute: `ServerMBean.ExtraEjbcOptions` Changes take effect after you redeploy the module or restart the server.
External Listen Address | The external IP address or DNS name for this server. This address will be sent with HTTP session cookies and with dynamic server lists to HTTP proxies. It will also be used by external application clients to enable the propagation of RMI traffic through network address translating (NAT) firewalls. You must specify an external DNS name for configurations in which a firewall is performing network address translation, unless clients are accessing WebLogic Server using t3 and the default channel. For example, define the external DNS name for configurations in which a firewall is performing network address translation, and clients are accessing WebLogic Server using HTTP via a proxy plug-in. MBean Attribute: `ServerMBean.ExternalDNSName` Changes take effect after you redeploy the module or restart the server.
Local Administration Port Override | Overrides the domain-wide administration port and specifies a different listen port on which this server listens for administrative requests. Valid only if the administrative channel is enabled for the domain. By default, if you enable the domain's administrative channel, all servers in the domain use the same listen port to listen for administrative requests. MBean Attribute: `ServerMBean.AdministrationPort` Minimum value: `0` Maximum value: `65534` Secure value: `7002`
JDBC LLR Table Name | The table name for this server's Logging Last Resource (LLR) database table(s). WebLogic Server creates the table(s) and then uses them during transaction processing for the LLR transaction optimization. This setting must be unique for each server. The default table name is `WL_LLR_SERVERNAME`. This setting only applies if this server hosts one or more LLR-enabled JDBC data sources. The format for the tables that WebLogic Server creates is [[[catalog.]schema.]name. Each "." in the table name is significant, and schema generally corresponds to username in many databases. IMPORTANT: If this value is changed but the LLR table already exists in the database, you must preserve the existing table's data. Consequently, when changing the table name, the existing database table must be renamed by a database administrator to match the new configured table name. Otherwise, transaction records may be lost, resulting in heuristic failures that aren't logged. IMPORTANT: Each server's table name must be unique. Multiple LLR-enabled data sources within the same server may share the same table, but multiple servers must not share the same table. If multiple same-named servers share a table, the behavior is undefined and it is likely that transactions will not recover properly after a crash, creating heuristic hazards. MBean Attribute: `ServerMBean.JDBCLLRTableName` Changes take effect after you redeploy the module or restart the server.

Related Tasks

- Configure default network connections
- Create and configure machines
- Configure clusters
- Start and stop servers

Related Topics

- Starting and Stopping Servers
- Understanding Server Life Cycle
- Using WebLogic Server Clusters
- Understanding Domain Configuration