Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Server --> Configuration --> General

Tasks Related Topics Attributes

## Overview

The Server—>Configuration—>General tab defines general configuration attributes for an instance of WebLogic Server.

## Tasks

Configuring a Machine

Configuring a Cluster

Configuring the Listen Address

Configuring the Listen Ports

Starting Managed Servers from the Administration Console

Shutting Down Instances of WebLogic Server

Adding and Removing Servers in an Existing Domain

Deleting a Managed Server

"Creating Execute Queues" in WebLogic Server Performance and Tuning

## Related Topics

Using WebLogic Server Clusters

Administration Port Configuration and Startup

Configuring WebLogic Server Web Components

## Attributes

Table 269-1

Attribute Label | Description | Value Constraints
--- | --- | ---
Name | An alphanumeric name for this server instance. This field will not accept spaces. Each server instance in your WebLogic environment must have a unique name, regardless of the domain or cluster in which it resides, or whether it is an Administration Server or a Managed Server. 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. For more information, refer to Cloning a Server. MBean: `weblogic.management. configuration.ServerMBean` Attribute: `Name` |
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. Node Manager uses this information to communicate with the server on its host machine. MBean: `weblogic.management. configuration.ServerMBean` Attribute: `Machine` | Configurable: yes
Cluster | The cluster to which this server belongs. If set, the server will listen for cluster multicast events. MBean: `weblogic.management. configuration.ServerMBean` Attribute: `Cluster` | Configurable: yes
Listen Address | The address from which this server listens for requests. Servers can be reached through the following URL: `protocol``://``listen-address``:``listen-port` By default, a server's listen address attribute is undefined, which enables you to 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. For more information, refer to Configuring the Listen Address. MBean: `weblogic.management. configuration.ServerMBean` Attribute: `ListenAddress` |
Listen Port Enabled | Determines whether the 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: `weblogic.management. configuration.ServerMBean` Attribute: `ListenPortEnabled` | Default: true Valid values: true false
Listen Port | The default plain-text (non-SSL) listen port for this server. For more information, refer to Configuring the Listen Ports. MBean: `weblogic.management. configuration.ServerMBean` Attribute: `ListenPort` | Minimum: 1 Maximum: 65534 Default: 7001 Configurable: yes
SSL Listen Port Enabled | Determines whether the server can be reached through the default SSL listen port. If you disable this listen port, you must enable the default plain-text (non-SSL) listen port. You can define additional listen ports for this server by configuring network channels. MBean: `weblogic.management. configuration.SSLMBean` Attribute: `Enabled` | Default: false Valid values: true false
SSL Listen Port | The default SSL listen port for this server. For more information, refer to Configuring the Listen Ports. MBean: `weblogic.management. configuration.SSLMBean` Attribute: `ListenPort` | Minimum: 1 Maximum: 65534 Default: 7002 Configurable: yes
Client Cert Proxy Enabled | When set to true for a server instance, this attribute specifies that certs from clients of web applications hosted on the server instance are provided in the special `WL-Proxy-Client-Cert` header sent by a proxy plug-in or `HttpClusterServlet`. (`ClientCertProxyEnabled` can be defined at the cluster level, at the server level, and at the web application level, in `web.xml`.) This setting is useful if user authentication is performed on the proxy server—setting `clientCertProxy` to true causes the plug-in to pass on the certs to the cluster in the `WL-Proxy-Client-Cert` header. The header can be used by any client with direct access to WebLogic Server. WebLogic Server takes the certificate information from that header, trusting that is came from a secure source (the plug-in) and uses that information to authenticate the user. If you set `clientCertProxy` to true, use a connection filter to ensure that WebLogic Server accepts connections only from the machine on which the plug-in is running. See "Using Network Connection Filters" in Programming WebLogic Security. | Default: false Valid values: true false
Java Compiler | The Java Compiler for all applications that need to compile Java code. MBean: `weblogic.management. configuration.ServerMBean` Attribute: `JavaCompiler` | Default: "javac" Dynamic: yes

#### Advanced Attributes

Table 269-2

Attribute Label | Description | Value Constraints
--- | --- | ---
WebLogic Plug-In Enabled | Set this attribute to true if the server instance will receive requests from a proxy plug-in or `HttpClusterServlet`. When `WeblogicPluginEnabled` is true, 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. If the server instance is a member of a cluster that will receive proxied requests, set `WeblogicPluginEnabled` for the cluster, on the Cluster -->Configuration-->General tab. `WeblogicPluginEnabled` can be configured in `ClusterMBean` or `ServerMBean`. If specified in both `ClusterMBean` and `ServerMBean`, the value in `ClusterMBean` value takes precedence. MBean: `weblogic.management. configuration.ServerMBean` Attribute: `WeblogicPluginEnabled` | Default: false Valid values: true false
Startup Mode | The state in which this server should be started. In the `RUNNING` state, a server offers its services to clients and can operate as a full member of a cluster. In the `STANDBY` state, a server can accept administration commands and participate in cluster communication, but is not accessible for requests that come from external clients. (If you select `STANDBY`, you must also enable the domain-wide administration port under this domain's Configuration > General tab.) MBean: `weblogic.management. configuration.ServerMBean` Attribute: `StartupMode` | Valid values: RUNNING STANDBY
Prepend to classpath | The options to prepend to the Java compiler classpath for when we need to compile Java code. MBean: `weblogic.management. configuration.ServerMBean` Attribute: `JavaCompilerPreClassPath` | Default: null
Append to classpath | The options to append to the Java compiler classpath for when we need to compile Java code. MBean: `weblogic.management. configuration.ServerMBean` Attribute: `JavaCompilerPostClassPath` | Default: null
Extra RMI Compiler Options | The extra options passed to `rmic` during server-side generation. If extra rmic options are specified at the EJB component level—on `EJBComponentMBean`—that value overrides this server-level value. See Configuring Compiler Options. MBean: `weblogic.management. configuration.ServerMBean` Attribute: `ExtraRmicOptions` | Default: null
Extra EJB Compiler Options | The extra options passed to `ejbc` during server-side generation. Note: If extra ejbc options are specified at the EJB component level—on `EJBComponentMBean`—that value overrides this server-level value. See Configuring Compiler Options. MBean: `weblogic.management. configuration.ServerMBean` Attribute: `ExtraEjbcOptions` | Default: null
External Listen Address | The external DNS name for the current server, which will be sent with HTTP session cookies and also with the dynamic server lists to HTTP proxies. Do not specify an IP address for this attribute—the value must be an actual domain name. This attribute is required for configurations in which a firewall is performing Network Address Translation, unless clients are accessing WebLogic Server using t3 and the default channel. For instance, 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: `weblogic.management. configuration.ServerMBean` Attribute: `ExternalDNSName` | Default: null Configurable: yes Required: yes
Administration Port Enabled | Indicates whether the administrative channel is enabled for the domain. You enable the administrative channel on the Domain > Configuration > General tab. For more information, refer to "Administration Port Configuration and Startup." | Valid values: true false
Local Administration Port Override (0: no 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: `weblogic.management. configuration.ServerMBean` Attribute: `AdministrationPort` | Minimum: 0 Maximum: 65534 Default: 0